[esb-issues] [JBoss JIRA] Created: (JBESB-2923) jbpm.esb: Add CallbackQueue to META-INF/deployment.xml

Daniel Bevenius (JIRA) jira-events at lists.jboss.org
Mon Nov 2 07:45:05 EST 2009


jbpm.esb: Add CallbackQueue to META-INF/deployment.xml
------------------------------------------------------

                 Key: JBESB-2923
                 URL: https://jira.jboss.org/jira/browse/JBESB-2923
             Project: JBoss ESB
          Issue Type: Task
      Security Level: Public (Everyone can see)
          Components: Process flow
            Reporter: Daniel Bevenius
            Assignee: Daniel Bevenius
             Fix For: 4.7


Upon startup sometimes the following error message is displayed:
13:27:41,136 WARN  [JmsActivation] Failure in jms activation org.jboss.resource.adapter.jms.inflow.JmsActivationSpec at b56c40(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter at 13df5d7 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:351)
    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:650)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
    at java.lang.Thread.run(Thread.java:595)

This queue, CallbackQueue, is defined in jbpm.esb/jbm-queue-service.xml but is not present in the depends section of the META-INF/deployment.xml:
<jbossesb-deployment>
  <depends>jboss.esb:deployment=jbossesb.esb</depends>
  <depends>jboss.esb:service=JbpmService</depends>
</jbossesb-deployment>
Adding the queue to the depends section should take care of this issue:
<jbossesb-deployment>
  <depends>jboss.esb:deployment=jbossesb.esb</depends>
  <depends>jboss.esb:service=JbpmService</depends>
  <depends>jboss.esb.destination:service=Queue,name=CallbackQueue</depends>
</jbossesb-deployment>



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the esb-issues mailing list