activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Dejan Bosanac <de...@nighttale.net>
Subject Re: Issue in example with failover
Date Tue, 09 Mar 2010 10:01:58 GMT
Hi Frank,

this is the issue we had before (and apparently it reoccurred). The problem
is that example application you're running doesn't have any non-deamon
threads and as transport is disconnected, the application shuts down before
it can reconnect. This is usually not the case in "real" applications as
they have another threads beside the amq transport ones.

I reopened the original issue to track this
https://issues.apache.org/activemq/browse/AMQ-796

Cheers
--
Dejan Bosanac - http://twitter.com/dejanb

Open Source Integration - http://fusesource.com/
ActiveMQ in Action - http://www.manning.com/snyder/
Blog - http://www.nighttale.net


On Tue, Mar 9, 2010 at 10:30 AM, Frank Werner <activemq@wesoft.de> wrote:

>
> If I use the following url
> -Durl='failover://(tcp://broker1:61616,tcp://broker2:61616)' I got the
> following output:
>
> root@broker1:/opt/apache-activemq-5.3.0/example # ant topic-listener
> -Durl='failover://(tcp://ppst-broker1:61616,tcp://broker2:61616)'
> Buildfile: build.xml
>
> init:
>
> compile:
>
> topic-listener:
>      [java] 10:24:11 INFO  Successfully connected to tcp://broker1:61616
>     [java] Waiting for messages...
> < ... now I stop broker1 ...>
>     [java] 10:24:25 WARN  Transport failed to tcp://broker1:61616 ,
> attempting to automatically reconnect due to: java.io.EOFException
>     [java] 10:24:25 INFO  Successfully reconnected to tcp://broker2:61616
>
> BUILD SUCCESSFUL
> Total time: 14 seconds
> root@broker2:/opt/apache-activemq-5.3.0/example #
>
> As you can see, it does reconnect successfully, but stops working after
> that
> :-(
>
> -Frank-
>
> --
> View this message in context:
> http://old.nabble.com/Issue-in-example-with-failover-tp27824427p27833305.html
> Sent from the ActiveMQ - User mailing list archive at Nabble.com.
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message