When I try and bring up the first machine (the master) jboss tries to deploy my MDB before jms is deployed.
You can add a "depends" to the MDB to add an dependency on the JMS topic/queue.
Billy Newman wrote:
To clarify it looks like the problem is that jms as a whole is not up when my MDB tries to deploy.
I see a ton of posts about people wanting to use the deploy-hasingleton and having problems but no one seems to have any answers. Any ideas would be greatly appreciated.
Bobby Anderson wrote:The exception I get is (I cannot get the exception from the server so the best I can do is type in the exception without the stack trace):
javax.naming.NameNotFoundException: DefaultJMSProvider not bound