[
https://issues.apache.org/activemq/browse/AMQ-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino resolved AMQ-796.
-------------------------------
Resolution: Fixed
Fix in rev 587504
The threads associated with the session are now setup to be non-daemon so
that if you
setup a MessageListener and let the main thread exit, your program will not
terminate
if there are no active transport threads which is the case when the failover
transport
is in the middle of reconnecting to a broker.
> 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
> Assignee: Hiram Chirino
> Fix For: 5.0.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.
-
You can reply to this email to add a comment to the issue online.
