[jira] [Commented] (AMQ-796) Client may shtudown when failover connection is reconnecting. We need to maintain at least 1 non-daemon thread alive.

["Scarciello (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/AMQ-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16659079#comment-16659079 ] 

Scarciello commented on AMQ-796:
--------------------------------

Just a small reminder to tells that this issue is still in 5.12.1.

Adding these in FailoverTransport.class fix the issue like [~kimmking] said before..
{code:java}
reconnectTaskFactory = new TaskRunnerFactory();
reconnectTaskFactory.setDaemon(false); // to set daemon=false by kimmking
reconnectTaskFactory.init();
{code}
If i look that Jira this issue is solved from 5.6.0 but we are a lot here to explain that it is not corrected because we have to edit FailoverTRansport.class by ourselves. So he's it the only workaround for now or maybe is resolved in the last version?

 

> 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
>          Issue Type: Bug
>    Affects Versions: 4.0, 5.3.0
>            Reporter: Hiram Chirino
>            Assignee: Rob 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
(v7.6.3#76005)