activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jaya_srini <jya_sr...@Hotmail.com>
Subject Re: Wire format negotiation timeout
Date Thu, 20 Nov 2008 01:37:56 GMT

Hi 

can someone answer my email below?

Basically

What could be some possible causes of the wireformat negotiation not being
established? 

Also, Is there a way to set the default timeout parameter from the
Connection URI i.e one of the wireformat.* options? 

Currently we are seeing a lot of negotiation timeouts and I would like to
understand why this happens. Could it be related to network connectivity
issues?

thank you
jaya



jaya_srini wrote:
> 
> Thanks Joe!
> 
> No. we only see this if I send higher than certain number of requests
> (after about 1000 - 2000 concurrent requests)
> 
> Couple of questions...
> 
> What could be some possible causes of the negitiation not being
> established?
> 
> Also, Is there a way to set this timeout parameter from the Connection URI
> i.e one of the wireformat.* options?
> 
> 
> 
> ttmdev wrote:
>> 
>> The TransportConnector is used by the broker to listen for and accept
>> connection requests from clients and other brokers. When a connection is
>> initially established, the connection endpoints go through  a wireformat
>> negotiation phase. This is explained on this page.  
>> 
>> http://activemq.apache.org/openwire-version-2-specification.html
>> 
>> In your case, I suspect that the broker has sent its wireformat info
>> object and is waiting for the other endpoint (peer) to respond, which it
>> never does within the alloted timeout. The default timeout value is 15
>> seconds (see 
>> http://activemq.apache.org/maven/activemq-core/apidocs/org/apache/activemq/transport/WireFormatNegotiator.html

>> WireFormatNegotiator.htm ). 
>> 
>> Do you see the problem with a lighter connection request load? 
>> 
>> Joe
>> 
>> 
>> 
>> jaya_srini wrote:
>>> 
>>> Hello
>>> 
>>> We are using ActiveMQ 5.0 and we see these messages in the logs when the
>>> broker is hit with multiple requests (in our case > 1000 concurrent
>>> requests). Each request creates a new connection, sends a message to the
>>> topic and closes the connection. There is also a durable consumer that
>>> gets created once and receives messages asynchrounously from the topic
>>> 
>>> ERROR TransportConnector             - Could not accept connection :
>>> Wire format
>>>  negotiation timeout: peer did not send his wire format.
>>> ERROR TransportConnector             - Could not accept connection :
>>> Wire format
>>>  negotiation timeout: peer did not send his wire format.
>>> 
>>> Can someone explain what the above error message means and how this can
>>> be resolved?
>>>  
>>> We are using the following Connect URI
>>> 
>>> tcp://localhost:61616?jms.useAsyncSend=true&jms.dispatchAsync=true&wireFormat.maxInactivityDuration=-1
>>> 
>>> thank much in advance!
>>> jaya
>>> 
>> 
>> 
> 
> 

-- 
View this message in context: http://www.nabble.com/Wire-format-negotiation-timeout-tp17562104p20593431.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.


Mime
View raw message