activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] Commented: (AMQCPP-246) Failover transport doesn't detect network failures
Date Tue, 16 Jun 2009 22:06:35 GMT


Timothy Bish commented on AMQCPP-246:

One thing to look out for is that the sockets might not get broken depending on your network
hardware, switches, routers etc.  You can try turning on soKeepAlive on the tcp transports
by appending soKeepAlive=true to the transports specified in the Failover transport URI.

> Failover transport doesn't detect network failures
> --------------------------------------------------
>                 Key: AMQCPP-246
>                 URL:
>             Project: ActiveMQ C++ Client
>          Issue Type: Bug
>          Components: CMS Impl
>    Affects Versions: 3.0
>         Environment: CMS Consumer running under  Linux (Fedora Core 10)
> Broker and JMS producer running under Linux (Redhat 7)
>            Reporter: Daniel Donoso
>            Assignee: Timothy Bish
>             Fix For: 3.0.1
>         Attachments: SimpleAsyncConsumer.cpp
> I tested the CMS SimpleAsyncConsumer example to check the failover transport funcionality
and it doesn't detect the network failures, and after network restauration the consumer never
receives any message.
> These are the steps:
> 1. The network has a failure. 
> 2. The Producer sends a message. 
> 3.  After a minute the network is up. (The consumer doesn't detect the failure)
> 4. The consumer doesn't receive the message.
> 5. The producer sends other message.
> 6. The consumer never receives old and new messages

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

View raw message