It seems that even PingPeriod is set, it won't fix the problem because there is a HTTPClientIL instance created on the JBOSS to listen on the queue on behalf of remote HTTP JMS client - the PingTask only applied to this instance that's why PingPeriod is turned off.
I guess that the only way available now is to use ClientMonitorInterceptor as Adrian suggested in another thread but this means that all the messages in the queue from the time the HTTP client is "killed" to the time it's detected as inactive to be removed would be "lost". OR go and change the code yourself to fix this up? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3833836#3833836 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3833836 ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
