Are there any network issue between the systems that running the client
application and broker ? Is this persistent message ? Is the broker
using 'jdbc' store ? Could you get a thread dump on the broker when
this occurs ?
amy
On 01/11/2012 03:02 AM, forums_at_java.net wrote:
> For our Glassfish applications we are using JMQ 4.4 (Update 2 Patch 5)
> for
> messaging. From the past few days, I am observing the following
> warning in
> the server log where the client applications are deployed:
>
> [#|2012-01-11T17:51:09.571+0800|WARNING|sun-appserver2.1|javax.jms.connection|_ThreadID=89;_Th
>
> readName=p: thread-pool-1; w:
> 52;_RequestID=3c6f7d3a-a1f7-411b-a6ee-ac0f8b51b53f;|[W2003]: Broker not
> responding [TEXT_MESSAGE(1)] for 120 seconds. Still trying..., broker
> addr=10.41.11.69:7676(7678), connectionID=2137016074680922112,
> clientID=null,
> consumerID=17|#]
> But on the broker logs I don't see any exceptions/warning/errors for
> the same
> time.
> Seems like due to this, the processing is quite slow and its more over an
> intermittent issue.
>
> How can I interpret this warning to troubleshoot this issue further?
> Regards,
> Manesh Abhimanyu K.
>
>
> --
>
> [Message sent by forum member 'maneshk']
>
> View Post: http://forums.java.net/node/882259
>
>