-
1. Re: Tracking down MQ Threads
genman Aug 27, 2005 2:29 AM (in response to dabramov)
The client count should immediately decrease after a client has properly closed its connection. You can turn on tracing (use the tracing interceptor) to verify that for every open, you have a corresponding close. -
2. Re: Tracking down MQ Threads
ansk Sep 8, 2005 9:16 AM (in response to dabramov)Could you elaborate this? How exactly can you perform such a trace?
Thanks,
//Andreas -
3. Re: Tracking down MQ Threads
genman Sep 9, 2005 1:18 AM (in response to dabramov)
Keywords: log4j, jboss logging, tracing interceptor -
4. Re: Tracking down MQ Threads
dabramov Sep 13, 2005 4:06 PM (in response to dabramov)Finally got around to doing some tracing - I turned on the TRACE logging for the TraceInterceptor. I can see subscriptions and unsubsciptions being logged.
The problem is that the ID identifing any particular subscription are bogus - always -2147483648 which is min int. Based on this information, it's not possible to correlate subscribes with the unsubscribes, so I can't see what's not being closed. Ideas?
2005-09-13 15:24:19,727 Thread-27528 TRACE [org.jboss.mq.server.TracingInterceptor] CALLED : subscribe
2005-09-13 15:24:19,727 Thread-27528 TRACE [org.jboss.mq.server.TracingInterceptor] ARG : Subscription[subId=-2147483
648 destination=TOPIC.FMLiveEventChangeTopic messageSelector=(JMSType = 'Updated' OR JMSType = 'Deleted' OR JMSType = 'N
ew') AND (DeviceType='SOLARIS' ) Local Create]
2005-09-13 15:26:19,304 Thread-27555 TRACE [org.jboss.mq.server.TracingInterceptor] CALLED : unsubscribe
2005-09-13 15:26:19,304 Thread-27555 TRACE [org.jboss.mq.server.TracingInterceptor] ARG : -2147483648
2005-09-13 15:26:19,305 Thread-27555 TRACE [org.jboss.mq.server.TracingInterceptor] RETURN : unsubscribe