June 2009 - esb-issues - Jboss List Archives

[JBoss JIRA] Created: (JBESB-2507) JMS JCA mapper sets maxMessages instead of maxSession

by Kevin Conner (JIRA)

JMS JCA mapper sets maxMessages instead of maxSession ----------------------------------------------------- Key: JBESB-2507 URL: https://jira.jboss.org/jira/browse/JBESB-2507 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.5 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.6 The JMS/JCA adapter initialises some variables in the activation spec and, until now, mapped the max threads count onto maxMessages. This was the wrong attribute to specify but has worked so far due to a bug in the base app server jms-ra.rar code, now fixed in JBPAPP-1045. We should have been setting the maxSession attribute instead. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-2504) Identify any issues with using IBM MQ and provide direct support within the ESB codebase

by Kevin Conner (JIRA)

Identify any issues with using IBM MQ and provide direct support within the ESB codebase ---------------------------------------------------------------------------------------- Key: JBESB-2504 URL: https://jira.jboss.org/jira/browse/JBESB-2504 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.2.1 CP4 Reporter: Kevin Conner Fix For: 4.2.1 CP5 TomF has already done some work on this task, in relation to a customer enquiry. The solution he created was to provide an adapter to the MQ ConnectionFactory/Connection classes which could then be referred to from within the ESB configuration. The main purpose of the adapter was to handle the requirement that there only be a single session per connection when executing within a transactional context. We need to move this requirement back into the ESB codebase and support it directly within the JMS connection pool. An additional part of this task will be to identify any further issues which arise and create appropriate JIRAs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

1
4
0 / 0

[JBoss JIRA] Created: (JBESB-2577) Remove old management console from the codebase

by Kevin Conner (JIRA)

Remove old management console from the codebase ----------------------------------------------- Key: JBESB-2577 URL: https://jira.jboss.org/jira/browse/JBESB-2577 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Management Affects Versions: 4.5 Reporter: Kevin Conner Assignee: Tom Cunningham Fix For: 4.6 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

3
4
0 / 0

[JBoss JIRA] Created: (JBESB-2483) JBM HeuristicMixedException may destabilise the resource used during transactional contexts

by Kevin Conner (JIRA)

JBM HeuristicMixedException may destabilise the resource used during transactional contexts ------------------------------------------------------------------------------------------- Key: JBESB-2483 URL: https://jira.jboss.org/jira/browse/JBESB-2483 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.5 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.6 JBoss Messaging sometimes causes a HeuristicMixedException to be raised by the transaction manager during commit. Once this happens the associated session would appear to be destabilised in that subsequent use does not appear possible The log files contain the following output. On the client side 2009-03-03 07:17:13,137 118839811 ERROR [org.hibernate.transaction.JTATransaction] (JbpmJobExector:<ip addr>:12:) JTA commit failed javax.transaction.HeuristicMixedException at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1414) at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:135) at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:87) at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.commit(ServerVMClientUserTransaction.java:140) at org.hibernate.transaction.JTATransaction.commit(JTATransaction.java:146) at org.jbpm.persistence.db.DbPersistenceService.commit(DbPersistenceService.java:295) at org.jbpm.persistence.db.DbPersistenceService.close(DbPersistenceService.java:253 This exception is sometimes, although not always, paired up with the following exception on the server side. 2009-03-03 07:29:32,752 119400749 ERROR [org.jboss.messaging.util.ExceptionUtil] (WorkerThread#7[<ip addr>:35552]:) ConnectionEndpoint[2gw-biv0otrf-1-png68srf-w3rpob-v2p1hs4] sendTransaction [4bz-4vj97urf-1-png68srf-w3rpob-v2p1hs4] javax.jms.IllegalStateException: Cannot find session with id i2y-gk8bttrf-1-png68srf-w3rpob-v2p1hs4 at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.processTransaction(ServerConnectionEndpoint.java:835) at org.jboss.jms.server.endpoint.ServerConnectionEndpoint.sendTransaction(ServerConnectionEndpoint.java:497) at org.jboss.jms.server.endpoint.advised.ConnectionAdvised.org$jboss$jms$server$endpoint$advised$ConnectionAdvised$sendTransaction$aop(ConnectionAdvised.java:101) at org.jboss.jms.server.endpoint.advised.ConnectionAdvised$sendTransaction_N3268650789275322226.invokeNext(ConnectionAdvised$sendTransaction_N3268650789275322226.java) at org.jboss.jms.server.container.SecurityAspect.handleSendTransaction(SecurityAspect.java:195) at sun.reflect.GeneratedMethodAccessor231.invoke(Unknown Source) The exceptions are always generated with the same session id which would suggest that there is an underlying issue in the JBoss Messaging codebase. We need to handle this until the issue is resolved within JBM. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2480) Client and server side JBM information can become out of sync

by Kevin Conner (JIRA)

