Issue Details (XML | Word | Printable)

Key: MULE-3823
Type: Bug Bug
Status: Reopened Reopened
Priority: Major Major
Assignee: Unassigned
Reporter: Daniel Zapata
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Mule

loanbroker example has javax.jms.JMSException: Cannot publish to a deleted Destination error

Created: 10/Oct/08 06:40 PM   Updated: 12/Dec/08 03:37 AM
Component/s: Examples / Tutorials, Transport: JMS
Affects Version/s: 2.1.0
Fix Version/s: 2.1.x Backlog

Time Tracking:
Not Specified

Issue Links:
Related
 

Labels:
User impact: Low
Log Output:
ERROR 2008-10-10 15:39:08,316 [ActiveMQ Session Task] org.mule.service.DefaultServiceExceptionStrategy:
********************************************************************************
Message : Failed to create and dispatch response event over Jms destination "temp-queue://ID:x300zapata-47862-1223681939233-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
JMS Code : null
JavaDoc : http://www.mulesource.org/docs/site/current2/apidocs/org/mule/api/transport/DispatchException.html
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 = ID:x300zapata-47862-1223681939233-2:0:19:1:1, replyTo = null, persistent = false, type = null, priority = 0, groupID = null, groupSequence = 0, targetConsumerId = null, compressed = false, userID = null, content = org.apache.activemq.util.ByteSequence@e265f5, marshalledProperties = null, dataStructure = null, redeliveryCounter = 0, size = 0, properties = {MULE_REMOTE_SYNC=true, MULE_CORRELATION_ID=9fb3cb5e-9724-11dd-bd47-eb139eebbf62, MULE_ENDPOINT=jms://esb.lender.service, MULE_ORIGINATING_ENDPOINT=LenderGateway, method=getCreditProfile}, readOnlyProperties = false, readOnlyBody = false, droppable = false}
********************************************************************************
Exception stack is:
1. Cannot publish to a deleted Destination: temp-queue://ID:x300zapata-47862-1223681939233-2:0:1(JMS Code: null) (javax.jms.JMSException)
  org.apache.activemq.ActiveMQSession:1498 (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:x300zapata-47862-1223681939233-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:150 (http://www.mulesource.org/docs/site/current2/apidocs/org/mule/api/transport/DispatchException.html)
********************************************************************************
Root Exception stack trace:
javax.jms.JMSException: Cannot publish to a deleted Destination: temp-queue://ID:x300zapata-47862-1223681939233-2:0:1
at org.apache.activemq.ActiveMQSession.send(ActiveMQSession.java:1498)
at org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:465)
at org.apache.activemq.ActiveMQMessageProducer.send(ActiveMQMessageProducer.java:384)
at org.mule.transport.jms.Jms102bSupport.send(Jms102bSupport.java:231)
at org.mule.transport.jms.Jms11Support.send(Jms11Support.java:191)
at org.mule.transport.jms.JmsReplyToHandler.processReplyTo(JmsReplyToHandler.java:122)
at org.mule.service.AbstractService.processReplyTo(AbstractService.java:842)
at org.mule.model.seda.SedaService.doSend(SedaService.java:232)
at org.mule.service.AbstractService.sendEvent(AbstractService.java:505)
at org.mule.DefaultMuleSession.sendEvent(DefaultMuleSession.java:354)
at org.mule.routing.inbound.DefaultInboundRouterCollection.send(DefaultInboundRouterCollection.java:220)
at org.mule.routing.inbound.DefaultInboundRouterCollection.route(DefaultInboundRouterCollection.java:180)
at org.mule.transport.AbstractMessageReceiver$DefaultInternalMessageListener.onMessage(AbstractMessageReceiver.java:365)
at org.mule.transport.AbstractMessageReceiver.routeMessage(AbstractMessageReceiver.java:253)
at org.mule.transport.AbstractReceiverWorker$1.doInTransaction(AbstractReceiverWorker.java:114)
at org.mule.transaction.TransactionTemplate.execute(TransactionTemplate.java:99)
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:281)
at org.apache.activemq.ActiveMQMessageConsumer.dispatch(ActiveMQMessageConsumer.java:840)
at org.apache.activemq.ActiveMQSessionExecutor.dispatch(ActiveMQSessionExecutor.java:96)
at org.apache.activemq.ActiveMQSessionExecutor.iterate(ActiveMQSessionExecutor.java:165)
at org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:111)
at org.apache.activemq.thread.PooledTaskRunner.access$100(PooledTaskRunner.java:26)
at org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:44)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:987)
at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:528)
at java.lang.Thread.run(Thread.java:595)

********************************************************************************


 Description  « Hide
Running the loanbroker in ESB mode and selecting either:
1. Calling out to a remote EJB using a Mule Endpoint.
2. Managing an EJB as a Mule component.
will generate a correct loan message, but there is also a stack trace (see log output section)

 All   Comments   Work Log   Change History   Transitions   FishEye      Sort Order: Ascending order - Click to sort in descending order
[ Permlink | « Hide ]
Travis Carlson added a comment - 13/Oct/08 06:35 AM
Duplicate of EE-913

[ Permlink | « Hide ]
Travis Carlson added a comment - 13/Oct/08 10:51 AM
Leaving the CE issue open rather than the EE issue


Powered by a free Atlassian JIRA open source license for MuleForge. Try JIRA - bug tracking software for your team.
Atlassian JIRA the Professional Issue Tracker. (Enterprise Edition, Version: 3.13.1-#333) - Bug/feature request - Atlassian news - Contact Administrators