activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From garima015 <garima_ind...@rediffmail.com>
Subject Re: [Spam: 5.0] Broker issue regarding queue
Date Thu, 15 Mar 2007 14:08:11 GMT

I am using activemq 4.1.0 version.In my network of two brokers,
When i brings down one broker i am getting

INFO  FailoverTransport              - Transport failed, attempting to
automatically reconnect due to: java.io.EOFException

on the second broker console.
Is this a problem in failover and reconnection.But my queues are visible on
second broker

Thanks



James.Strachan wrote:
> 
> On 3/14/07, garima015 <garima_indiya@rediffmail.com> wrote:
>>
>> when i am manually shutting down the broker 1 my application is getting
>> connected to second broker
>> but console of first broker is showing exception.It does not have a clean
>> exit
>> WARN  DemandForwardingBridge         - Caught exception from local start
>> java.io.IOException: Transport disposed.
>>
>> Is it a kind of problem.
> 
> No - just a timing issue, nothing to worry about.
> 
>> How much usually application should take to resume the connection to
>> second
>> broker upon failure of first.
> 
> A client should reconnect to another broker after the broker has died
> within a second; assuming that the client can detect the socket has
> died. On some platforms it can take hours or days for the OS to notify
> a process that the socket has died; if so you might want to use an
> inactivity timeout (which is set to 30 seconds by default)
> http://activemq.apache.org/configuring-wire-formats.html
> 
> 
> -- 
> 
> James
> -------
> http://radio.weblogs.com/0112098/
> 
> 

-- 
View this message in context: http://www.nabble.com/Broker-issue-regarding-queue-tf3402927s2354.html#a9495188
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message