[mule-user] Problem with jms outbound and ActiveMQ -Caught exception in Exception Strategy: null
Geir Arnesen
We have an inbound jms endpoint, and a outbound jms endpoint. I got Caught
exception in Exception Strategy: null
java.lang.NullPointerException
Have tried with success replacing the outbound endpoint with a file endoint.
008-03-13 18:37:22,654 [DEBUG ] [vmConnector.receiver.4]
no.aftenposten.mule.di.ws.mock.DummyTransformer - Object after transform:
<?xml version="1.0" encoding="iso-8859-1"?><SiebelMessage
MessageId="1-49MQ"
IntObjectName="AP01 MACD Performance Order"
MessageType="Integration Object"
IntObjectFormat="Siebel Hierarchical"
><Li...
2008-03-13 18:37:22,654 [DEBUG ] [vmConnector.receiver.4]
no.aftenposten.mule.di.ws.mock.DummyTransformer - The transformed object is
of expected type. Type is: String
2008-03-13 18:37:22,662 [ERROR ] [activeMQConnector.dispatcher.1]
org.mule.impl.DefaultComponentExceptionStrategy - Caught exception in
Exception Strategy: null
java.lang.NullPointerException
at
org.apache.activemq.command.ActiveMQTempDestination.delete(ActiveMQTempDestination.java:50)
at org.mule.providers.jms.JmsConnector.close(JmsConnector.java:1035)
at org.mule.providers.jms.JmsConnector.closeQuietly(JmsConnector.java:1049)
at
org.mule.providers.jms.JmsMessageDispatcher.dispatchMessage(JmsMessageDispatcher.java:309)
at
org.mule.providers.jms.JmsMessageDispatcher.doDispatch(JmsMessageDispatcher.java:64)
at
org.mule.providers.AbstractMessageDispatcher$Worker.run(AbstractMessageDispatcher.java:561)
at org.mule.impl.work.WorkerContext.run(WorkerContext.java:310)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:650)
at
edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:675)
at java.lang.Thread.run(Thread.java:613)
2008-03-13 18:37:22,663 [ERROR ] [activeMQConnector.dispatcher.1]
org.mule.impl.DefaultComponentExceptionStrategy - Message being processed
is:
org.mule.providers.DefaultMessageAdapter/org.mule.providers.DefaultMessageAdapter@5b5f7e{id=ID:AF-IM-701.local-63927-1205429841640-1:0:1:1:1,
payload=java.lang.String,
correlationId=231b4b12-f124-11dc-8cd3-3bf31e860e37, correlationGroup=-1,
correlationSeq=-1, encoding=UTF-8, exceptionPayload=null, properties={
MULE_ORIGINATING_ENDPOINT=endpoint.vm.siebel.subscription.create.ab.in
MULE_REMOTE_SYNC=true
JMSDeliveryMode=1
JMSCorrelationID=231b4b12-f124-11dc-8cd3-3bf31e860e37
JMSMessageID=ID:AF-IM-701.local-63927-1205429841640-1:0:1:1:1
JMSDestination=queue://siebel.in
connector=activeMQConnector
JMSTimestamp=1205429842643
JMSExpiration=0
JMSRedelivered=false
JMSPriority=4
MULE_SESSION=SUQ9MjMxYzM1NzMtZjEyNC0xMWRjLThjZDMtM2JmMzFlODYwZTM3O0lEPTIzMWMzNTczLWYxMjQtMTFkYy04Y2QzLTNiZjMxZTg2MGUzNw==
MULE_ENDPOINT=jms://siebel.subscription.create.ab.in?connector=activeMQConnector
MULE_CORRELATION_ID=231b4b12-f124-11dc-8cd3-3bf31e860e37
}}
2008-03-13 18:37:22,689 [DEBUG ] [activeMQConnector.dispatcher.1]
org.apache.activemq.ActiveMQSession - Sending message: ActiveMQObjectMessage
{commandId = 0, responseRequired = false, messageId =
ID:AF-IM-701.local-63912-1205429797293-1:0:8:1:1, originalDestination =
null, originalTransactionId = null, producerId =
ID:AF-IM-701.local-63912-1205429797293-1:0:8:1, destination =
queue://ERROR.QUEUE, transactionId = null, expiration = 0, timestamp =
1205429842677, arrival = 0, correlationId =
231b4b12-f124-11dc-8cd3-3bf31e860e37, replyTo =
temp-queue://ID:AF-IM-701.local-63912-1205429797293-1:0:2, persistent =
true, type = null, priority = 4, groupID = null, groupSequence = 0,
targetConsumerId = null, compressed = false, userID = null, content =
org.apache.activemq.util.ByteSequence@f4ebfe, marshalledProperties = null,
dataStructure = null, redeliveryCounter = 0, size = 0, properties =
{MULE_REMOTE_SYNC=true,
MULE_CORRELATION_ID=231b4b12-f124-11dc-8cd3-3bf31e860e37,
MULE_ENDPOINT=jms://ERROR.QUEUE?connector=activeMQConnector,
connector=activeMQConnector,
MULE_ORIGINATING_ENDPOINT=endpoint.vm.siebel.subscription.create.ab.in},
readOnlyProperties = true, readOnlyBody = true, droppable = false}
--
View this message in context: http://www.nabble.com/Problem-with-jms-outbound-and-ActiveMQ--Caught-exception-in-Exception-Strategy%3A-null-tp16033109p16033109.html
Sent from the Mule - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
Geir Arnesen
I replied to a wrong thread (my own published)
I solved the problem by adding this transformer to the jms outbound
endpoint:
I found a solution by adding a MessagePropertiesTransformer on the outbound
jms endpoint, - stripping of the JMSReplyTo property
<transformer name="MessagePropertiesTransformer"
className="org.mule.transformers.simple.MessagePropertiesTransformer" >
<properties>
<map name="deletProperties">
<property name="JMSReplyTo" value=""/>
</map>
</properties>
</transformer>
--
View this message in context: http://www.nabble.com/Problem-with-jms-outbound-and-ActiveMQ--Caught-exception-in-Exception-Strategy%3A-null-tp16033109p16039996.html
David Dossot
<list name="deleteProperties">
<entry value="JMSReplyTo"/>
</list>
instead of the map?
D.
Geir Arnesen
Agree! and this worked perferct. Wasn't aware of the map. Just saw how the
MessagePropertiesTransformer was just in another case.
--
View this message in context: http://www.nabble.com/Problem-with-jms-outbound-and-ActiveMQ--Caught-exception-in-Exception-Strategy%3A-null-tp16033109p16044469.html