[JBoss JIRA] Created: (JBESB-2484) 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-2484
URL: https://jira.jboss.org/jira/browse/JBESB-2484
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
15 years, 7 months
[JBoss JIRA] Created: (JBESB-2779) InVM ReplyTo cleanup code invalid in ServiceInvoker
by Kevin Conner (JIRA)
InVM ReplyTo cleanup code invalid in ServiceInvoker
---------------------------------------------------
Key: JBESB-2779
URL: https://jira.jboss.org/jira/browse/JBESB-2779
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Transports
Affects Versions: 4.4 CP3
Reporter: Martin Vecera
Assignee: Kevin Conner
Fix For: 4.4 CP3
I have two services in a single ESB archive. Both have set invmScope="GLOBAL", the first service is accessible via EBWS and routes the message to the second service. The client awaits a response, which should be sent by the second service to a thread that executes EBWS servlet. Instead of this and exception is thrown.
2009-07-22 08:30:43,550 ERROR [org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] Failed to send reply to address InVMEpr [ PortReference < <wsa:Address invm://thread-910-3/
>, <wsa:ReferenceProperties jbossesb:passByValue : false/> > ] for message header: [ To: InVMEpr [ PortReference < <wsa:Address invm://thread-910-3/>, <wsa:ReferenceProperties jbossesb
:passByValue : false/> > ] From: InVMEpr [ PortReference < <wsa:Address invm://526f757465725465737424242424242424242424242445425753526f757465/false?false#10000/>, <wsa:ReferencePropert
ies jbossesb:passByValue : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/invm/> > ] RelatesTo: b013fa7a-18ac-40ef-bac5-7ad3ef2c6c5b ]
org.jboss.soa.esb.couriers.CourierException: No deliverAsync courier
at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.deliver(TwoWayCourierImpl.java:170)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.messageTo(ActionProcessingPipeline.java:835)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.replyTo(ActionProcessingPipeline.java:757)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:687)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:574)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:408)
at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:540)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
When an JMS queue is configured in the first service, everything works like a charm.
--
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
15 years, 7 months
[JBoss JIRA] Created: (JBESB-2771) JmsCourier should be allowed to overwrite outgoing JMS Message properties.
by Daniel Bevenius (JIRA)
JmsCourier should be allowed to overwrite outgoing JMS Message properties.
--------------------------------------------------------------------------
Key: JBESB-2771
URL: https://jira.jboss.org/jira/browse/JBESB-2771
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Rosetta, Transports
Affects Versions: 4.6
Reporter: Daniel Bevenius
Assignee: Daniel Bevenius
Fix For: 4.7
When a JmsCourier is created and is specified to be a sender (isReciever=false), the passed in JMSEPR's message selector is stored in a field (_messageProperties which is a List of KeyValuePairs).
When this JmsCourier is going to deliver a JMS Message it will iterate through the properties and set them on the outgoing JMS Message. The problem here is that the current implementation will first check to see if the JMS Message already has a property with the same key set on it, and if it has, will not overwrite the value.
This is a problem because before this is done the JMSPropertiesStrategy will have been run and might for example have set the 'jbossESBresponseUUID' causing and old and invalid message selector to be passed through.
This can be fixed by letting the JmsCourier have the last say and overwrite message properties. Or an explicit check could be add for 'jbossESBresponseUUID'.
This issue was reported by Toshiya Kobayashi who also provided some nice examples that reproduce this issue.
--
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
15 years, 7 months
[JBoss JIRA] Created: (JBESB-2758) ReplyTo header is invalid after static router with InVM
by Martin Vecera (JIRA)
ReplyTo header is invalid after static router with InVM
-------------------------------------------------------
Key: JBESB-2758
URL: https://jira.jboss.org/jira/browse/JBESB-2758
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Transports
Affects Versions: 4.4 CP3
Reporter: Martin Vecera
I have two services in a single ESB archive. Both have set invmScope="GLOBAL", the first service is accessible via EBWS and routes the message to the second service. The client awaits a response, which should be sent by the second service to a thread that executes EBWS servlet. Instead of this and exception is thrown.
2009-07-22 08:30:43,550 ERROR [org.jboss.soa.esb.listeners.message.ActionProcessingPipeline] Failed to send reply to address InVMEpr [ PortReference < <wsa:Address invm://thread-910-3/
>, <wsa:ReferenceProperties jbossesb:passByValue : false/> > ] for message header: [ To: InVMEpr [ PortReference < <wsa:Address invm://thread-910-3/>, <wsa:ReferenceProperties jbossesb
:passByValue : false/> > ] From: InVMEpr [ PortReference < <wsa:Address invm://526f757465725465737424242424242424242424242445425753526f757465/false?false#10000/>, <wsa:ReferencePropert
ies jbossesb:passByValue : false/>, <wsa:ReferenceProperties jbossesb:type : urn:jboss/esb/epr/type/invm/> > ] RelatesTo: b013fa7a-18ac-40ef-bac5-7ad3ef2c6c5b ]
org.jboss.soa.esb.couriers.CourierException: No deliverAsync courier
at org.jboss.internal.soa.esb.couriers.TwoWayCourierImpl.deliver(TwoWayCourierImpl.java:170)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.messageTo(ActionProcessingPipeline.java:835)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.replyTo(ActionProcessingPipeline.java:757)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:687)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.processPipeline(ActionProcessingPipeline.java:574)
at org.jboss.soa.esb.listeners.message.ActionProcessingPipeline.process(ActionProcessingPipeline.java:408)
at org.jboss.soa.esb.listeners.message.MessageAwareListener$TransactionalRunner.run(MessageAwareListener.java:540)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:619)
When an JMS queue is configured in the first service, everything works like a charm.
--
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
15 years, 7 months