MDB's and destination creation
thammoud Mar 14, 2011 9:52 AMHi,
We are in the process of moving from 4.x to 6.x and are having issues with HornetQ deployment. We are receiving the following exception when the server comes up:
08:42:33,084 WARN [HornetQActivation] Failure in HornetQ activation org.hornetq.ra.inflow.HornetQActivationSpec(ra=org.hornetq.ra.HornetQResourceAdapter@796f15db destination=topic/Beta destinationType=javax.jms.Topic ack=Auto-acknowledge durable=false clientID=null user=null maxSession=15): HornetQException[errorCode=105 message=Unable to validate user: null for check type CREATE_NON_DURABLE_QUEUE for address jms.topic.Beta]
at org.hornetq.core.protocol.core.impl.ChannelImpl.sendBlocking(ChannelImpl.java:287) [:6.0.0.Final]
at org.hornetq.core.client.impl.ClientSessionImpl.internalCreateQueue(ClientSessionImpl.java:1627) [:6.0.0.Final]
at org.hornetq.core.client.impl.ClientSessionImpl.createQueue(ClientSessionImpl.java:290) [:6.0.0.Final]
at org.hornetq.core.client.impl.DelegatingSession.createQueue(DelegatingSession.java:283) [:6.0.0.Final]
at org.hornetq.ra.inflow.HornetQMessageHandler.setup(HornetQMessageHandler.java:153) [:6.0.0.Final]
at org.hornetq.ra.inflow.HornetQActivation.setup(HornetQActivation.java:291) [:6.0.0.Final]
at org.hornetq.ra.inflow.HornetQActivation$SetupActivation.run(HornetQActivation.java:573) [:6.0.0.Final]
at org.jboss.resource.work.WorkWrapper.run(WorkWrapper.java:172) [:6.0.0.Final]
at org.jboss.threads.SimpleDirectExecutor.execute(SimpleDirectExecutor.java:33) [:2.0.0.CR7]
at org.jboss.threads.QueueExecutor.runTask(QueueExecutor.java:801) [:2.0.0.CR7]
at org.jboss.threads.QueueExecutor.access$100(QueueExecutor.java:45) [:2.0.0.CR7]
at org.jboss.threads.QueueExecutor$Worker.run(QueueExecutor.java:842) [:2.0.0.CR7]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_24]
at org.jboss.threads.JBossThread.run(JBossThread.java:122) [:2.0.0.CR7]
We have placed a hornetq-jms.xml in the root on the ear file.
<configuration xmlns="urn:hornetq"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="urn:hornetq /schema/hornetq-jms.xsd">
<topic name="StockSplit">
<entry name="/topic/StockSplit"/>
</topic>
.....
</configuration>
Eventually, the deployment works and MDB "reconnects". It seems like there is some order dependency. Perhaps, we need to force the hornetq-jms.xml to be deployed first. How do accomplish that without dependency logic in the hundred's of MDB's that we have? Thank yu very much.
Tarek