We have a problem with one of our client programs that subscribes to a topic (this is a temp subscription). The thread that processes the subscribed messages gets "stuck".
Initial effect was that a lot of messages queued up on the topic (in one case we had over 200,000). Now we set a maxDepth on the topic, so that everyone gets an exception when the topic reaches the maxDepth. The topic queue remains full, although other publishers and subscribers still seem to work.
I'd like to be able to identify the "stuck" subscriber and kill it's connection.
I'm not sure where to look though. Would enabling "ClientMonitorInterceptor" help? I expect messages from each client at least once a minute.
Any suggestions will be greatly appreciated...
...richie
