You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by magellings <ma...@qg.com> on 2010/11/18 18:26:19 UTC
NMS > InactivityException?
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!
--
View this message in context: http://activemq.2283324.n4.nabble.com/NMS-InactivityException-tp3049191p3049191.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: NMS > InactivityException?
Posted by magellings <ma...@qg.com>.
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.
--
View this message in context: http://activemq.2283324.n4.nabble.com/NMS-InactivityException-tp3049191p3049659.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: NMS > InactivityException?
Posted by Timothy Bish <ta...@fusesource.com>.
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: tim.bish@fusesource.com
Web: http://fusesource.com
Twitter: tabish121
Blog: http://timbish.blogspot.com/
Re: NMS > InactivityException?
Posted by magellings <ma...@qg.com>.
I'm not setting that explicitly so I'm guessing it's the default, whatever
that is.
--
View this message in context: http://activemq.2283324.n4.nabble.com/NMS-InactivityException-tp3049191p3049397.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.
Re: NMS > InactivityException?
Posted by Timothy Bish <ta...@fusesource.com>.
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: tim.bish@fusesource.com
Web: http://fusesource.com
Twitter: tabish121
Blog: http://timbish.blogspot.com/