You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Watson (JIRA)" <ji...@apache.org> on 2010/04/29 02:02:33 UTC
[jira] Updated: (AMQ-796) Client may shtudown when failover
connection is reconnecting. We need to maintain at least 1 non-daemon
thread alive.
[ https://issues.apache.org/activemq/browse/AMQ-796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gary Watson updated AMQ-796:
----------------------------
Attachment: AMQ-796.cmd
This is a Windows cmd script that uses 2 instances of the ProducerTool sample app to create 2 embedded brokers, and the single-threaded ConsumerTool with a failover URI to demonstrate the problem.
> 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, 5.3.0
> Reporter: Hiram Chirino
> Assignee: Hiram Chirino
> Fix For: 5.0.0, 4.0.3
>
> Attachments: AMQ-796.cmd
>
>
> 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.