it seems coherent, as we don't use producer flow control. We'll see if longer
delay helps.
There is another exception we get sometimes when trying to open connection
with the broker.We can't really understand its meaning... and how it affects
the connection. May it be caused by a possible lack of memory too?
CMSException: OpenWireFormatNegotiator::requestWire format negotiation
timeout: peer did not send his wire f
ormat.
FILE: activemq/connector/openwire/OpenWireFormatNegotiator.cpp,
LINE: 98
FILE: activemq/connector/openwire/OpenWireFormatNegotiator.cpp,
LINE: 107
FILE: activemq/connector/openwire/OpenWireConnector.cpp, LINE: 1533
FILE: activemq/connector/openwire/OpenWireConnector.cpp, LINE: 249
FILE: activemq/connector/openwire/OpenWireConnector.cpp, LINE: 186
FILE: activemq/core/ActiveMQConnectionFactory.cpp, LINE: 173
Timothy Bish wrote:
>
> Things like this can also happen if you disable producer flow control on
> the client or the Broker is running out of memory.
>
> The default timeout that we used prior to adding the option to set it on
> the connection was 15 seconds, one second just seems a bit to brief to
> me to allow for other processes on the local machine which could hog the
> CPU for short periods of time.
>
> Regards
> Tim.
>
>
> On Wed, 2009-01-28 at 06:07 -0800, Sebastien SOILEN wrote:
>>
>> Thanks for your quick answer.
>> We are trying with a 5s timeout, but we aren't under heavy load, the
>> clients
>> are all local and few (<50).
>>
>>
>>
>>
>>
>>
>>
>>
> --
> Tim Bish
> http://fusesource.com
> http://timbish.blogspot.com/
>
>
>
>
>
--
View this message in context:
http://www.nabble.com/ActiveMQ-invalid-response-tp21703873p21707017.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
