You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Aman Nanner (JIRA)" <ji...@apache.org> on 2007/08/31 16:46:32 UTC

[jira] Commented: (GERONIMO-2880) TransportDisposedIOException occurs when trying to close ActiveMQ queue

    [ https://issues.apache.org/jira/browse/GERONIMO-2880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12524101 ] 

Aman Nanner commented on GERONIMO-2880:
---------------------------------------

This issue is occuring when we try to close a Queue.

{panel}
10:42:34,957 ERROR [Transaction] Unexpected exception rolling back org.apache.geronimo.transaction.manager.WrapperNamedXAResource@70e59f; continuing with rollback
javax.transaction.xa.XAException: Peer (vm://localhost#79) disposed.
	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:127)
	at org.apache.geronimo.transaction.manager.WrapperNamedXAResource.rollback(WrapperNamedXAResource.java:78)
	at org.apache.geronimo.transaction.manager.TransactionImpl.rollbackResources(TransactionImpl.java:581)
	at org.apache.geronimo.transaction.manager.TransactionImpl.rollback(TransactionImpl.java:475)
	at org.apache.geronimo.transaction.manager.TransactionManagerImpl.rollback(TransactionManagerImpl.java:250)
	at org.apache.geronimo.transaction.manager.TransactionManagerImpl$$FastClassByCGLIB$$14ee5fe0.invoke(<generated>)
	at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53)
	at org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38)
	at org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124)
	at org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:830)
	at org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57)
	at org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35)
	at org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96)
	at org.apache.geronimo.transaction.manager.XidImporter$$EnhancerByCGLIB$$abb1517c.rollback(<generated>)
	at org.apache.geronimo.transaction.GeronimoUserTransaction.rollback(GeronimoUserTransaction.java:74)
.................
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
	at org.apache.geronimo.tomcat.valve.DefaultSubjectValve.invoke(DefaultSubjectValve.java:56)
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:525)
	at org.apache.geronimo.tomcat.GeronimoStandardContext$SystemMethodValve.invoke(GeronimoStandardContext.java:353)
	at org.apache.geronimo.tomcat.valve.GeronimoBeforeAfterValve.invoke(GeronimoBeforeAfterValve.java:47)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
	at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:393)
	at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:563)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261)
	at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
	at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:581)
	at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
	at java.lang.Thread.run(Thread.java:595)
Caused by: javax.jms.JMSException: Peer (vm://localhost#79) disposed.
	at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:58)
	at org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1185)
	at org.apache.activemq.TransactionContext.rollback(TransactionContext.java:409)
	... 62 more
Caused by: org.apache.activemq.transport.TransportDisposedIOException: Peer (vm://localhost#79) disposed.
	at org.apache.activemq.transport.vm.VMTransport.oneway(VMTransport.java:86)
	at org.apache.activemq.transport.MutexTransport.oneway(MutexTransport.java:47)
	at org.apache.activemq.transport.ResponseCorrelator.asyncRequest(ResponseCorrelator.java:69)
	at org.apache.activemq.transport.ResponseCorrelator.request(ResponseCorrelator.java:74)
	at org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1175)
	... 63 more
{panel}

> TransportDisposedIOException occurs when trying to close ActiveMQ queue
> -----------------------------------------------------------------------
>
>                 Key: GERONIMO-2880
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-2880
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: ActiveMQ
>    Affects Versions: 2.0.x
>         Environment: Windows XP SP2
>            Reporter: Aman Nanner
>            Priority: Critical
>             Fix For: 2.0.x, 2.1
>
>
> I have discovered some problems with queues while running unittest in our own J2EE app.
> After sending a message on a queue, when we try to call the close() method on the queue, we get the following exception:
> ----
> org.apache.activemq.transport.TransportDisposedIOException: Peer (vm://localhost#69) disposed.
> ----
> where the number after "localhost" is different every time.
> We do not experience this problem with topics.  We are using ActiveMQ as part of an "embedded" configuration with Geronimo.
> I've done some debugging and the problem occurs at this line in the ActiveMQMessageProducer.close() method:
> ----
> this.session.asyncSendPacket(info.createRemoveCommand());
> ----
> The queue itself is disposed properly in the dispose() method that is called in the line before, but this sending of the asynchronous packet fails.

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