[mule-user] JMS Reply To Dispatch Exceptions: Mule 2, Active MQ 4.1.2

0 views

Skip to first unread message

HoyaBoya

unread,

Jun 6, 2008, 11:18:00 AM6/6/08

to us...@mule.codehaus.org

Hi All,

We're migrating an application from Mule 1.4.x to Mule 2.0.0. The
application works fine post-migration but I am seeing exceptions with
respect to several of our JMS endpoints where Mule is trying to dispatch the
message to the replyTo JMS destination which is no longer there.

I've tried to configure our work flow to not need to "respond" over JMS, but
nothing seems to take. Does anyone have any ideas?

The exception (multiply this out by the number of JMS endpoints we have in
our workflow)

********************************************************************************
Message : Failed to create and dispatch response event over
Jms destination
"temp-queue://ID:intencode01.sling.com-51180-1212764575460-2:0:1". Failed to
route event via endpoint: null. Message payload is of type:
ActiveMQObjectMessage
Type : org.mule.api.transport.DispatchException
Code : MULE_ERROR-42999
Payload : ActiveMQObjectMessage {commandId = 0,
responseRequired = false, messageId = null, originalDestination = null,
originalTransactionId = null, producerId = null, destination = null,
transactionId = null, expiration = 0, timestamp = 0, arrival = 0,
correlationId = a5eceb5e-33d9-11dd-9c23-059fcbec1c7b, replyTo = null,
persistent = false, type = null, priority = 0, groupID = null, groupSequence
= 0, targetConsumerId = null, compressed = false, userID = null, content =
org.apache.activemq.util.ByteSequence@3bf0d7f5, marshalledProperties = null,
dataStructure = null, redeliveryCounter = 0, size = 0, properties =
{Accept_Encoding=gzip, deflate, User_Agent=Mozilla/5.0 (Macintosh; U; Intel
Mac OS X 10_5_3; en-us) AppleWebKit/525.18 (KHTML, like Gecko) Version/3.1.1
Safari/525.20, Cookie=s_lastvisit=1209652755991, http_request=/clip,
Host=ec2-72-44-52-193.compute-1.amazonaws.com:9002, http_version=HTTP/1.1,
MULE_ENDPOINT=vm://finish, MULE_ORIGINATING_ENDPOINT=FINISH,
Connection=true, Content_Type=multipart/form-data;
boundary=----WebKitFormBoundaryyzq148HhtETAIaDA, http_method=POST,
Content_Length=9122736, replyTo=BOB, Accept_Language=en-us,
MULE_CORRELATION_ID=a5eceb5e-33d9-11dd-9c23-059fcbec1c7b,
Referer=http://ec2-72-44-52-193.compute-1.amazonaws.com:9080/uploadclip.html,
MULE_REMOTE_CLIENT_ADDRESS=/65.46.75.10:61841, MULE_REMOTE_SYNC=true,
Accept=text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5},
readOnlyProperties = false, readOnlyBody = false, droppable = false}
JavaDoc :
http://mule.mulesource.org/docs/apidocs/org/mule/api/transport/DispatchException.html
JMS Code : null
********************************************************************************
Exception stack is:
1. Cannot publish to a deleted Destination:
temp-queue://ID:intencode01.sling.com-51180-1212764575460-2:0:1(JMS Code:
null) (javax.jms.JMSException)
org.apache.activemq.ActiveMQSession:1500
(http://java.sun.com/j2ee/sdk_1.3/techdocs/api/javax/jms/JMSException.html)
2. Failed to create and dispatch response event over Jms destination
"temp-queue://ID:intencode01.sling.com-51180-1212764575460-2:0:1". Failed to
route event via endpoint: null. Message payload is of type:
ActiveMQObjectMessage (org.mule.api.transport.DispatchException)
org.mule.transport.jms.JmsReplyToHandler:147
(http://mule.mulesource.org/docs/apidocs/org/mule/api/transport/DispatchException.html)
********************************************************************************
Root Exception stack trace:
javax.jms.JMSException: Cannot publish to a deleted Destination:
temp-queue://ID:intencode01.sling.com-51180-1212764575460-2:0:1
at org.apache.activemq.ActiveMQSession.send(ActiveMQSession.java:1500)
at
org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:465)
at
org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:384)
at org.mule.transport.jms.Jms11Support.send(Jms11Support.java:169)
at org.mule.transport.jms.Jms11Support.send(Jms11Support.java:151)
at
org.mule.transport.jms.JmsReplyToHandler.processReplyTo(JmsReplyToHandler.java:113)
at
org.mule.service.AbstractService.processReplyTo(AbstractService.java:848)
at org.mule.model.seda.SedaService.doSend(SedaService.java:237)
at org.mule.service.AbstractService.sendEvent(AbstractService.java:510)
at org.mule.DefaultMuleSession.sendEvent(DefaultMuleSession.java:351)
at
org.mule.routing.inbound.DefaultInboundRouterCollection.send(DefaultInboundRouterCollection.java:196)
at
org.mule.routing.inbound.DefaultInboundRouterCollection.route(DefaultInboundRouterCollection.java:164)
at
org.mule.transport.AbstractMessageReceiver$DefaultInternalMessageListener.onMessage(AbstractMessageReceiver.java:604)
at
org.mule.transport.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:346)
at
org.mule.transport.AbstractReceiverWorker$1.doInTransaction(AbstractReceiverWorker.java:114)
at
org.mule.transaction.TransactionTemplate.execute(TransactionTemplate.java:112)
at
org.mule.transport.AbstractReceiverWorker.doRun(AbstractReceiverWorker.java:131)
at
org.mule.transport.AbstractReceiverWorker.run(AbstractReceiverWorker.java:62)
at org.mule.work.WorkerContext.run(WorkerContext.java:310)
at org.mule.work.SyncWorkExecutor.doExecute(SyncWorkExecutor.java:41)
at org.mule.work.MuleWorkManager.executeWork(MuleWorkManager.java:269)
at org.mule.work.MuleWorkManager.doWork(MuleWorkManager.java:157)
at
org.mule.transport.jms.MultiConsumerJmsMessageReceiver$SubReceiver.onMessage(MultiConsumerJmsMessageReceiver.java:264)
at
org.apache.activemq.ActiveMQMessageConsumer.dispatch(ActiveMQMessageConsumer.java:854)
at
org.apache.activemq.ActiveMQSessionExecutor.dispatch(ActiveMQSessionExecutor.java:104)
at
org.apache.activemq.ActiveMQSessionExecutor.iterate(ActiveMQSessionExecutor.java:171)
at
org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:120)
at
org.apache.activemq.thread.PooledTaskRunner.access$100(PooledTaskRunner.java:26)
at
org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:47)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)
at java.lang.Thread.run(Thread.java:619)

