[
https://issues.apache.org/jira/browse/QPID-3520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robbie Gemmell updated QPID-3520:
---------------------------------
Description: It appears that the failover process can effectively start the
Connection during failover if it was currently stopped, as it starts the
Dispatcher thread in the Session implementation to clean the pre-dispatch
queue, which is part of what calling Connection.start() does. (was: It appears
that the failover process can block itself if it occurs during the Connection
being stopped and there are any messages in the pre-dispatch queue, as the
dispatcher thread will wait for the connection to be started again, but
failover can be waiting for the dispatcher to do some cleanup of the
pre-dispatch queue.)
Summary: failover process can effectively start the Connection if they
are currently stopped (was: failover process can block itself if the
Connection is stopped)
> failover process can effectively start the Connection if they are currently
> stopped
> -----------------------------------------------------------------------------------
>
> Key: QPID-3520
> URL: https://issues.apache.org/jira/browse/QPID-3520
> Project: Qpid
> Issue Type: Bug
> Components: Java Client
> Reporter: Robbie Gemmell
>
> It appears that the failover process can effectively start the Connection
> during failover if it was currently stopped, as it starts the Dispatcher
> thread in the Session implementation to clean the pre-dispatch queue, which
> is part of what calling Connection.start() does.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
