JMS starting order

[akirdat]

My ear file is being deployed before the JMS service starts, which causes my application to throw some startup errors like:

NameNotFoundException: DefaultJMSProvider

How do I make sure the JMS server is started before my ear gets deployed?

[akirdat]

I am using Jboss-3.2.1 and I just moved all the jms files from the jms directory into the deploy directory and I dont get the error anymore.

[akirdat]

I still get the following error:

javax.jms.JMSException: Invalid transaction id.
at org.jboss.mq.SpyXAResourceManager.addMessage(SpyXAResourceManager.java:95)
at org.jboss.mq.SpySession.sendMessage(SpySession.java:695)
at org.jboss.mq.SpyQueueSender.internalSend(SpyQueueSender.java:118)
at org.jboss.mq.SpyQueueSender.send(SpyQueueSender.java:68)

I would appreciate any help or comments.

I have posted the error and related code here :

http://www.jboss.org/modules/bb/index.html?module=bb&op=viewtopic&t=

[stephanenicoll]

Are you starting the default server. I know 3.2.1 has been shipped with an invalid parameter in the Jboss-service.xml

RecursiveSearch is set to False while it should be True

Please search your jboss-service.xml in service/default/conf and update.

that's why it works if you put everything in the deploy directory ;)

[akirdat]

Thanks! That worked.

[ronr]

I have a durable topic subscription and it seems that when jboss restarts my .ear is only partially deployed when messages begin to be delivered to the message driven beans. This results in all kinds of nasty errors. Can I specify that the durable messages do not get delivered until after my .ear is completely deployed.

Thanks for any help.