activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "james strachan (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (AMQ-839) Opening a connection after closing a connectoin with the same clientid sometimes fails
Date Sat, 29 Jul 2006 08:06:23 GMT
     [ https://issues.apache.org/activemq/browse/AMQ-839?page=all ]

james strachan resolved AMQ-839.
--------------------------------

    Fix Version/s: 4.1
       Resolution: Fixed

Patch applied. Could you try reproduce the issue? Let us know if its not fixed and we can
reopen. If its not fixed, a JUnit test case would help us know for sure if we've fixed it:)

> Opening a connection after closing a connectoin with the same clientid sometimes fails
> --------------------------------------------------------------------------------------
>
>                 Key: AMQ-839
>                 URL: https://issues.apache.org/activemq/browse/AMQ-839
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 4.0.1
>         Environment: Linux Red Hat Enterprise 4
>            Reporter: Christopher Mihaly
>             Fix For: 4.1
>
>
> If a client closes a connection, and then fairly quicly tries to open a connection with
the same clientid, this sometimes fails.  Apparently, the connection is not completely closed
on the broker when the close on the connection completes.  This allows the client to try to
open a conection and receive a client already connected exception.   The close connection
should not return until the connection is actually closed, or at least an attribute on the
collection should allow for setting if you want to wait or not.

-- 
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

        

Mime
View raw message