Embedded HornetQ not stopping correctly

[teto]

Hi,

I'm running an embedded HornetQ instance and I can't get it to stop completely. Two non-daemon threads stay around and I suspect they are not from the HornetQ server but from the JNDI server, these are the stack traces for them as reported by Eclipse:

Thread [Naming Bootstrap#2] (Suspended)

Unsafe.park(boolean, long) line: not available [native method]

LockSupport.park(Object) line: 186

AbstractQueuedSynchronizer$ConditionObject.await() line: 2043

LinkedBlockingQueue<E>.take() line: 386

ThreadPoolExecutor.getTask() line: 1043

ThreadPoolExecutor.runWorker(ThreadPoolExecutor$Worker) line: 1103

ThreadPoolExecutor$Worker.run() line: 603

Thread.run() line: 636

Thread [Naming Bootstrap#1] (Suspended)

Unsafe.park(boolean, long) line: not available [native method]

LockSupport.park(Object) line: 186

AbstractQueuedSynchronizer$ConditionObject.await() line: 2043

LinkedBlockingQueue<E>.take() line: 386

ThreadPoolExecutor.getTask() line: 1043

ThreadPoolExecutor.runWorker(ThreadPoolExecutor$Worker) line: 1103

ThreadPoolExecutor$Worker.run() line: 603

Thread.run() line: 636

Thread [Naming Bootstrap#2] (Suspended)

Unsafe.park(boolean, long) line: not available [native method]

LockSupport.park(Object) line: 186

AbstractQueuedSynchronizer$ConditionObject.await() line: 2043

LinkedBlockingQueue<E>.take() line: 386

ThreadPoolExecutor.getTask() line: 1043

ThreadPoolExecutor.runWorker(ThreadPoolExecutor$Worker) line: 1103

ThreadPoolExecutor$Worker.run() line: 603

Thread.run() line: 636

Thread [Naming Bootstrap#1] (Suspended)

Unsafe.park(boolean, long) line: not available [native method]

LockSupport.park(Object) line: 186

AbstractQueuedSynchronizer$ConditionObject.await() line: 2043

LinkedBlockingQueue<E>.take() line: 386

ThreadPoolExecutor.getTask() line: 1043

ThreadPoolExecutor.runWorker(ThreadPoolExecutor$Worker) line: 1103

ThreadPoolExecutor$Worker.run() line: 603

Thread.run() line: 636

They seem to be stuck waiting on a BlockingQueue. I'm using the embedded example as a guideline, but in the example System.exit(0) is executed right after stopping the resources:

jmsServer.stop();

naming.stop();

jndiServer.stop();

System.exit(0);

I can't call system.exit(0) in my application. Any ideas about what could be going on? I'm using HornetQ 2.1.2.Final. Thanks in advance.

[clebert.suconic]

How you're starting your JNDI server?

You could probably just use the same one we use...

look at our hornetq-beans.xml

You should be able to use any Context you like with HornetQ embedded.

This is probably more a question to JBossAS experts (since we use it from there). But I will try to help if you provide some info in how you're starting it.

Also, since you're embedded, why do you need a JNDI server?

[teto]

Hi Clebert,

thanks for your fast answer. I was just following the embedded example as a starting point, in fact I don't think I need the JNDI server at all, as long as I provide the connection params to my clients, right? However I need to setup the server programatically, i.e. no xml config files and I'm having trouble getting a JMS server up without using XML ad JNDI, can you point me to some resources?

[clebert.suconic]

Take a look at this class here:

http://anonsvn.jboss.org/repos/hornetq/trunk/tests/src/org/hornetq/tests/util/JMSTestBase.java

This class is starting a JMS Server for our tests.

It's using an InVMContext (which is just a dumb implementation based on a Hashmap that only sits on the test environment).

You could also set the context as null.

All the programatic configs will happen on the Configuration classes. We have a Configuration class for everything we do.

[clebert.suconic]

I almost forgot it..

There's a jms embedded example as well...

distribution/examples/jms/embedded