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/03/09 23:49:09 UTC

[jira] Resolved: (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:all-tabpanel ]

Aman Nanner resolved GERONIMO-2880.
-----------------------------------

       Resolution: Invalid
    Fix Version/s: 1.2

This issue seems to have resolved itself with an update to the latest ActiveMQ 4.1 snapshot.

> 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: 1.2
>         Environment: Windows XP SP2
>            Reporter: Aman Nanner
>             Fix For: 1.2
>
>
> 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.