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.b...@fusesource.com Web: http://fusesource.com Twitter: tabish121 Blog: http://timbish.blogspot.com/
