You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Oliver Treichel (JIRA)" <ji...@apache.org> on 2008/06/18 21:56:01 UTC

[jira] Commented: (AMQ-1431) The connection is already closed at MDB's rollback in ra

    [ https://issues.apache.org/activemq/browse/AMQ-1431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=43566#action_43566 ] 

Oliver Treichel commented on AMQ-1431:
--------------------------------------

Same issue with OpenEJB 3.0 and ActiveMQ 5.1.0

> The connection is already closed at MDB's rollback in ra
> --------------------------------------------------------
>
>                 Key: AMQ-1431
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1431
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Connector
>    Affects Versions: 4.1.1
>         Environment: OC4J 10.1.3.2, OC4J 10.1.3.3, Oracle AS 10.1.3.2
>            Reporter: Igor Kim
>            Priority: Critical
>         Attachments: ejb-jar.xml, orion-ejb-jar.xml, Test2MDB.java
>
>
> The exception occures in RA during rollback and causes message loss
> javax.transaction.xa.XAException: The connection is already closed
>       at org.apache.activemq.TransactionContext.toXAException(TransactionContext.java:619)
>       at org.apache.activemq.TransactionContext.rollback(TransactionContext.java:420)
>       at org.apache.activemq.ra.LocalAndXATransaction.rollback(LocalAndXATransaction.java:129)
>       at oracle.j2ee.connector.transaction.XAResourceWrapper.rollback(XAResourceWrapper.java:156)
>       at com.evermind.server.TransactionEnlistment.rollback(TransactionEnlistment.java:76)
>       at com.evermind.server.ApplicationServerTransaction.rollbackResource(ApplicationServerTransaction.java:580)
>       at com.evermind.server.ApplicationServerTransaction.rollbackResources(ApplicationServerTransaction.java:567)
>       at com.evermind.server.ApplicationServerTransaction.rollback(ApplicationServerTransaction.java:544)
>       at com.evermind.server.ApplicationServerTransaction.rollback(ApplicationServerTransaction.java:527)
>       at com.evermind.server.ApplicationServerTransactionManager.rollback(ApplicationServerTransactionManager.java:439)
>       at com.evermind.server.ejb.EJBTransactionManager.end(EJBTransactionManager.java:129)
>       at com.evermind.server.ejb.MessageDrivenHome.afterDelivery(MessageDrivenHome.java:968)
>       at oracle.j2ee.connector.messageinflow.MessageEndpointBaseState.afterDelivery(MessageEndpointBaseState.java:93)
>       at oracle.j2ee.connector.messageinflow.MessageEndpointWaitingForAfterDeliveryState.afterDelivery(MessageEndpointWaitingForAfterDeliveryState.java:30)
>       at oracle.j2ee.connector.messageinflow.MessageEndpointImpl.afterDelivery(MessageEndpointImpl.java:202)
>       at org.apache.activemq.ra.MessageEndpointProxy$MessageEndpointAlive.afterDelivery(MessageEndpointProxy.java:126)
>       at org.apache.activemq.ra.MessageEndpointProxy.afterDelivery(MessageEndpointProxy.java:65)
>       at org.apache.activemq.ra.ServerSessionImpl.afterDelivery(ServerSessionImpl.java:216)
>       at org.apache.activemq.ActiveMQSession.run(ActiveMQSession.java:751)
>       at org.apache.activemq.ra.ServerSessionImpl.run(ServerSessionImpl.java:165)
>       at oracle.j2ee.connector.work.WorkWrapper.runTargetWork(WorkWrapper.java:242)
>       at oracle.j2ee.connector.work.WorkWrapper.doWork(WorkWrapper.java:215)
>       at oracle.j2ee.connector.work.WorkWrapper.run(WorkWrapper.java:190)
>       at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:819)
>       at java.lang.Thread.run(Thread.java:595)
> Caused by: org.apache.activemq.ConnectionClosedException: The connection is already closed
>       at org.apache.activemq.ActiveMQConnection.checkClosed(ActiveMQConnection.java:1245)
>       at org.apache.activemq.ActiveMQConnection.checkClosedOrFailed(ActiveMQConnection.java:1232)
>       at org.apache.activemq.TransactionContext.rollback(TransactionContext.java:404)
>       ... 23 more

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.