JMS Unknown Destination Error

[danielkalcevich]

I am trying to add a ObjectMessage to my JMS Queue and am getting an unknown destination exception. I am able to connect to the Queue on startup though. Any ideas what could be causing the error?

I am on JBoss 4.0.5-GA and am using a MessageProducer to attempt and sent the message to the Destination.

Daniel

-----
Error:

org.quartz.JobExecutionException: javax.jms.JMSException: Unknown Destination Type [See nested exception: javax.jms.JMSE
xception: Unknown Destination Type]
at com.firstam.mlsdatachecker.quartz.BatchSchedulerJob.executeInternal(BatchSchedulerJob.java:108)
at org.springframework.scheduling.quartz.QuartzJobBean.execute(QuartzJobBean.java:79)
at org.quartz.core.JobRunShell.run(JobRunShell.java:203)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
* Nested Exception (Underlying Cause) ---------------
javax.jms.JMSException: Unknown Destination Type
at org.exolab.jms.message.MessageHeader.setJMSDestination(MessageHeader.java:194)
at org.exolab.jms.message.MessageImpl.setJMSDestination(MessageImpl.java:301)
at org.jboss.mq.SpyMessageProducer.send(SpyMessageProducer.java:257)
at org.jboss.mq.SpyMessageProducer.send(SpyMessageProducer.java:206)
at com.firstam.mlsdatachecker.jms.JMSConnector.sendObjectMessage(JMSConnector.java:229)
at com.firstam.mlsdatachecker.quartz.BatchSchedulerJob.executeInternal(BatchSchedulerJob.java:97)
at org.springframework.scheduling.quartz.QuartzJobBean.execute(QuartzJobBean.java:79)
at org.quartz.core.JobRunShell.run(JobRunShell.java:203)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)

------
Queue Definition:

<mbean code="org.jboss.mq.server.jmx.Queue"
 name="jboss.mq.destination:service=Queue,name=BatchProcess">
 <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
 <depends optional-attribute-name="SecurityManager">jboss.mq:service=SecurityManager</depends>
 <attribute name="MessageCounterHistoryDayLimit">-1</attribute>
 <attribute name="SecurityConf">
 <security>
 <role name="mdc_user" read="true" write="true"/>
 </security>
 </attribute>
 </mbean>

[clebert.suconic]

We are working in a new implementation of JMS, called JBoss Messaging.

JBoss Messaging is a complete rewrite as we are focusing on performance by changing some fundamental things like adding paging support and other things.

By looking at your Queue, you are using the legacy implementation.


If you are in fact using Messaging, you are mixing the definitions what would cause error

If you are not, you are in the wrong forum. You should use the MQ User's forums

[clebert.suconic]

I forgot to say that JBoss Messaging in on 1.0.1.GA already.

It's not the default JMS provider yet (until we release JBoss 5) but you can easily change configurations to have it working as your default. Just look at documentation and you can use a simple ant script to make the configuration change (well.. it will create a new server with the configuration needed)