On Wed, Jan 2, 2013 at 9:05 PM, falckburker <[email protected]> wrote: > Has anyone successfully used preserveMessageQos with Oracle AQ? > > When I add "preserveMessageQos=true" to a camel endpoint uri, it causes an > AQjmsException with the reason "JMS-110: Property JMSXDeliveryCount not > writeable". This is occurring on the latest camel 2.8, 2.9 and 2.10, and on > the latest Oracle 10g and 11g. > > In a camel route, when placing the message on the destination queue, the > JmsMessageHelper call to removeJmsProperty involves clearing out the oracle > AQjmsMessage properties and then adding back all of those properties not > intended to be deleted. I don't believe this is a permission issue in my > oracle configuration, it's probably just how oracle decided to uphold the > jms spec (not allowing "JMSXDeliveryCount" and the like to be altered/set by > the client). > > I'm not sure if the fix here needs to be in camel or oracle... >
Do you have a stacktrace? We can try to get that fixed out of the box in Camel. > Suggestions? > Remove that header before sending the the QA queue. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Using-preserveMessageQos-causes-AQjmsException-in-Oracle-AQ-tp5724797.html > Sent from the Camel Development mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. FuseSource is now part of Red Hat Email: [email protected] Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
