This error indicates that we did not receive a WireFormat response from
the Broker when we connected, which could mean that the broker is in a
bad state and is unable to respond to us. This could be related to an
out of memory situation.
On Wed, 2009-01-28 at 06:40 -0800, Sebastien SOILEN wrote:
t;> 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.blogs
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 proces
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).
--
View this message in context:
http://www.nabble.com/ActiveMQ-invalid-response-tp21703873p21706383.html
Sent from the ActiveMQ - User mail
By setting the send timeout you are making the client more susceptible
to failing because the broker is using flow control. Also a one second
timeout is pretty short depending on how many client are using your
broker and what the overall network load is, I'd recommend something a
good deal higher,
a bug, a
misuse or a wrong configuration (more probable),
especially due to the random occurrences of the exception.
Any clue?
More infos needed?
Regards,
Sebastien SOILEN
--
View this message in context:
http://www.nabble.com/ActiveMQ-invalid-response-tp21703873p21703873.html
Sent from the
