Return-Path: X-Original-To: apmail-camel-dev-archive@www.apache.org Delivered-To: apmail-camel-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 03D70E78A for ; Wed, 2 Jan 2013 20:05:37 +0000 (UTC) Received: (qmail 6962 invoked by uid 500); 2 Jan 2013 20:05:36 -0000 Delivered-To: apmail-camel-dev-archive@camel.apache.org Received: (qmail 6903 invoked by uid 500); 2 Jan 2013 20:05:36 -0000 Mailing-List: contact dev-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list dev@camel.apache.org Received: (qmail 6802 invoked by uid 99); 2 Jan 2013 20:05:36 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Jan 2013 20:05:36 +0000 X-ASF-Spam-Status: No, hits=2.0 required=5.0 tests=SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Jan 2013 20:05:29 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1TqUYm-0002Do-AT for dev@camel.apache.org; Wed, 02 Jan 2013 12:05:08 -0800 Date: Wed, 2 Jan 2013 12:05:08 -0800 (PST) From: falckburker To: dev@camel.apache.org Message-ID: <1357157108226-5724797.post@n5.nabble.com> Subject: Using preserveMessageQos causes AQjmsException in Oracle AQ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org 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... Suggestions? -- 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.