[
https://issues.apache.org/jira/browse/AMQ-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17841007#comment-17841007
]
Matthew Washburn commented on AMQ-796:
--------------------------------------
https://issues.apache.org/jira/browse/AMQ-9483
I put a patch on this ticket to fix this issue. I concur that it is not fixed.
> 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/jira/browse/AMQ-796
> Project: ActiveMQ Classic
> Issue Type: Bug
> Affects Versions: 4.0, 5.3.0
> Reporter: Hiram R. Chirino
> Assignee: Robert Davies
> Priority: Major
> Fix For: 5.6.0, 4.0.3
>
> Attachments: AMQ-796.cmd, Sender.java, jstack_amq_5.6.0,
> jstack_v5.8.0, threadDump.txt
>
>
> 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 was sent by Atlassian Jira
(v8.20.10#820010)
