It is difficult to identify what may be going wrong here without more
information but from the exception in server log, it appears that you are
having trouble with lazy initialization of the JMS service. A simple work
around for this issue to disable lazy-init by doing the following:
set lazy-init=false in the jms-host element of default-config
set the JVM option org.glassfish.jms.EagerStartup=true
This will enable the JMS service to be eagerly started when GF starts-up.
--
[Message sent by forum member 'sats']
View Post: http://forums.java.net/node/795394