[ https://issues.apache.org/activemq/browse/AMQ-796?page=all ]
Hiram Chirino updated AMQ-796:
------------------------------
Fix Version/s: 4.2
(was: 4.1.0)
> Client may shtudown when failover connection is reconnecting. We need to
> maintain at least 1 non-daemon thread alive.
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: AMQ-796
> URL: https://issues.apache.org/activemq/browse/AMQ-796
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 4.0
> Reporter: Hiram Chirino
> Fix For: 4.2.0, 4.0.3
>
>
> Dejan Reported on the User lists:
> Hi,
> after some experiments I found that this problem only exists if there are no
> other threads in the application. It seems like connection thread dies
> before it manages to reconnect. By starting another thread in the
> application, it succeeds to recover from master failure and reconnect to the
> slave broker. So I have a workaround for now, but it would be nice to make
> this work even for simple (single-threaded) clients.
> Regards,
> Dejan
--
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
