One further thought on this issue. It might have not been evident from the stack trace above, that the publishing thread is running within the JBoss AS (and hence the JMS server) process itself. It seems this publishing thread is directly writing through to the subscribers and blocking with a timeout of 15 mins in some cases when a subscribing client has suddenly died. This also locks out all further publishing threads for the whole timeout period as these are synchronized on the JMS session and waiting for the ongoing call to publish to terminate. Does this ring any bells on how to avoid the long timeout? Do "normal" timeouts not take effect due to the in-process publishing? Or, do you think it to be promising to route the generated messages to an external process first, that in turn publishes them to the JMS server? This approach would avoid the in-process publishing. Thanks a lot, again, for your support. Ralf Torsten View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4199703#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...