Our mule-config.xml endpoints and connectors:

<vm:connector name="syncVm" />
<vm:connector name="asyncVm" queueEvents="true" />

<jms:activemq-connector name="jmsConnector" specification="1.1"
durable="false" clientId="medbiabus2" acknowledgementMode="AUTO_ACKNOWLEDGE"
persistentDelivery="true" eagerConsumer="false"
recoverJmsConnections="true"/>

<vm:endpoint name="TEST_VM_Q" path="test.vm.q" connector-ref="asyncVm"
synchronous="false"/>
<vm:endpoint name="RESPONSE_SLING" path="response.sling"
connector-ref="asyncVm" synchronous="false"/>

<jms:endpoint name="DOWNLOAD" queue="download" synchronous="false"/>

<vm:endpoint name="ADMIN_FILTH_FILTER" path="admin.filth.filter"
connector-ref="asyncVm" synchronous="false"/>
<vm:endpoint name="VIDEO_FILTH_FILTER" path="video.filth.filter"
connector-ref="asyncVm" synchronous="false"/>
<vm:endpoint name="IMAGE_FILTH_FILTER" path="image.filth.filter"
connector-ref="asyncVm" synchronous="false"/>

<jms:endpoint name="ENCODE_BROADCAST" topic="encode.broadcast?replyTo=BOB"
synchronous="false" remoteSync="false"/>

<vm:endpoint name="FLV_PROGRESSIVE_SCAN_INJECTION"
path="flv.progressive.scan.injection" connector-ref="asyncVm"
synchronous="false"/>
<vm:endpoint name="IMAGE_CONVERT" path="image.convert"
connector-ref="asyncVm" synchronous="false"/>
<vm:endpoint name="CDN_UPLOAD" path="cdn.upload" connector-ref="asyncVm"
synchronous="false"/>
<vm:endpoint name="METADATA_SAVE" path="metadata.save"
connector-ref="asyncVm" synchronous="false"/>
<vm:endpoint name="CLEANUP" path="cleanup" connector-ref="asyncVm"
synchronous="false"/>
<vm:endpoint name="ENCODE_VERIFICATION" path="encode.verification"
connector-ref="asyncVm"/>
<vm:endpoint name="FINISH" path="finish" connector-ref="asyncVm"
synchronous="false"/>
<vm:endpoint name="QUEUE_BRIDGE" path="queue.bridge"
connector-ref="asyncVm" synchronous="false"/>
<vm:endpoint name="QUEUE_ERROR" path="queue.error" connector-ref="asyncVm"
synchronous="false"/>

--
View this message in context: http://www.nabble.com/JMS-Reply-To-Dispatch-Exceptions%3A-Mule-2%2C-Active-MQ-4.1.2-tp17694720p17694720.html
Sent from the Mule - User mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe from this list, please visit: