activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMQ-6439) Active MQ Failover Exception
Date Thu, 22 Sep 2016 15:58:20 GMT

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

Timothy Bish commented on AMQ-6439:
-----------------------------------

First, its best not to point to mailing list threads in JIRA issues, provide all the relevant
information in the issue as the list messages can go missing etc.  

Second it is usually a good idea to try the latest broker release before reporting an issue
as there are quite a few fixes in each release and you are running a rather old version it
seems.

If you think there is an actual bug then we'd need a way to reproduce the issue otherwise
we will have to close it out as incomplete given that we can't just guess what might be wrong.
 If you need support the mailing lists are the place to ask questions, JIRA is for real bugs.
 

> Active MQ Failover Exception
> ----------------------------
>
>                 Key: AMQ-6439
>                 URL: https://issues.apache.org/jira/browse/AMQ-6439
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker, networkbridge, Transport
>    Affects Versions: 5.11.4
>         Environment: Mac OS , Active MQ 5.11 , Java 8 Producer , Java 8 Consumer
>            Reporter: akhil
>
> I am using the common file storage as a KahaDB mount for the two brokers and they are
not in the network. I am running the local producer anad consumer against two of the brokers
using the failover string. It is working as expected in case of master slave topology in case
of DB locks. The producer is able to switch the connection from active master to slave or
slave to master during the failover but consumer is having the issue. it is going into the
idle state after certain time and never ever reconnecting to the new master broker. you can
find mored details in this forum where i have placed the example and screen shots. The consumer
channel is getting blocked and you can find more info here :
> http://activemq.2283324.n4.nabble.com/JMS-exception-during-the-Failover-td4716047.html



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message