activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <jira+amq...@apache.org>
Subject [jira] Commented: (AMQNET-211) ConnectionInterruptedListener doesnt raise the event when broker network dies in failover mode
Date Mon, 23 Nov 2009 13:23:54 GMT

    [ https://issues.apache.org/activemq/browse/AMQNET-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=56022#action_56022
] 

Timothy Bish commented on AMQNET-211:
-------------------------------------

Ok, this is working as I'd expect then.  The NMS.ActiveMQ implementation currently doesn't
have an inactivity monitor so there's no active ping of the connection from the client so
in the case of the network plug being pulled you are essentially waiting for the OS to timeout
the socket, this can take up to an hour depending on the OS and the TCP/IP config.  

Adding an inactivity monitor is on my TODO list but I'm not sure it will make it into the
1.2.0 release, we are planning on cutting release candidates for that this week.

> ConnectionInterruptedListener doesnt raise the event when broker network dies in failover
mode
> ----------------------------------------------------------------------------------------------
>
>                 Key: AMQNET-211
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-211
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: ActiveMQ, NMS
>    Affects Versions: 1.2.0
>         Environment: ActiveMQ 5.3 stable release. tested also with ActiveMQ 5.4 Nightly
build
> Apache.NMS 1.2.0.1778
> Apache.NMS.ActiveMQ.dll 1.2.0.1778
>            Reporter: Sebastien Rodriguez
>            Assignee: Jim Gomes
>         Attachments: activemq.xml
>
>
> The problem comes when I set up the following configuration:
> Network of brokers (2 brokers, A and B) in failover mode
> Client written in C# using the Apache.NMS.ActiveMQ client, configured in failover mode.
(machine C)
> When stopping manually the service in one computer(A for eg), the switch is done without
any problems. C uses B to send the data. The admin console shows he has one consumer.
> Turning the service on and doing the same step in the other computer works great too
(the client failovers to the recovered broker again without any problems: C is connected to
A now)
> Unplugging the network cable in A does not cause C to switch to B again. Looking at the
admin console there are no consumers connected to B.
> Looking the logs of B:
> jvm 1    |  WARN | Could not start network bridge between: vm://10.216.1.66 and: tcp://10.216.1.101:61616
due to: java.net.ConnectException: Connection timed out: connect
> This should have raised a ConnectionInterruptedListener event. Logs shoes nothing such
happens

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message