activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Posta <christian.po...@gmail.com>
Subject Re: "Wire format negotiation timeout: peer did not send his wire format"
Date Mon, 12 May 2014 16:45:49 GMT
What networking/firewalls do you have between your clients and broker?

On Sun, May 11, 2014 at 7:30 AM, Larry Meadors <larry.meadors@gmail.com> wrote:
> No hints?
>
> This is killing me - I'm restarting AMQ several times a week now. :-/
>
> On Wed, May 7, 2014 at 11:18 AM, Larry Meadors <larry.meadors@gmail.com> wrote:
>> I'm running AMQ 5.7.0 with a camel application (using camel 2.10.7, in
>> case that's relevant) and recently, the app has started logging these
>> messages:
>>
>> WARN  o.a.c.c.j.DefaultJmsMessageListenerContainer - Setup of JMS
>> message listener invoker failed for destination 'play.save' - trying
>> to recover. Cause: Wire format negotiation timeout: peer did not send
>> his wire format.
>>
>> Once that starts happening, it seems that AMQ drops all connections,
>> and won't allow any new ones to be created. The result is that nothing
>> can send or consume messages and I end up restarting AMQ to get things
>> rolling again.
>>
>> That's not epic.
>>
>> The odd thing is that this app ran for close to a year with the same
>> AMQ configuration, then started throwing these down about the same
>> time I increased the JVM memory limits for it and AMQ.
>>
>> I'm kind of stumped and looking for options. I considered dropping the
>> memory limits back to where they were before, but the reason I
>> increased them is because we were getting a lot of volume, and that
>> appeared to be causing OOMs.
>>
>> Any suggestions?
>>
>> Larry



-- 
Christian Posta
http://www.christianposta.com/blog
twitter: @christianposta

Mime
View raw message