You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "akhil (JIRA)" <ji...@apache.org> on 2016/09/27 00:32:20 UTC

[jira] [Comment Edited] (AMQ-6439) Active MQ Failover Exception

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

akhil edited comment on AMQ-6439 at 9/27/16 12:31 AM:
------------------------------------------------------

I have figured out the fix in client code and it's not reproducible any more.


was (Author: areddy7021):
I have figured out the fix and it's not reproducible any more.

> 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
>             Fix For: 5.x
>
>
> 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)