activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Rosenberg <jrosenb...@shopzilla.com>
Subject Re: [jira] Created: (AMQ-1450) Timed failure notification for FailOverTransport
Date Tue, 13 Nov 2007 17:21:19 GMT

I think this would be big improvement, we are wrestling with this issue at
present.  If no broker is available, we want it to return to the client
quickly, but it should then continue retrying, so that subsequent requests
that happen after a broker is available are successful.

I have seen now, that if I wait long enough, it does eventually retry. 
Apparently there's a timer (I waited 30 minutes).  Perhaps this timer is
something that could easily made configurable, with something much less than
30 minutes?

Jason


DEBUG [2007-11-13 16:51:54,393] thread:Timer-0                            
FailoverTransport -- Stopped.
DEBUG [2007-11-13 16:53:36,651] thread:http-8080-exec-2                   
FailoverTransport -- Waking up reconnect task
DEBUG [2007-11-13 16:53:36,652] thread:http-8080-exec-2                   
FailoverTransport -- Started.
DEBUG [2007-11-13 16:53:36,652] thread:ActiveMQ Task                      
FailoverTransport -- Attempting connect to: tcp://localhost:61616
DEBUG [2007-11-13 16:53:36,657] thread:ActiveMQ Task                   
WireFormatNegotiator -- Sending: WireFormatInfo { version=2,
properties={CacheSize=1024, CacheEnabled=true, SizePrefixDisabled=false,
TcpNoDelayEnabled=true, MaxInactivityDur
ation=30000, TightEncodingEnabled=true, StackTraceEnabled=true},
magic=[A,c,t,i,v,e,M,Q]}
DEBUG [2007-11-13 16:53:36,658] thread:ActiveMQ Task                      
FailoverTransport -- Connection established
DEBUG [2007-11-13 16:53:36,714] thread:ActiveMQ Transport:
tcp://localhost/127.0.0.1:61616           WireFormatNegotiator -- Received
WireFormat: WireFormatInfo { version=2, properties={CacheSize=1024,
CacheEnabled=true, SizePrefixDisabled=false,
 TcpNoDelayEnabled=true, MaxInactivityDuration=30000,
TightEncodingEnabled=true, StackTraceEnabled=true}, magic=[A,c,t,i,v,e,M,Q]}
DEBUG [2007-11-13 16:53:36,714] thread:ActiveMQ Transport:
tcp://localhost/127.0.0.1:61616           WireFormatNegotiator --
tcp://localhost/127.0.0.1:61616 before negotiation:
OpenWireFormat{version=2, cacheEnabled=false, stackTraceEnabled=false
, tightEncodingEnabled=false, sizePrefixDisabled=false}
DEBUG [2007-11-13 16:53:36,714] thread:ActiveMQ Transport:
tcp://localhost/127.0.0.1:61616           WireFormatNegotiator --
tcp://localhost/127.0.0.1:61616 after negotiation: OpenWireFormat{version=2,
cacheEnabled=true, stackTraceEnabled=true, t
ightEncodingEnabled=true, sizePrefixDisabled=false}





JIRA jira@apache.org wrote:
> 
> Timed failure notification for FailOverTransport 
> -------------------------------------------------
> 
>                  Key: AMQ-1450
>                  URL: https://issues.apache.org/activemq/browse/AMQ-1450
>              Project: ActiveMQ
>           Issue Type: Improvement
>           Components: Transport
>     Affects Versions: 4.1.1
>             Reporter: Diego Belfer
> 
> 
> It would be good to have a new property for the FailOverTransport, in
> order to define the maximum time to wait when sending a message if a
> reconnection attempt is taking place.
> 
> This would avoid blocking client threads for an unbounded amount of time,
> while it would still allow an unbounded time for  the reconnection
> attempt.
> 
> I was looking at the code, and it does not seem hard to add. I could add
> it if you think it would be useful for others.
> 
> Thanks,
> Diego Belfer
> 
> 
> 
> 
> -- 
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
> 
> 
> 

-- 
View this message in context: http://www.nabble.com/-jira--Created%3A-%28AMQ-1450%29-Timed-failure-notification-for-FailOverTransport-tf4591250s2354.html#a13730485
Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.


Mime
View raw message