[JBoss JIRA] Created: (JBESB-2924) server/XXX/lib/commons-httpclient.jar being deleted on undeploy
by Kevin Conner (JIRA)
server/XXX/lib/commons-httpclient.jar being deleted on undeploy
---------------------------------------------------------------
Key: JBESB-2924
URL: https://jira.jboss.org/jira/browse/JBESB-2924
Project: JBoss ESB
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Build and Release
Affects Versions: 4.6
Reporter: Kevin Conner
Assignee: Kevin Conner
Fix For: 4.7
The as5 installation copies commons-httpclient-XXX.jar into server/XXX/lib but the undeploy is deleting commons-httpclient*.jar. This catches the version in as4 as well as as5.
The consequence of this is that the httpclient classes do not appear to be on the classloader even though commons-httpclient.jar exists in the top level lib directory.
--
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
14 years, 6 months
- 1
- 1
[JBoss JIRA] Created: (JBESB-2923) jbpm.esb: Add CallbackQueue to META-INF/deployment.xml
by Daniel Bevenius (JIRA)
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@b56c40(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter(a)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
14 years, 6 months
- 1
- 1