[jira] Updated: (AMQ-1078) Messages consumed with the Resource Adapter are intermittently not delivered
[ https://issues.apache.org/activemq/browse/AMQ-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christopher G. Stach II updated AMQ-1078: - Attachment: AMQ-1078.patch > Messages consumed with the Resource Adapter are intermittently not delivered > > > Key: AMQ-1078 > URL: https://issues.apache.org/activemq/browse/AMQ-1078 > Project: ActiveMQ > Issue Type: Bug > Components: Broker, Connector >Affects Versions: 4.0 >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.1.1, 4.2.0 > > Attachments: AMQ-1078.patch > > > The cause is that the ActiveMQSessionExecutor was starting and using it's > dispatch thread instead of the Thread managed by the resource adapter. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (AMQ-1078) Messages consumed with the Resource Adapter are intermittently not delivered
[ https://issues.apache.org/activemq/browse/AMQ-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37934 ] Christopher G. Stach II commented on AMQ-1078: -- Well, I pulled out the patch and applied it to 4.1.0 and it fixed the problem. > Messages consumed with the Resource Adapter are intermittently not delivered > > > Key: AMQ-1078 > URL: https://issues.apache.org/activemq/browse/AMQ-1078 > Project: ActiveMQ > Issue Type: Bug > Components: Broker, Connector >Affects Versions: 4.0 >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.1.1, 4.2.0 > > > The cause is that the ActiveMQSessionExecutor was starting and using it's > dispatch thread instead of the Thread managed by the resource adapter. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-1078) Messages consumed with the Resource Adapter are intermittently not delivered
[ https://issues.apache.org/activemq/browse/AMQ-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37861 ] Christopher G. Stach II commented on AMQ-1078: -- Is this "fixed, but not closed" or "not really fixed"? > Messages consumed with the Resource Adapter are intermittently not delivered > > > Key: AMQ-1078 > URL: https://issues.apache.org/activemq/browse/AMQ-1078 > Project: ActiveMQ > Issue Type: Bug > Components: Broker, Connector >Affects Versions: 4.0 >Reporter: Hiram Chirino > Assigned To: Hiram Chirino > Fix For: 4.1.1, 4.2.0 > > > The cause is that the ActiveMQSessionExecutor was starting and using it's > dispatch thread instead of the Thread managed by the resource adapter. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-767) avoid use of XHTML in activemq-web-console so things work great in IE 6
[ https://issues.apache.org/activemq/browse/AMQ-767?page=comments#action_37462 ] Christopher G. Stach II commented on AMQ-767: - IE 6 was doing the right thing. http://www.w3.org/TR/html4/interact/scripts.html#h-18.2.1 http://www.w3.org/TR/xhtml1/#guidelines > avoid use of XHTML in activemq-web-console so things work great in IE 6 > --- > > Key: AMQ-767 > URL: https://issues.apache.org/activemq/browse/AMQ-767 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 4.0.1 >Reporter: james strachan > Fix For: 4.2.0 > > Attachments: mainDecorator.patch > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-767) avoid use of XHTML in activemq-web-console so things work great in IE 6
[ https://issues.apache.org/activemq/browse/AMQ-767?page=comments#action_37219 ] Christopher G. Stach II commented on AMQ-767: - All of our XHTML works perfectly in IE 6. What's the issue? > avoid use of XHTML in activemq-web-console so things work great in IE 6 > --- > > Key: AMQ-767 > URL: https://issues.apache.org/activemq/browse/AMQ-767 > Project: ActiveMQ > Issue Type: Bug >Affects Versions: 4.0.1 >Reporter: james strachan > Fix For: 4.1 > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (AMQ-747) Redelivery backoff should add random delay for collision avoidance
Redelivery backoff should add random delay for collision avoidance -- Key: AMQ-747 URL: https://issues.apache.org/activemq/browse/AMQ-747 Project: ActiveMQ Type: Improvement Components: Connector Versions: 4.0 Reporter: Christopher G. Stach II If a rollback on two messages happens between three transactional deliveries, and the two messages are redelivered with the same redelivery backoff settings, there is a likelihood that both messages will cause another rollback to happen. If maximumRedeliveries is set too low, or there are a maximumRedeliveries + 1 messages coming in simultaneously, messages may never get delivered. Can we get another option for the clients that adds a random backoff delay adjustment in addition to the constant backoff delay factor? This would end up working like most other collision avoidance algorithms. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (AMQ-738) Broker does not recognize failed broker upon reconnect
[
https://issues.apache.org/activemq/browse/AMQ-738?page=comments#action_36267 ]
Christopher G. Stach II commented on AMQ-738:
-
Here's the broker config:
http://activemq.org/config/1.0";>
classpath:/application.properties
SYSTEM_PROPERTIES_MODE_OVERRIDE
multicast://${amq.serviceName}
${java.io.tmpdir}/${amq.dataDir}
2
vm://${amq.brokerName}
multicast://${amq.serviceName}
tcp://${amq.bindAddress}:${amq.bindPort}
> Broker does not recognize failed broker upon reconnect
> --
>
> Key: AMQ-738
> URL: https://issues.apache.org/activemq/browse/AMQ-738
> Project: ActiveMQ
> Type: Bug
> Components: Broker
> Versions: 4.0
> Reporter: Christopher G. Stach II
>
>
> After normal shutdown of a broker and bring it back up, the first broker
> reports this error:
> [11:07:15.162] Establishing network connection between from
> vm://app1-test?network=true to tcp://10.xxx:49995
> [11:07:15.165] Starting a network connection between vm://app1-test#20 and
> tcp://null:0 has been established.
> [11:07:15.294] Async error occurred: javax.jms.InvalidClientIDException:
> Broker: app1-test - Client: NC_app2-test_inboundapp1-test already connected
> [11:07:15.294] javax.jms.InvalidClientIDException: Broker: app1-test -
> Client: NC_app2-test_inboundapp1-test already connected
> [11:07:15.294] at
> org.apache.activemq.broker.region.RegionBroker.addConnection(RegionBroker.java:176)
> [11:07:15.294] at
> org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69)
> [11:07:15.294] at
> org.apache.activemq.advisory.AdvisoryBroker.addConnection(AdvisoryBroker.java:69)
> [11:07:15.294] at
> org.apache.activemq.broker.BrokerFilter.addConnection(BrokerFilter.java:69)
> [11:07:15.294] at
> org.apache.activemq.broker.MutableBrokerFilter.addConnection(MutableBrokerFilter.java:82)
> [11:07:15.294] at
> org.apache.activemq.broker.AbstractConnection.processAddConnection(AbstractConnection.java:507)
> [11:07:15.294] at
> org.apache.activemq.command.ConnectionInfo.visit(ConnectionInfo.java:118)
> [11:07:15.294] at
> org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:201)
> [11:07:15.294] at
> org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:62)
> [11:07:15.294] at
> org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:97)
> [11:07:15.294] at
> org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:63)
> [11:07:15.294] at
> org.apache.activemq.transport.vm.VMTransport.oneway(VMTransport.java:76)
> [11:07:15.294] at
> org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:44)
> [11:07:15.294] at
> org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60)
> [11:07:15.294] at
> org.apache.activemq.network.DemandForwardingBridgeSupport.startLocalBridge(DemandForwardingBridgeSupport.java:192)
> [11:07:15.294] at
> org.apache.activemq.network.DemandForwardingBridgeSupport$3.run(DemandForwardingBridgeSupport.java:162)
> [11:07:15.327] Network connection between vm://app1-test#20 and
> tcp://app2.xxx/10.xxx:49995(app2-test) has been established.
> [11:07:15.347] Unexpected local command: ConnectionError {commandId = 2,
> responseRequired = false, connectionId = null, exception =
> javax.jms.InvalidClientIDException: Broker: app1-test - Client:
> NC_app2-test_inboundapp1-test already connected}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (AMQ-731) Redeliveries don't work with resource adapter and Jencks
[ https://issues.apache.org/activemq/browse/AMQ-731?page=all ]
Christopher G. Stach II updated AMQ-731:
Attachment: amq-txcontext.patch
This simple patch fixes the whole problem.
> Redeliveries don't work with resource adapter and Jencks
>
>
> Key: AMQ-731
> URL: https://issues.apache.org/activemq/browse/AMQ-731
> Project: ActiveMQ
> Type: Bug
> Components: Connector
> Versions: 4.0
> Environment: Sun JDK 1.5.0_06, Jencks 1.1.3, AMQ 4.0, Resin Pro 3.0.14
> Reporter: Christopher G. Stach II
> Attachments: amq-txcontext.patch
>
>
> During a rollback in a JTA transaction, this exception is generated a few
> times:
> org.apache.activemq.broker.AbstractConnection.serviceException Async
> error occurred: javax.jms.JMSException: Could not correlate
> acknowledgment with dispatched message: MessageAck {commandId = 137,
> responseRequired = false, ackType = 1, consumerId =
> ID:xxx-2276-1148335783189-2:5:-1:2, firstMessageId =
> ID:xxx-2276-1148335783189-2:1:1:1:2, lastMessageId =
> ID:xxx-2276-1148335783189-2:1:1:1:2, destination = queue://xxxQueue,
> transactionId = null, messageCount = 1}
> javax.jms.JMSException: Could not correlate acknowledgment with
> dispatched message: MessageAck {commandId = 137, responseRequired =
> false, ackType = 1, consumerId = ID:xxx-2276-1148335783189-2:5:-1:2,
> firstMessageId = ID:xxx-2276-1148335783189-2:1:1:1:2, lastMessageId =
> ID:xxx-2276-1148335783189-2:1:1:1:2, destination = queue://xxxQueue,
> transactionId = null, messageCount = 1}
> at
> org.apache.activemq.broker.region.PrefetchSubscription.acknowledge(PrefetchSubscription.java:175)
> at
> org.apache.activemq.broker.region.AbstractRegion.acknowledge(AbstractRegion.java:233)
> at
> org.apache.activemq.broker.region.RegionBroker.acknowledge(RegionBroker.java:362)
> at
> org.apache.activemq.broker.TransactionBroker.acknowledge(TransactionBroker.java:176)
> at
> org.apache.activemq.broker.BrokerFilter.acknowledge(BrokerFilter.java:65)
> at
> org.apache.activemq.broker.BrokerFilter.acknowledge(BrokerFilter.java:65)
> at
> org.apache.activemq.broker.MutableBrokerFilter.acknowledge(MutableBrokerFilter.java:78)
> at
> org.apache.activemq.broker.AbstractConnection.processMessageAck(AbstractConnection.java:356)
> at org.apache.activemq.command.MessageAck.visit(MessageAck.java:178)
> at
> org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:201)
> at
> org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:62)
> at
> org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:97)
> at
> org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:63)
> at
> org.apache.activemq.transport.vm.VMTransport.oneway(VMTransport.java:76)
> at
> org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:44)
> at
> org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60)
> at
> org.apache.activemq.ActiveMQConnection.asyncSendPacket(ActiveMQConnection.java:)
> at
> org.apache.activemq.ActiveMQSession.asyncSendPacket(ActiveMQSession.java:1655)
> at
> org.apache.activemq.ActiveMQSession$2.afterRollback(ActiveMQSession.java:720)
> at
> org.apache.activemq.TransactionContext.afterRollback(TransactionContext.java:134)
> at
> org.apache.activemq.TransactionContext.rollback(TransactionContext.java:409)
> at
> org.apache.activemq.ra.LocalAndXATransaction.rollback(LocalAndXATransaction.java:126)
> at
> org.apache.geronimo.transaction.manager.WrapperNamedXAResource.rollback(WrapperNamedXAResource.java:78)
> at
> com.caucho.transaction.TransactionImpl.rollbackInt(TransactionImpl.java:787)
> at
> com.caucho.transaction.TransactionImpl.commit(TransactionImpl.java:560)
> at org.jencks.XAEndpoint.afterDelivery(XAEndpoint.java:103)
> at
> org.apache.activemq.ra.MessageEndpointProxy$MessageEndpointAlive.afterDelivery(MessageEndpointProxy.java:125)
> at
> org.apache.activemq.ra.MessageEndpointProxy.afterDelivery(MessageEndpointProxy.java:64)
> at
> org.apache.activemq.ra.ServerSessionImpl.afterDelivery(ServerSessionImpl.java:214)
> at org.apache.activemq.ActiveMQSession.run(ActiveMQSession.java:751)
> at
> org.apache.activemq.ra.ServerSessionImpl.run(ServerSessionImpl.java:163)
> at com.caucho.jca.WorkThread.run(WorkThread.java:99)
> at com.caucho.util.ThreadPool.runTasks(ThreadPool.java:490)
> at com.caucho.util.ThreadPool.run(ThreadPool.java:423)
> at java.lang.Thread.run(Thread.java:595)
> Note that the ackType is a poison ack. This shouldn't be the case as the
> configuration (below) on the
[jira] Commented: (AMQ-731) Redeliveries don't work with resource adapter and Jencks
[
https://issues.apache.org/activemq/browse/AMQ-731?page=comments#action_36242 ]
Christopher G. Stach II commented on AMQ-731:
-
It could be multiple transactions or multiple branches. For example, a single
database connection can support X number of concurrent transactions as well as
Y number of branches within each transaction. I assume that since Resin is the
application server, the transaction manager, and the JCA container, it is
calling end on the enlisted XAResources.
Check out the stack trace above. JBoss TreeCache is calling suspend on the TM
to do some work outside of the transaction (TreeCache.suspend() line: 101). We
use Hibernate's connection after_statement release mode, which is appropriate
for connections using JTA.
> Redeliveries don't work with resource adapter and Jencks
>
>
> Key: AMQ-731
> URL: https://issues.apache.org/activemq/browse/AMQ-731
> Project: ActiveMQ
> Type: Bug
> Components: Connector
> Versions: 4.0
> Environment: Sun JDK 1.5.0_06, Jencks 1.1.3, AMQ 4.0, Resin Pro 3.0.14
> Reporter: Christopher G. Stach II
>
>
> During a rollback in a JTA transaction, this exception is generated a few
> times:
> org.apache.activemq.broker.AbstractConnection.serviceException Async
> error occurred: javax.jms.JMSException: Could not correlate
> acknowledgment with dispatched message: MessageAck {commandId = 137,
> responseRequired = false, ackType = 1, consumerId =
> ID:xxx-2276-1148335783189-2:5:-1:2, firstMessageId =
> ID:xxx-2276-1148335783189-2:1:1:1:2, lastMessageId =
> ID:xxx-2276-1148335783189-2:1:1:1:2, destination = queue://xxxQueue,
> transactionId = null, messageCount = 1}
> javax.jms.JMSException: Could not correlate acknowledgment with
> dispatched message: MessageAck {commandId = 137, responseRequired =
> false, ackType = 1, consumerId = ID:xxx-2276-1148335783189-2:5:-1:2,
> firstMessageId = ID:xxx-2276-1148335783189-2:1:1:1:2, lastMessageId =
> ID:xxx-2276-1148335783189-2:1:1:1:2, destination = queue://xxxQueue,
> transactionId = null, messageCount = 1}
> at
> org.apache.activemq.broker.region.PrefetchSubscription.acknowledge(PrefetchSubscription.java:175)
> at
> org.apache.activemq.broker.region.AbstractRegion.acknowledge(AbstractRegion.java:233)
> at
> org.apache.activemq.broker.region.RegionBroker.acknowledge(RegionBroker.java:362)
> at
> org.apache.activemq.broker.TransactionBroker.acknowledge(TransactionBroker.java:176)
> at
> org.apache.activemq.broker.BrokerFilter.acknowledge(BrokerFilter.java:65)
> at
> org.apache.activemq.broker.BrokerFilter.acknowledge(BrokerFilter.java:65)
> at
> org.apache.activemq.broker.MutableBrokerFilter.acknowledge(MutableBrokerFilter.java:78)
> at
> org.apache.activemq.broker.AbstractConnection.processMessageAck(AbstractConnection.java:356)
> at org.apache.activemq.command.MessageAck.visit(MessageAck.java:178)
> at
> org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:201)
> at
> org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:62)
> at
> org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:97)
> at
> org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:63)
> at
> org.apache.activemq.transport.vm.VMTransport.oneway(VMTransport.java:76)
> at
> org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:44)
> at
> org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60)
> at
> org.apache.activemq.ActiveMQConnection.asyncSendPacket(ActiveMQConnection.java:)
> at
> org.apache.activemq.ActiveMQSession.asyncSendPacket(ActiveMQSession.java:1655)
> at
> org.apache.activemq.ActiveMQSession$2.afterRollback(ActiveMQSession.java:720)
> at
> org.apache.activemq.TransactionContext.afterRollback(TransactionContext.java:134)
> at
> org.apache.activemq.TransactionContext.rollback(TransactionContext.java:409)
> at
> org.apache.activemq.ra.LocalAndXATransaction.rollback(LocalAndXATransaction.java:126)
> at
> org.apache.geronimo.transaction.manager.WrapperNamedXAResource.rollback(WrapperNamedXAResource.java:78)
> at
> com.caucho.transaction.TransactionImpl.rollbackInt(TransactionImpl.java:787)
> at
> com.caucho.transaction.TransactionImpl.commit(TransactionImpl.java:560)
> at org.jencks.XAEndpoint.afterDelivery(XAEndpoint.java:103)
> at
> org.apache.activemq.ra.MessageEndpointProxy$MessageEndpointAlive.afterDelivery(MessageEndpointProxy.java:125)
> at
> org.apache.activemq.ra.MessageEndpointProxy.afterDelivery(MessageEndpointProxy.java:64)
> at
> org.apache.activemq.ra.ServerSessionImpl.afterDelivery(ServerSession
[jira] Commented: (AMQ-731) Redeliveries don't work with resource adapter and Jencks
[
https://issues.apache.org/activemq/browse/AMQ-731?page=comments#action_36238 ]
Christopher G. Stach II commented on AMQ-731:
-
Resin's TransactionImpl.suspend() method, which doesn't exist in Geronimo,
calls XAResource.end(Xid, XAResource.TMSUSPEND),
WrapperNamedXAResource.end(Xid, int) line: 51 in the above stack trace.
> Redeliveries don't work with resource adapter and Jencks
>
>
> Key: AMQ-731
> URL: https://issues.apache.org/activemq/browse/AMQ-731
> Project: ActiveMQ
> Type: Bug
> Components: Connector
> Versions: 4.0
> Environment: Sun JDK 1.5.0_06, Jencks 1.1.3, AMQ 4.0, Resin Pro 3.0.14
> Reporter: Christopher G. Stach II
>
>
> During a rollback in a JTA transaction, this exception is generated a few
> times:
> org.apache.activemq.broker.AbstractConnection.serviceException Async
> error occurred: javax.jms.JMSException: Could not correlate
> acknowledgment with dispatched message: MessageAck {commandId = 137,
> responseRequired = false, ackType = 1, consumerId =
> ID:xxx-2276-1148335783189-2:5:-1:2, firstMessageId =
> ID:xxx-2276-1148335783189-2:1:1:1:2, lastMessageId =
> ID:xxx-2276-1148335783189-2:1:1:1:2, destination = queue://xxxQueue,
> transactionId = null, messageCount = 1}
> javax.jms.JMSException: Could not correlate acknowledgment with
> dispatched message: MessageAck {commandId = 137, responseRequired =
> false, ackType = 1, consumerId = ID:xxx-2276-1148335783189-2:5:-1:2,
> firstMessageId = ID:xxx-2276-1148335783189-2:1:1:1:2, lastMessageId =
> ID:xxx-2276-1148335783189-2:1:1:1:2, destination = queue://xxxQueue,
> transactionId = null, messageCount = 1}
> at
> org.apache.activemq.broker.region.PrefetchSubscription.acknowledge(PrefetchSubscription.java:175)
> at
> org.apache.activemq.broker.region.AbstractRegion.acknowledge(AbstractRegion.java:233)
> at
> org.apache.activemq.broker.region.RegionBroker.acknowledge(RegionBroker.java:362)
> at
> org.apache.activemq.broker.TransactionBroker.acknowledge(TransactionBroker.java:176)
> at
> org.apache.activemq.broker.BrokerFilter.acknowledge(BrokerFilter.java:65)
> at
> org.apache.activemq.broker.BrokerFilter.acknowledge(BrokerFilter.java:65)
> at
> org.apache.activemq.broker.MutableBrokerFilter.acknowledge(MutableBrokerFilter.java:78)
> at
> org.apache.activemq.broker.AbstractConnection.processMessageAck(AbstractConnection.java:356)
> at org.apache.activemq.command.MessageAck.visit(MessageAck.java:178)
> at
> org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:201)
> at
> org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:62)
> at
> org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:97)
> at
> org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:63)
> at
> org.apache.activemq.transport.vm.VMTransport.oneway(VMTransport.java:76)
> at
> org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:44)
> at
> org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60)
> at
> org.apache.activemq.ActiveMQConnection.asyncSendPacket(ActiveMQConnection.java:)
> at
> org.apache.activemq.ActiveMQSession.asyncSendPacket(ActiveMQSession.java:1655)
> at
> org.apache.activemq.ActiveMQSession$2.afterRollback(ActiveMQSession.java:720)
> at
> org.apache.activemq.TransactionContext.afterRollback(TransactionContext.java:134)
> at
> org.apache.activemq.TransactionContext.rollback(TransactionContext.java:409)
> at
> org.apache.activemq.ra.LocalAndXATransaction.rollback(LocalAndXATransaction.java:126)
> at
> org.apache.geronimo.transaction.manager.WrapperNamedXAResource.rollback(WrapperNamedXAResource.java:78)
> at
> com.caucho.transaction.TransactionImpl.rollbackInt(TransactionImpl.java:787)
> at
> com.caucho.transaction.TransactionImpl.commit(TransactionImpl.java:560)
> at org.jencks.XAEndpoint.afterDelivery(XAEndpoint.java:103)
> at
> org.apache.activemq.ra.MessageEndpointProxy$MessageEndpointAlive.afterDelivery(MessageEndpointProxy.java:125)
> at
> org.apache.activemq.ra.MessageEndpointProxy.afterDelivery(MessageEndpointProxy.java:64)
> at
> org.apache.activemq.ra.ServerSessionImpl.afterDelivery(ServerSessionImpl.java:214)
> at org.apache.activemq.ActiveMQSession.run(ActiveMQSession.java:751)
> at
> org.apache.activemq.ra.ServerSessionImpl.run(ServerSessionImpl.java:163)
> at com.caucho.jca.WorkThread.run(WorkThread.java:99)
> at com.caucho.util.ThreadPool.runTasks(ThreadPool.java:490)
> at com.caucho.util.ThreadPool.run(ThreadPool.java:423)
> at java.lang.Thread.run(Thread.java
[jira] Commented: (AMQ-731) Redeliveries don't work with resource adapter and Jencks
[
https://issues.apache.org/activemq/browse/AMQ-731?page=comments#action_36237 ]
Christopher G. Stach II commented on AMQ-731:
-
Comparing Resin's and Geronmio's TransactionManagerImpl suspend methods,
Geronimo's doesn't even suspend the transaction. The test case I have could
probably never work, and it's no wonder that none of the AMQ developers have
come across this if testing is only done with Geronimo.
> Redeliveries don't work with resource adapter and Jencks
>
>
> Key: AMQ-731
> URL: https://issues.apache.org/activemq/browse/AMQ-731
> Project: ActiveMQ
> Type: Bug
> Components: Connector
> Versions: 4.0
> Environment: Sun JDK 1.5.0_06, Jencks 1.1.3, AMQ 4.0, Resin Pro 3.0.14
> Reporter: Christopher G. Stach II
>
>
> During a rollback in a JTA transaction, this exception is generated a few
> times:
> org.apache.activemq.broker.AbstractConnection.serviceException Async
> error occurred: javax.jms.JMSException: Could not correlate
> acknowledgment with dispatched message: MessageAck {commandId = 137,
> responseRequired = false, ackType = 1, consumerId =
> ID:xxx-2276-1148335783189-2:5:-1:2, firstMessageId =
> ID:xxx-2276-1148335783189-2:1:1:1:2, lastMessageId =
> ID:xxx-2276-1148335783189-2:1:1:1:2, destination = queue://xxxQueue,
> transactionId = null, messageCount = 1}
> javax.jms.JMSException: Could not correlate acknowledgment with
> dispatched message: MessageAck {commandId = 137, responseRequired =
> false, ackType = 1, consumerId = ID:xxx-2276-1148335783189-2:5:-1:2,
> firstMessageId = ID:xxx-2276-1148335783189-2:1:1:1:2, lastMessageId =
> ID:xxx-2276-1148335783189-2:1:1:1:2, destination = queue://xxxQueue,
> transactionId = null, messageCount = 1}
> at
> org.apache.activemq.broker.region.PrefetchSubscription.acknowledge(PrefetchSubscription.java:175)
> at
> org.apache.activemq.broker.region.AbstractRegion.acknowledge(AbstractRegion.java:233)
> at
> org.apache.activemq.broker.region.RegionBroker.acknowledge(RegionBroker.java:362)
> at
> org.apache.activemq.broker.TransactionBroker.acknowledge(TransactionBroker.java:176)
> at
> org.apache.activemq.broker.BrokerFilter.acknowledge(BrokerFilter.java:65)
> at
> org.apache.activemq.broker.BrokerFilter.acknowledge(BrokerFilter.java:65)
> at
> org.apache.activemq.broker.MutableBrokerFilter.acknowledge(MutableBrokerFilter.java:78)
> at
> org.apache.activemq.broker.AbstractConnection.processMessageAck(AbstractConnection.java:356)
> at org.apache.activemq.command.MessageAck.visit(MessageAck.java:178)
> at
> org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:201)
> at
> org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:62)
> at
> org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:97)
> at
> org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:63)
> at
> org.apache.activemq.transport.vm.VMTransport.oneway(VMTransport.java:76)
> at
> org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:44)
> at
> org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60)
> at
> org.apache.activemq.ActiveMQConnection.asyncSendPacket(ActiveMQConnection.java:)
> at
> org.apache.activemq.ActiveMQSession.asyncSendPacket(ActiveMQSession.java:1655)
> at
> org.apache.activemq.ActiveMQSession$2.afterRollback(ActiveMQSession.java:720)
> at
> org.apache.activemq.TransactionContext.afterRollback(TransactionContext.java:134)
> at
> org.apache.activemq.TransactionContext.rollback(TransactionContext.java:409)
> at
> org.apache.activemq.ra.LocalAndXATransaction.rollback(LocalAndXATransaction.java:126)
> at
> org.apache.geronimo.transaction.manager.WrapperNamedXAResource.rollback(WrapperNamedXAResource.java:78)
> at
> com.caucho.transaction.TransactionImpl.rollbackInt(TransactionImpl.java:787)
> at
> com.caucho.transaction.TransactionImpl.commit(TransactionImpl.java:560)
> at org.jencks.XAEndpoint.afterDelivery(XAEndpoint.java:103)
> at
> org.apache.activemq.ra.MessageEndpointProxy$MessageEndpointAlive.afterDelivery(MessageEndpointProxy.java:125)
> at
> org.apache.activemq.ra.MessageEndpointProxy.afterDelivery(MessageEndpointProxy.java:64)
> at
> org.apache.activemq.ra.ServerSessionImpl.afterDelivery(ServerSessionImpl.java:214)
> at org.apache.activemq.ActiveMQSession.run(ActiveMQSession.java:751)
> at
> org.apache.activemq.ra.ServerSessionImpl.run(ServerSessionImpl.java:163)
> at com.caucho.jca.WorkThread.run(WorkThread.java:99)
> at com.caucho.util.ThreadPool.runTasks(ThreadPool.java:490)
> at com.caucho.
[jira] Commented: (AMQ-731) Redeliveries don't work with resource adapter and Jencks
[
https://issues.apache.org/activemq/browse/AMQ-731?page=comments#action_36229 ]
Christopher G. Stach II commented on AMQ-731:
-
So, with that being said, should endedXATransactionContexts actually be a Map
of LinkedHashSets?
> Redeliveries don't work with resource adapter and Jencks
>
>
> Key: AMQ-731
> URL: https://issues.apache.org/activemq/browse/AMQ-731
> Project: ActiveMQ
> Type: Bug
> Components: Connector
> Versions: 4.0
> Environment: Sun JDK 1.5.0_06, Jencks 1.1.3, AMQ 4.0, Resin Pro 3.0.14
> Reporter: Christopher G. Stach II
>
>
> During a rollback in a JTA transaction, this exception is generated a few
> times:
> org.apache.activemq.broker.AbstractConnection.serviceException Async
> error occurred: javax.jms.JMSException: Could not correlate
> acknowledgment with dispatched message: MessageAck {commandId = 137,
> responseRequired = false, ackType = 1, consumerId =
> ID:xxx-2276-1148335783189-2:5:-1:2, firstMessageId =
> ID:xxx-2276-1148335783189-2:1:1:1:2, lastMessageId =
> ID:xxx-2276-1148335783189-2:1:1:1:2, destination = queue://xxxQueue,
> transactionId = null, messageCount = 1}
> javax.jms.JMSException: Could not correlate acknowledgment with
> dispatched message: MessageAck {commandId = 137, responseRequired =
> false, ackType = 1, consumerId = ID:xxx-2276-1148335783189-2:5:-1:2,
> firstMessageId = ID:xxx-2276-1148335783189-2:1:1:1:2, lastMessageId =
> ID:xxx-2276-1148335783189-2:1:1:1:2, destination = queue://xxxQueue,
> transactionId = null, messageCount = 1}
> at
> org.apache.activemq.broker.region.PrefetchSubscription.acknowledge(PrefetchSubscription.java:175)
> at
> org.apache.activemq.broker.region.AbstractRegion.acknowledge(AbstractRegion.java:233)
> at
> org.apache.activemq.broker.region.RegionBroker.acknowledge(RegionBroker.java:362)
> at
> org.apache.activemq.broker.TransactionBroker.acknowledge(TransactionBroker.java:176)
> at
> org.apache.activemq.broker.BrokerFilter.acknowledge(BrokerFilter.java:65)
> at
> org.apache.activemq.broker.BrokerFilter.acknowledge(BrokerFilter.java:65)
> at
> org.apache.activemq.broker.MutableBrokerFilter.acknowledge(MutableBrokerFilter.java:78)
> at
> org.apache.activemq.broker.AbstractConnection.processMessageAck(AbstractConnection.java:356)
> at org.apache.activemq.command.MessageAck.visit(MessageAck.java:178)
> at
> org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:201)
> at
> org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:62)
> at
> org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:97)
> at
> org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:63)
> at
> org.apache.activemq.transport.vm.VMTransport.oneway(VMTransport.java:76)
> at
> org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:44)
> at
> org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60)
> at
> org.apache.activemq.ActiveMQConnection.asyncSendPacket(ActiveMQConnection.java:)
> at
> org.apache.activemq.ActiveMQSession.asyncSendPacket(ActiveMQSession.java:1655)
> at
> org.apache.activemq.ActiveMQSession$2.afterRollback(ActiveMQSession.java:720)
> at
> org.apache.activemq.TransactionContext.afterRollback(TransactionContext.java:134)
> at
> org.apache.activemq.TransactionContext.rollback(TransactionContext.java:409)
> at
> org.apache.activemq.ra.LocalAndXATransaction.rollback(LocalAndXATransaction.java:126)
> at
> org.apache.geronimo.transaction.manager.WrapperNamedXAResource.rollback(WrapperNamedXAResource.java:78)
> at
> com.caucho.transaction.TransactionImpl.rollbackInt(TransactionImpl.java:787)
> at
> com.caucho.transaction.TransactionImpl.commit(TransactionImpl.java:560)
> at org.jencks.XAEndpoint.afterDelivery(XAEndpoint.java:103)
> at
> org.apache.activemq.ra.MessageEndpointProxy$MessageEndpointAlive.afterDelivery(MessageEndpointProxy.java:125)
> at
> org.apache.activemq.ra.MessageEndpointProxy.afterDelivery(MessageEndpointProxy.java:64)
> at
> org.apache.activemq.ra.ServerSessionImpl.afterDelivery(ServerSessionImpl.java:214)
> at org.apache.activemq.ActiveMQSession.run(ActiveMQSession.java:751)
> at
> org.apache.activemq.ra.ServerSessionImpl.run(ServerSessionImpl.java:163)
> at com.caucho.jca.WorkThread.run(WorkThread.java:99)
> at com.caucho.util.ThreadPool.runTasks(ThreadPool.java:490)
> at com.caucho.util.ThreadPool.run(ThreadPool.java:423)
> at java.lang.Thread.run(Thread.java:595)
> Note that the ackType is a poison ack. This shouldn't be the case as the
> configuration (b
[jira] Commented: (AMQ-731) Redeliveries don't work with resource adapter and Jencks
[ https://issues.apache.org/activemq/browse/AMQ-731?page=comments#action_36228 ] Christopher G. Stach II commented on AMQ-731: - Okay, this is the stack trace with a breakpoint put at TransactionContext line 560. It happens over and over and over, each time the transaction is suspended. Thread [resin-30] (Suspended (breakpoint at line 560 in TransactionContext)) TransactionContext.setXid(Xid) line: 560 TransactionContext.end(Xid, int) line: 327 LocalAndXATransaction.end(Xid, int) line: 89 WrapperNamedXAResource.end(Xid, int) line: 51 TransactionImpl.suspend() line: 448 TransactionManagerImpl.suspend() line: 201 TreeCache.suspend() line: 101 TreeCache.put(Object, Object) line: 71 UpdateTimestampsCache.preinvalidate(Serializable[]) line: 54 ActionQueue.execute(Executable) line: 244 DefaultSaveOrUpdateEventListener(AbstractSaveEventListener).performSaveOrReplicate(Object, EntityKey, EntityPersister, boolean, Object, EventSource, boolean) line: 290 DefaultSaveOrUpdateEventListener(AbstractSaveEventListener).performSave(Object, Serializable, EntityPersister, boolean, Object, EventSource, boolean) line: 180 DefaultSaveOrUpdateEventListener(AbstractSaveEventListener).saveWithGeneratedId(Object, String, Object, EventSource, boolean) line: 108 DefaultSaveOrUpdateEventListener.saveWithGeneratedOrRequestedId(SaveOrUpdateEvent) line: 186 DefaultSaveOrUpdateEventListener.entityIsTransient(SaveOrUpdateEvent) line: 175 DefaultSaveOrUpdateEventListener.performSaveOrUpdate(SaveOrUpdateEvent) line: 98 DefaultSaveOrUpdateEventListener.onSaveOrUpdate(SaveOrUpdateEvent) line: 70 SessionImpl.fireSaveOrUpdate(SaveOrUpdateEvent) line: 509 SessionImpl.saveOrUpdate(String, Object) line: 501 SessionImpl.saveOrUpdate(Object) line: 497 HibernateTemplate$18.doInHibernate(Session) line: 693 HibernateTemplate.execute(HibernateCallback, boolean) line: 366 HibernateTemplate.saveOrUpdate(Object) line: 690 LeadDAOImpl(AbstractDAOImpl).saveOrUpdate(E) line: 281 NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] NativeMethodAccessorImpl.invoke(Object, Object[]) line: 39 DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25 Method.invoke(Object, Object...) line: 585 AopUtils.invokeJoinpointUsingReflection(Object, Method, Object[]) line: 287 ReflectiveMethodInvocation.invokeJoinpoint() line: 181 ReflectiveMethodInvocation.proceed() line: 148 TransactionInterceptor.invoke(MethodInvocation) line: 96 ReflectiveMethodInvocation.proceed() line: 170 JdkDynamicAopProxy.invoke(Object, Method, Object[]) line: 176 $Proxy46.saveOrUpdate(Object) line: not available RefinanceLeadImpl(LeadImpl).save() line: 545 ProcessorImpl.processLead(DistributionContext, Lead) line: 126 NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] NativeMethodAccessorImpl.invoke(Object, Object[]) line: 39 DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25 Method.invoke(Object, Object...) line: 585 AopUtils.invokeJoinpointUsingReflection(Object, Method, Object[]) line: 287 ReflectiveMethodInvocation.invokeJoinpoint() line: 181 ReflectiveMethodInvocation.proceed() line: 148 TransactionInterceptor.invoke(MethodInvocation) line: 96 ReflectiveMethodInvocation.proceed() line: 170 JdkDynamicAopProxy.invoke(Object, Method, Object[]) line: 176 $Proxy74.processLead(DistributionContext, Lead) line: not available ProcessorFacadeImpl$1.run() line: 92 ProcessorFacadeImpl(DistributionContextWrapper).wrap(DistributionContextWrapper$DistributionContextRunnable) line: 124 ProcessorFacadeImpl.processLead(Lead) line: 89 NativeMethodAccessorImpl.invoke0(Method, Object, Object[]) line: not available [native method] NativeMethodAccessorImpl.invoke(Object, Object[]) line: 39 DelegatingMethodAccessorImpl.invoke(Object, Object[]) line: 25 Method.invoke(Object, Object...) line: 585 AopUtils.invokeJoinpointUsingReflection(Object, Method, Object[]) line: 287 ReflectiveMethodInvocation.invokeJoinpoint() line: 181 ReflectiveMethodInvocation.proceed() line: 148 TransactionInterceptor.invoke(MethodInvocation) line: 96 ReflectiveMethodInvocation.proceed() line: 170 JdkDynamicAopProxy.invoke(Object, Method, Object[])
[jira] Commented: (AMQ-731) Redeliveries don't work with resource adapter and Jencks
[
https://issues.apache.org/activemq/browse/AMQ-731?page=comments#action_36227 ]
Christopher G. Stach II commented on AMQ-731:
-
Oh, I should add, that once the redeliveries are exhausted, it ends up getting
a ConnectionClosedException and jumping down to TransactionContext line 414.
> Redeliveries don't work with resource adapter and Jencks
>
>
> Key: AMQ-731
> URL: https://issues.apache.org/activemq/browse/AMQ-731
> Project: ActiveMQ
> Type: Bug
> Components: Connector
> Versions: 4.0
> Environment: Sun JDK 1.5.0_06, Jencks 1.1.3, AMQ 4.0, Resin Pro 3.0.14
> Reporter: Christopher G. Stach II
>
>
> During a rollback in a JTA transaction, this exception is generated a few
> times:
> org.apache.activemq.broker.AbstractConnection.serviceException Async
> error occurred: javax.jms.JMSException: Could not correlate
> acknowledgment with dispatched message: MessageAck {commandId = 137,
> responseRequired = false, ackType = 1, consumerId =
> ID:xxx-2276-1148335783189-2:5:-1:2, firstMessageId =
> ID:xxx-2276-1148335783189-2:1:1:1:2, lastMessageId =
> ID:xxx-2276-1148335783189-2:1:1:1:2, destination = queue://xxxQueue,
> transactionId = null, messageCount = 1}
> javax.jms.JMSException: Could not correlate acknowledgment with
> dispatched message: MessageAck {commandId = 137, responseRequired =
> false, ackType = 1, consumerId = ID:xxx-2276-1148335783189-2:5:-1:2,
> firstMessageId = ID:xxx-2276-1148335783189-2:1:1:1:2, lastMessageId =
> ID:xxx-2276-1148335783189-2:1:1:1:2, destination = queue://xxxQueue,
> transactionId = null, messageCount = 1}
> at
> org.apache.activemq.broker.region.PrefetchSubscription.acknowledge(PrefetchSubscription.java:175)
> at
> org.apache.activemq.broker.region.AbstractRegion.acknowledge(AbstractRegion.java:233)
> at
> org.apache.activemq.broker.region.RegionBroker.acknowledge(RegionBroker.java:362)
> at
> org.apache.activemq.broker.TransactionBroker.acknowledge(TransactionBroker.java:176)
> at
> org.apache.activemq.broker.BrokerFilter.acknowledge(BrokerFilter.java:65)
> at
> org.apache.activemq.broker.BrokerFilter.acknowledge(BrokerFilter.java:65)
> at
> org.apache.activemq.broker.MutableBrokerFilter.acknowledge(MutableBrokerFilter.java:78)
> at
> org.apache.activemq.broker.AbstractConnection.processMessageAck(AbstractConnection.java:356)
> at org.apache.activemq.command.MessageAck.visit(MessageAck.java:178)
> at
> org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:201)
> at
> org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:62)
> at
> org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:97)
> at
> org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:63)
> at
> org.apache.activemq.transport.vm.VMTransport.oneway(VMTransport.java:76)
> at
> org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:44)
> at
> org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60)
> at
> org.apache.activemq.ActiveMQConnection.asyncSendPacket(ActiveMQConnection.java:)
> at
> org.apache.activemq.ActiveMQSession.asyncSendPacket(ActiveMQSession.java:1655)
> at
> org.apache.activemq.ActiveMQSession$2.afterRollback(ActiveMQSession.java:720)
> at
> org.apache.activemq.TransactionContext.afterRollback(TransactionContext.java:134)
> at
> org.apache.activemq.TransactionContext.rollback(TransactionContext.java:409)
> at
> org.apache.activemq.ra.LocalAndXATransaction.rollback(LocalAndXATransaction.java:126)
> at
> org.apache.geronimo.transaction.manager.WrapperNamedXAResource.rollback(WrapperNamedXAResource.java:78)
> at
> com.caucho.transaction.TransactionImpl.rollbackInt(TransactionImpl.java:787)
> at
> com.caucho.transaction.TransactionImpl.commit(TransactionImpl.java:560)
> at org.jencks.XAEndpoint.afterDelivery(XAEndpoint.java:103)
> at
> org.apache.activemq.ra.MessageEndpointProxy$MessageEndpointAlive.afterDelivery(MessageEndpointProxy.java:125)
> at
> org.apache.activemq.ra.MessageEndpointProxy.afterDelivery(MessageEndpointProxy.java:64)
> at
> org.apache.activemq.ra.ServerSessionImpl.afterDelivery(ServerSessionImpl.java:214)
> at org.apache.activemq.ActiveMQSession.run(ActiveMQSession.java:751)
> at
> org.apache.activemq.ra.ServerSessionImpl.run(ServerSessionImpl.java:163)
> at com.caucho.jca.WorkThread.run(WorkThread.java:99)
> at com.caucho.util.ThreadPool.runTasks(ThreadPool.java:490)
> at com.caucho.util.ThreadPool.run(ThreadPool.java:423)
> at java.lang.Thread.run(Thread.java:595)
> Note that the ackType is a poison
[jira] Commented: (AMQ-731) Redeliveries don't work with resource adapter and Jencks
[
https://issues.apache.org/activemq/browse/AMQ-731?page=comments#action_36226 ]
Christopher G. Stach II commented on AMQ-731:
-
Okay, here's a bit more information. While stepping through a rollback, I've
found l.elementData in TransactionContext.rollback(Xid) to contain 24 entries
for the _same_ TransactionContext. The loop at line 407 iterates over all of
these, calling afterRollback on each. afterRollback calls
Synchronization.afterRollback at ActiveMQSession line 706 where redelivery is
evaluated. Since max redeliveries is set at 9 and there are 24 entries, the
redeliveries are exhausted before this loop completes.
So, the question is, why 24 entries?
> Redeliveries don't work with resource adapter and Jencks
>
>
> Key: AMQ-731
> URL: https://issues.apache.org/activemq/browse/AMQ-731
> Project: ActiveMQ
> Type: Bug
> Components: Connector
> Versions: 4.0
> Environment: Sun JDK 1.5.0_06, Jencks 1.1.3, AMQ 4.0, Resin Pro 3.0.14
> Reporter: Christopher G. Stach II
>
>
> During a rollback in a JTA transaction, this exception is generated a few
> times:
> org.apache.activemq.broker.AbstractConnection.serviceException Async
> error occurred: javax.jms.JMSException: Could not correlate
> acknowledgment with dispatched message: MessageAck {commandId = 137,
> responseRequired = false, ackType = 1, consumerId =
> ID:xxx-2276-1148335783189-2:5:-1:2, firstMessageId =
> ID:xxx-2276-1148335783189-2:1:1:1:2, lastMessageId =
> ID:xxx-2276-1148335783189-2:1:1:1:2, destination = queue://xxxQueue,
> transactionId = null, messageCount = 1}
> javax.jms.JMSException: Could not correlate acknowledgment with
> dispatched message: MessageAck {commandId = 137, responseRequired =
> false, ackType = 1, consumerId = ID:xxx-2276-1148335783189-2:5:-1:2,
> firstMessageId = ID:xxx-2276-1148335783189-2:1:1:1:2, lastMessageId =
> ID:xxx-2276-1148335783189-2:1:1:1:2, destination = queue://xxxQueue,
> transactionId = null, messageCount = 1}
> at
> org.apache.activemq.broker.region.PrefetchSubscription.acknowledge(PrefetchSubscription.java:175)
> at
> org.apache.activemq.broker.region.AbstractRegion.acknowledge(AbstractRegion.java:233)
> at
> org.apache.activemq.broker.region.RegionBroker.acknowledge(RegionBroker.java:362)
> at
> org.apache.activemq.broker.TransactionBroker.acknowledge(TransactionBroker.java:176)
> at
> org.apache.activemq.broker.BrokerFilter.acknowledge(BrokerFilter.java:65)
> at
> org.apache.activemq.broker.BrokerFilter.acknowledge(BrokerFilter.java:65)
> at
> org.apache.activemq.broker.MutableBrokerFilter.acknowledge(MutableBrokerFilter.java:78)
> at
> org.apache.activemq.broker.AbstractConnection.processMessageAck(AbstractConnection.java:356)
> at org.apache.activemq.command.MessageAck.visit(MessageAck.java:178)
> at
> org.apache.activemq.broker.AbstractConnection.service(AbstractConnection.java:201)
> at
> org.apache.activemq.broker.TransportConnection$1.onCommand(TransportConnection.java:62)
> at
> org.apache.activemq.transport.ResponseCorrelator.onCommand(ResponseCorrelator.java:97)
> at
> org.apache.activemq.transport.TransportFilter.onCommand(TransportFilter.java:63)
> at
> org.apache.activemq.transport.vm.VMTransport.oneway(VMTransport.java:76)
> at
> org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:44)
> at
> org.apache.activemq.transport.ResponseCorrelator.oneway(ResponseCorrelator.java:60)
> at
> org.apache.activemq.ActiveMQConnection.asyncSendPacket(ActiveMQConnection.java:)
> at
> org.apache.activemq.ActiveMQSession.asyncSendPacket(ActiveMQSession.java:1655)
> at
> org.apache.activemq.ActiveMQSession$2.afterRollback(ActiveMQSession.java:720)
> at
> org.apache.activemq.TransactionContext.afterRollback(TransactionContext.java:134)
> at
> org.apache.activemq.TransactionContext.rollback(TransactionContext.java:409)
> at
> org.apache.activemq.ra.LocalAndXATransaction.rollback(LocalAndXATransaction.java:126)
> at
> org.apache.geronimo.transaction.manager.WrapperNamedXAResource.rollback(WrapperNamedXAResource.java:78)
> at
> com.caucho.transaction.TransactionImpl.rollbackInt(TransactionImpl.java:787)
> at
> com.caucho.transaction.TransactionImpl.commit(TransactionImpl.java:560)
> at org.jencks.XAEndpoint.afterDelivery(XAEndpoint.java:103)
> at
> org.apache.activemq.ra.MessageEndpointProxy$MessageEndpointAlive.afterDelivery(MessageEndpointProxy.java:125)
> at
> org.apache.activemq.ra.MessageEndpointProxy.afterDelivery(MessageEndpointProxy.java:64)
> at
> org.apache.activemq.ra.ServerSessionImpl.afterDelivery(ServerSessionImpl.java:214)
> at org.apache.activemq.ActiveMQSession.run(ActiveMQS
