Hide Forgot
Date of First Response: 2008-06-20 11:35:34 Workaround Description: Add the following lines to jbossesb.esb/META-INF/deployment.xml <depends>jboss.esb.destination:service=Queue,name=DataCollectorQueue</depends> <depends>jboss.esb.destination:service=Queue,name=OperationsCollectorQueue</depends> <depends>jboss.esb.destination:service=Queue,name=OperationsResultCollectorQueue</depends> project_key: SOA Seeing this with CP02 CR2 and DB2: > ERROR [org.jboss.messaging.util.ExceptionUtil] SessionEndpoint[71-73lfcmhf-1-4o1dcmhf-1noe8i-1171ga] createQueue [b1-w3lfcmhf-1-4o1dcmhf-1noe8i-1171ga] javax.jms.JMSException: There is no administratively defined queue with name:queue/OperationsCollectorQueue
Link: Added: This issue is a dependency of JBESB-1839
Workaround Description: Added: Add the following lines to jbossesb.esb/META-INF/deployment.xml <depends>jboss.esb.destination:service=Queue,name=DataCollectorQueue</depends> <depends>jboss.esb.destination:service=Queue,name=OperationsCollectorQueue</depends> <depends>jboss.esb.destination:service=Queue,name=OperationsResultCollectorQueue</depends>
Just wondering - why wouldn't this cause a problem with DBs other than DB2??
This is not related to the databases, it is the startup order of the MBeans. As there is no existing dependency between the esb archive and the queues it will be possible for them to be deployed in any order. If the queues are deployed first then you will not see any error messages, reverse the order and they will appear. It may be that having a remote DB does alter the timings/sequence but it could also be present in other configurations.
Ah - thanks - that does make sense - the remote DB2 that I am using is a bit slow...
Still a problem in CP02 CR3: [ldimaggi@ldimaggi CP02_CR3]$ cat /opt/CP02_CR2/jboss-soa-p-standalone.4.2.0/jboss-as/server/default/deploy/jbossesb.esb/META-INF/deployment.xml <?xml version="1.0" encoding="UTF-8"?> <jbossesb-deployment> <depends>jboss.jca:service=DataSourceBinding,name=JBossESBDS</depends> <depends>jboss.esb.destination:service=Queue,name=DeadMessageQueue</depends> <depends>jboss.esb:service=MessageStoreDatabaseInitializer</depends> </jbossesb-deployment> [ldimaggi@ldimaggi CP02_CR3]$ diff /opt/CP02_CR2/jboss-soa-p-standalone.4.2.0/jboss-as/server/default/deploy/jbossesb.esb/META-INF/deployment.xml /opt/CP02_CR3/jboss-soa-p-standalone.4.2.0/jboss-as/server/default/deploy/jbossesb.esb/META-INF/deployment.xml <no diff>
The changes are definitely in the SOA branch http://anonsvn.labs.jboss.com/labs/jbossesb/workspace/platform/JBESB_4_2_1_SOA_4_2/product/services/jbossesb/src/main/resources/META-INF/deployment.xml
Differences are here http://viewvc.jboss.org/cgi-bin/viewvc.cgi/labs/labs/jbossesb/workspace/platform/JBESB_4_2_1_SOA_4_2/product/services/jbossesb/src/main/resources/META-INF/deployment.xml?r1=20698&r2=20697&pathrev=20698
There was a miscommunication between Trev and myself, none of the changes associated with this merge were pulled into the build.
Verified fixed in CP02 CR4 build: [ldimaggi@ldimaggi CP02_CR4]$ diff /opt/CP02_CR2/jboss-soa-p-standalone.4.2.0/jboss-as/server/default/deploy/jbossesb.esb/META-INF/deployment.xml /opt/CP02_CR4/jboss-soa-p-standalone.4.2.0/jboss-as/server/default/deploy/jbossesb.esb/META-INF/deployment.xml 5a6,8 > <depends>jboss.esb.destination:service=Queue,name=DataCollectorQueue</depends> > <depends>jboss.esb.destination:service=Queue,name=OperationsCollectorQueue</depends> > <depends>jboss.esb.destination:service=Queue,name=OperationsResultCollectorQueue</depends> [ldimaggi@ldimaggi CP02_CR4]$ diff /opt/CP02_CR2/jboss-soa-p-standalone.4.2.0/jboss-as/server/default/deploy/jbossesb.esb/META-INF/deployment.xml /opt/CP02_CR4/jboss-soa-p.4.2.0/jboss-as/server/production/deploy/jbossesb.esb/META-INF/deployment.xml 5a6,8 > <depends>jboss.esb.destination:service=Queue,name=DataCollectorQueue</depends> > <depends>jboss.esb.destination:service=Queue,name=OperationsCollectorQueue</depends> > <depends>jboss.esb.destination:service=Queue,name=OperationsResultCollectorQueue</depends>