After upgrading from 1.5.0 to 1.6.1, we find that that exception clauses such
as this one
<onException>
<exception>my.package.SomeException</exception>
<redeliveryPolicy maximumRedeliveries="0" />
<handled>
<constant>true</constant>
</handled>
<to ref="tpforholdArbeidskoe" />
</onException>
cause the message body to be *empty* after the message has been moved to
tpforholdArbeidskoe.
(tpforholdArbeidskoe is a message queue on ActiveMQ, as is the route's
from-endpoint).
The following trace may be of relevance:
---------------------------------------------------
17:11:20,844 ERROR [STDERR] 17.jun.2009 17:11:20
org.apache.camel.component.jms.JmsProducer process
WARNING: Disabling JMSReplyTo as this Exchange is not OUT capable:
Exchange[JmsMessage: ActiveMQTextMessage {commandId =
8, responseRequired = false, messageId =
ID:vmutvjee1-b58-2757-1245247294282-2:3:1:1:4, originalDestination = null,
ori
ginalTransactionId = null, producerId =
ID:vmutvjee1-b58-2757-1245247294282-2:3:1:1, destination =
queue://queue.samordn
ing.TPForhold, transactionId = null, expiration = 0, timestamp =
1245251471047, arrival = 0, brokerInTime = 124525147106
3, brokerOutTime = 1245251471063, correlationId = , replyTo = null,
persistent = false, type = , priority = 0, groupID =
null, groupSequence = 0, targetConsumerId = null, compressed = false,
userID = null, content = null, marshalledProperti
es = null, dataStructure = null, redeliveryCounter = 0, size = 0, properties
= null, readOnlyProperties = true, readOnly
Body = true, droppable = false, text = <?xml version="1.0"
encoding="UTF-8"?>
<TPForholdHendelse>
<type>Opprett</type>
<ordning>1015</ordning>
<datKundeFoedtNum>xxxxxxx</datKundeFoedtNum>
<ideKundePrsnr>xxxxxx</ideKundePrsnr>
</TPForholdHendelse>
}] with destination: queue.samordning.TPForholdTilArbeidskoe
17:11:20,860 ERROR [STDERR] 17.jun.2009 17:11:20
org.apache.camel.processor.Logger log
SEVERE: Failed delivery for exchangeId:
ID-vmutvjee1-b58/3030-1245251235079/0-0. Handled by the failure processor:
Trace
Interceptor[To[ref:tpforholdArbeidskoe]]
17:11:20,875 ERROR [STDERR] 17.jun.2009 17:11:20
org.apache.camel.processor.Logger process
INFO: ID-vmutvjee1-b58/3030-1245251235079/2-1 -> choice(), Pattern:InOnly ,
Headers:{JMSTimestamp=1245251480860, org.apa
che.camel.MultiParameterArray=false, JMSType=,
org.apache.camel.RedeliveryCounter=0, JMSXGroupID=null, JMSReplyTo=null,
JMSDestination=queue://queue.samordning.TPForholdTilArbeidskoe,
JMSRedelivered=false, JMSExpiration=0, org.apache.camel.
Redelivered=false,
JMSMessageID=ID:vmutvjee1-b58-3023-1245251233625-0:642:1:1:1,
JMSDeliveryMode=2, JMSCorrelationID=, J
MSPriority=4} , BodyType:null , Body:null
---------------------------------------------------
Anyone know the reason why we lose the message body?
- Rune
--
View this message in context:
http://www.nabble.com/Message-body-lost-when-message-moved-by-exception-clause-tp24088536p24088536.html
Sent from the Camel - Users mailing list archive at Nabble.com.
