Re: JMS exceptions in Mule 2.2.1

Please do file a jira. It also seems that if you set specification on the jms connector to 1.1 the error will go away.

HTH,
Andrew

On Jul 2, 2009 7:09 PM, "Ron Fulkerson" <ron.fulkerson@...> wrote:

Hi,

This works, thank you!  It was immensely helpful to have a working example to test configuration changes against, etc..  Doing so allowed me to eventually track down the final issue that was preventing me from progressing - one small bug.

The <reply-to> tag must be used with an address attribute.  Using a ref attribute works with queues, but does not work with topics.  Topics in a reply-to ref tag cause a ClassCastException (pasted below with config).  I also tested this in 2.1.2 and had the same results.  Do you want a jira filed for this issue?

Fortunately this is easy enough to work around, and I am now enjoying Mule 2.2.1!

Thanks again for all the help,
Ron

ERROR 2009-07-02 15:57:59,247 [jmsConnector.dispatcher.1] org.mule.DefaultExceptionStrategy: Caught exception in Exception Strategy: org.apache.activemq.ActiveMQTopicSession cannot be cast to javax.jms.QueueSession
java.lang.ClassCastException: org.apache.activemq.ActiveMQTopicSession cannot be cast to javax.jms.QueueSession
      at org.mule.transport.jms.Jms102bSupport.createDestination(Jms102bSupport.java:219)
      at org.mule.transport.jms.JmsMessageDispatcher.getReplyToDestination(JmsMessageDispatcher.java:477)
      at org.mule.transport.jms.JmsMessageDispatcher.dispatchMessage(JmsMessageDispatcher.java:171)
      at org.mule.transport.jms.JmsMessageDispatcher.doDispatch(JmsMessageDispatcher.java:73)
      at org.mule.transport.AbstractMessageDispatcher$Worker.run(AbstractMessageDispatcher.java:262)
      at org.mule.work.WorkerContext.run(WorkerContext.java:310)

<?xml version="1.0" encoding="UTF-8"?> <mule xmlns="http://www.mulesource.org/schema/mule/core/2.2...

    <jms:activemq-connector name="jmsConnector" brokerURL="tcp://localhost:4101" disableTemporaryReplyToDestinations="true"/>

  <stdio:connector name="SystemStreamConnector" promptMessage="Please enter something:" messageDel...

    <jms:endpoint name="RequestRef" topic="request" connector-ref="jmsConnector"/>
  <jms:endpoint name="ReplyRef" topic="reply" connector-ref="jmsConnector"/>

    <model name="jms-test-suite">                     <service name="EchoUMO">           <inbound> ...

                  <outbound-endpoint ref="RequestRef" synchronous="true"/>
                  <reply-to ref="ReplyRef"/>

              </chaining-router>           </outbound>           <async-reply timeout="10000" failO...

              <inbound-endpoint ref="ReplyRef"/>

              <single-async-reply-router/>           </async-reply>       </service>       <servic...

              <inbound-endpoint ref="RequestRef" synchronous="true"/>

          </inbound>           <echo-component />       </service>   </model> </mule> Puneet Gup...

> > I tested the below config in 2.2.1-EE and it worked fine. The log shows that the reply was sent ...