[
https://issues.apache.org/jira/browse/CAMEL-10237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15420652#comment-15420652
]
Preben Asmussen commented on CAMEL-10237:
-----------------------------------------
Digged a bit into this.
Turns out that it's only the JMSXUserID that is the problem. If I remove
setting the JMSXUserID from
https://github.com/apache/camel/blob/master/components/camel-jms/src/main/java/org/apache/camel/component/jms/JmsBinding.java#L184
it works on OracleAQ.
Still there is a sligt difference in which JMSX headers get's populated between
2.17.1 and 2.17.2->
2.17.2 and newer ->
JMS_OracleDelay=0, JMS_OracleDeliveryMode=2, JMS_OracleTimestamp=1471240798892,
JMSCorrelationID=null, JMSCorrelationIDAsBytes=null, JMSDeliveryMode=2,
JMSDestination=INTAQ.YARN_UPDATE_HUB, JMSExpiration=0,
JMSMessageID=ID:3A16F131215794F4E053B50D650A06C2, JMSPriority=1,
JMSRedelivered=false, JMSReplyTo=null, JMSTimestamp=1471240798892,
JMSType=null, JMSXGroupID=null}
2.17.1->
JMS_OracleDelay=0, JMS_OracleDeliveryMode=2, JMS_OracleTimestamp=1471240970894,
JMSCorrelationID=null, JMSCorrelationIDAsBytes=null, JMSDeliveryMode=2,
JMSDestination=INTAQ.YARN_UPDATE_HUB, JMSExpiration=0,
JMSMessageID=ID:3A16FB721A86BFA8E053B50D650AA65F, JMSPriority=1,
JMSRedelivered=false, JMSReplyTo=null, JMSTimestamp=1471240970894,
JMSType=null, JMSXDeliveryCount=1, JMSXGroupID=null,
JMSXRecvTimestamp=1471240970965, JMSXState=0, JMSXUserID=INTAQ}
> Problem setting JMSX jms properties on OracleAQ
> -----------------------------------------------
>
> Key: CAMEL-10237
> URL: https://issues.apache.org/jira/browse/CAMEL-10237
> Project: Camel
> Issue Type: Bug
> Components: camel-jms
> Affects Versions: 2.17.2, 2.17.3
> Reporter: Preben Asmussen
> Fix For: 2.18.0, 2.17.4
>
>
> See description in
> http://camel.465427.n5.nabble.com/possible-camel-jms-regression-in-2-17-2-td5786290.html
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
