[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-dev
Subject:    [jira] Resolved: (AMQ-839) Opening a connection after closing a
From:       "james strachan (JIRA)" <jira () apache ! org>
Date:       2006-07-29 8:06:23
Message-ID: 16334650.1154160383316.JavaMail.jira () brutus
[Download RAW message or body]

     [ 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

        


[prev in list] [next in list] [prev in thread] [next in thread]