Date of First Response: 2009-12-02 05:13:08 project_key: SOA An exception is thrown during startup: javax.naming.NameNotFoundException: CallbackQueue not bound It seems that there is missing dependency among jbpm internal components. The issue was spotted when PostgreSQL was used so it probably depends on timing 10:23:34,592 INFO [JBpmCallback] initialise() invoked - config=<action action="action" class="org.jboss.soa.esb.services.jbpm.actions.JBpmCallback"/> 10:23:34,653 INFO [Environment] Hibernate 3.3.2.GA 10:23:34,659 INFO [Environment] hibernate.properties not found 10:23:34,670 INFO [Environment] Bytecode provider name : javassist 10:23:34,682 INFO [Environment] using JDK 1.4 java.sql.Timestamp handling 10:23:34,734 INFO [JDBCDataStore] Generated token 'authToken:30BD5930-BEE4-11DE-9930-B5F2924765A2' for user: 'jbossesb/JBoss ESB User' 10:23:34,773 INFO [JDBCDataStore] Generated token 'authToken:30C4D340-BEE4-11DE-9340-8A7373868BF1' for user: 'jbossesb/JBoss ESB User' 10:23:34,913 WARN [JmsActivation] Failure in jms activation org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@401f25(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter@215d51 destination=queue/CallbackQueue destinationType=javax.jms.Queue tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=1 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=5) javax.naming.NameNotFoundException: CallbackQueue not bound at org.jnp.server.NamingServer.getBinding(NamingServer.java:771) at org.jnp.server.NamingServer.getBinding(NamingServer.java:779) at org.jnp.server.NamingServer.getObject(NamingServer.java:785) at org.jnp.server.NamingServer.lookup(NamingServer.java:443) at org.jnp.server.NamingServer.lookup(NamingServer.java:399) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:726) at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:686) at javax.naming.InitialContext.lookup(InitialContext.java:392) at org.jboss.util.naming.Util.lookup(Util.java:222) at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupDestination(JmsActivation.java:464) at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:352) at org.jboss.resource.adapter.jms.inflow.JmsActivation$SetupActivation.run(JmsActivation.java:729) at org.jboss.resource.work.WorkWrapper.execute(WorkWrapper.java:205) at org.jboss.util.threadpool.BasicTaskWrapper.run(BasicTaskWrapper.java:260) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang.Thread.run(Thread.java:619) 10:23:34,915 INFO [QueueService] Queue[/queue/CallbackQueue] started, fullSize=200000, pageSize=2000, downCacheSize=2000 10:23:34,929 INFO [TomcatDeployment] deploy, ctxPath=/jbpm-console 10:23:35,081 INFO [config] Initializing Mojarra (1.2_13-b01-FCS) for context '/jbpm-console'
Was fixed at the beginning of November.
Link: Added: This issue depends JBESB-2923
Verified in ER5