NMS > InactivityException?

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

NMS > InactivityException?

magellings
I'm seeing a lot of these messages logged by the NMS ActiveMQ provider.  There are multiple log statements every millisecond and seems to be infinite.  Any ideas why this is occurring?

2010-11-18 10:02:25,107 [17384] [DEBUG] Apache.NMS.Tracer - No Message sent since last write check. Sending a KeepAliveInfo
2010-11-18 10:02:25,107 [17384] [DEBUG] Apache.NMS.Tracer - Inactivity Monitor: A read check is not currently allowed.
2010-11-18 10:02:25,107 [17384] [DEBUG] Apache.NMS.Tracer - No Message sent since last write check. Sending a KeepAliveInfo
2010-11-18 10:02:25,107 [17384] [DEBUG] Apache.NMS.Tracer - Inactivity Monitor: A read check is not currently allowed.
2010-11-18 10:02:25,107 [17384] [DEBUG] Apache.NMS.Tracer - No Message sent since last write check. Sending a KeepAliveInfo
2010-11-18 10:02:25,107 [17384] [DEBUG] Apache.NMS.Tracer - Inactivity Monitor: A read check is not currently allowed.
2010-11-18 10:02:25,107 [17384] [DEBUG] Apache.NMS.Tracer - No Message sent since last write check. Sending a KeepAliveInfo
2010-11-18 10:02:25,107 [17384] [DEBUG] Apache.NMS.Tracer - No message received since last read check! Sending an InactivityException!
Reply | Threaded
Open this post in threaded view
|

Re: NMS > InactivityException?

Timothy Bish-2
On Thu, 2010-11-18 at 09:26 -0800, magellings wrote:

> I'm seeing a lot of these messages logged by the NMS ActiveMQ provider.
> There are multiple log statements every millisecond and seems to be
> infinite.  Any ideas why this is occurring?
>
> 2010-11-18 10:02:25,107 [17384] [DEBUG] Apache.NMS.Tracer - No Message sent
> since last write check. Sending a KeepAliveInfo
> 2010-11-18 10:02:25,107 [17384] [DEBUG] Apache.NMS.Tracer - Inactivity
> Monitor: A read check is not currently allowed.
> 2010-11-18 10:02:25,107 [17384] [DEBUG] Apache.NMS.Tracer - No Message sent
> since last write check. Sending a KeepAliveInfo
> 2010-11-18 10:02:25,107 [17384] [DEBUG] Apache.NMS.Tracer - Inactivity
> Monitor: A read check is not currently allowed.
> 2010-11-18 10:02:25,107 [17384] [DEBUG] Apache.NMS.Tracer - No Message sent
> since last write check. Sending a KeepAliveInfo
> 2010-11-18 10:02:25,107 [17384] [DEBUG] Apache.NMS.Tracer - Inactivity
> Monitor: A read check is not currently allowed.
> 2010-11-18 10:02:25,107 [17384] [DEBUG] Apache.NMS.Tracer - No Message sent
> since last write check. Sending a KeepAliveInfo
> 2010-11-18 10:02:25,107 [17384] [DEBUG] Apache.NMS.Tracer - No message
> received since last read check! Sending an InactivityException!
>

What is your maxInactivityDuration set to?  Looks like the thread that
is firing the inactivity check is spinning.

Regards
Tim.


--
Tim Bish
------------
FuseSource
Email: [hidden email]
Web: http://fusesource.com
Twitter: tabish121
Blog: http://timbish.blogspot.com/


Reply | Threaded
Open this post in threaded view
|

Re: NMS > InactivityException?

magellings
I'm not setting that explicitly so I'm guessing it's the default, whatever that is.
Reply | Threaded
Open this post in threaded view
|

Re: NMS > InactivityException?

Timothy Bish-2
On Thu, 2010-11-18 at 11:20 -0800, magellings wrote:
> I'm not setting that explicitly so I'm guessing it's the default, whatever
> that is.

Best bet would be to provide a sample app that demonstrates the issue,
the inactivity monitor should be defaulting to a duration of 30secs
which would mean a write check would be done every 10secs.

Regards

--
Tim Bish
------------
FuseSource
Email: [hidden email]
Web: http://fusesource.com
Twitter: tabish121
Blog: http://timbish.blogspot.com/


Reply | Threaded
Open this post in threaded view
|

Re: NMS > InactivityException?

magellings
For now Tim I have just disabled it.  We implemented our own keep alive functionality when we discovered this same issue where consumer is idle and there is a network hiccup.