Client and server side JBM information can become out of sync ------------------------------------------------------------- Key: JBESB-2480 URL: https://jira.jboss.org/jira/browse/JBESB-2480 Project: JBoss ESB Issue Type: Bug Security Level: Public (Everyone can see) Components: Transports Affects Versions: 4.5 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.6 The issue appears to be occurring with the connection information and has been seen with a co-located (client and server in same VM) deployment. This may be indicative of a race condition, with the server side (even though co-located) deciding to close the connection at the same time as we access it. The result of this is the following Caused by: java.lang.IllegalStateException: Cannot find object in dispatcher with id jr51-zktjeurf-1-wxm28srf-0fpqee-t2p1hs4 at org.jboss.jms.wireformat.ConnectionCreateSessionDelegateRequest.serverInvoke(ConnectionCreateSessionDelegateRequest.java:84) at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143) at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:866) at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:608) at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:420) at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:173) We should check for this during session creation and, if found, attempt to cleanup and re-establish the connection. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

1
2
0 / 0

[JBoss JIRA] Created: (JBESB-2097) ServiceInvoker Exception details

by Burr Sutter (JIRA)

ServiceInvoker Exception details -------------------------------- Key: JBESB-2097 URL: https://jira.jboss.org/jira/browse/JBESB-2097 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Rosetta Affects Versions: 4.4 Reporter: Burr Sutter Current the ServiceInvoker.deliverSync() method might throw the following exceptions: MessageDeliverException RegistryException FaultMessageException requestMessage = MessageFactory.getInstance().getMessage(); requestMessage.getProperties().setProperty(Environment.EXCEPTION_ON_DELIVERY_FAILURE,"true"); ServiceInvoker invoker = new ServiceInvoker("MyCategory", "Service99"); replyMessage = invoker.deliverSync(requestMessage,2000); A service name which does not exist results in a MessageDeliverException, with the following information exposed via a System.err.println(mde); 11:25:16,179 ERROR [STDERR] org.jboss.soa.esb.listeners.message.MessageDeliverEx ception: Failed to deliver message [header: [ ]] to Service [MyCategory:Servic e99]. Check for errors. It would have made more sense for it to be a RegistryException and the actual message doesn't indicate that there is a lookup problem. Futhermore, a timeout results in the following MessageDeliverException: 11:45:06,278 ERROR [STDERR] org.jboss.soa.esb.listeners.message.MessageDeliverEx ception: Failed to deliver message [header: [ To: InVMEpr [ PortReference < <wsa :Address invm://52455354456173794553425365727669636531/false?false#10000/>, <wsa :ReferenceProperties jbossesb:passByValue : false/>, <wsa:ReferenceProperties jb ossesb:type : urn:jboss/esb/epr/type/invm/> > ] ReplyTo: InVMEpr [ PortReference < <wsa:Address invm://thread-559/>, <wsa:ReferenceProperties jbossesb:passByVal ue : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/in vm/> > ] ]] to Service [MyCategory:Service1]. Told not to retry. No indication that the problem is timeout and the "Told not to retry" is a bit terse. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 9 months

4
11
0 / 0

[JBoss JIRA] Created: (JBESB-2659) Add Smooks User Guide

by Tom Fennelly (JIRA)

Add Smooks User Guide --------------------- Key: JBESB-2659 URL: https://jira.jboss.org/jira/browse/JBESB-2659 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Transformation Service Reporter: Tom Fennelly Assignee: Tom Fennelly Fix For: 4.6 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2581) Allow registry organization information to be configured

by Kevin Conner (JIRA)

Allow registry organization information to be configured -------------------------------------------------------- Key: JBESB-2581 URL: https://jira.jboss.org/jira/browse/JBESB-2581 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Registry and Repository Affects Versions: 4.5 Reporter: Kevin Conner Fix For: 4.6 This covers retrieval and creation of the organization within the registry. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 10 months

2
4
0 / 0

[JBoss JIRA] Created: (JBESB-2657) Remove drop/delete from jBPM quartz configuration files

by Kevin Conner (JIRA)

Remove drop/delete from jBPM quartz configuration files ------------------------------------------------------- Key: JBESB-2657 URL: https://jira.jboss.org/jira/browse/JBESB-2657 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.4 CP2 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 10 months

1
1
0 / 0

[JBoss JIRA] Created: (JBESB-2658) Add configuration for jBPM/JMS inflow scheduler service

by Kevin Conner (JIRA)

Add configuration for jBPM/JMS inflow scheduler service ------------------------------------------------------- Key: JBESB-2658 URL: https://jira.jboss.org/jira/browse/JBESB-2658 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Process flow Affects Versions: 4.4 CP2 Reporter: Kevin Conner Assignee: Kevin Conner Fix For: 4.4 CP3 Should have been in the configuration files as a commented out section. Need to add definitions for the queue and listener, and update documentation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

16 years, 10 months

1
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

esb-issues June 2009