We have recently ported our application from Weblogic JMS client to JBoss's HornetQ client.
We have always run our client jvm inside the Tanuki wrapper, but since going to HornetQ our app and its service are stopping unexpectedly.
It turns out that the HornetQ client must run as a daemon thread, meaning that Tanuki no longer sees it as a monitored thread. (Weblogic's JMS client did not run as a daemon.) Tanuki therefore terminates our jvm, as there are "no non-daemon threads".
So - is there any way we can configure Tanuki to monitor a daemon thread, so we don't get it terminating the jvm?
Many thanks for your help!
Log in to post a comment.