Return-Path: Delivered-To: apmail-camel-users-archive@www.apache.org Received: (qmail 60636 invoked from network); 12 Nov 2010 09:56:45 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 12 Nov 2010 09:56:45 -0000 Received: (qmail 82850 invoked by uid 500); 12 Nov 2010 09:57:17 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 82611 invoked by uid 500); 12 Nov 2010 09:57:16 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Received: (qmail 82603 invoked by uid 99); 12 Nov 2010 09:57:16 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Nov 2010 09:57:16 +0000 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=SPF_HELO_PASS,SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Nov 2010 09:57:10 +0000 Received: from sam.nabble.com ([192.168.236.26]) by kuber.nabble.com with esmtp (Exim 4.63) (envelope-from ) id 1PGqNF-0007Vw-I3 for users@camel.apache.org; Fri, 12 Nov 2010 01:56:49 -0800 Date: Fri, 12 Nov 2010 01:56:49 -0800 (PST) From: waterback To: users@camel.apache.org Message-ID: <1289555809553-3261737.post@n5.nabble.com> In-Reply-To: References: <1289479506978-3260184.post@n5.nabble.com> <1289549526039-3261601.post@n5.nabble.com> <1289552654997-3261656.post@n5.nabble.com> <1289553768621-3261686.post@n5.nabble.com> Subject: Re: Connect with WebSphere MQ / Single Consumer allowed MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Get your point... i'll try that, hopefully it works, because i read in other posts / forums that exception listeners are not supported in j2ee-Servers (or at least in WebSphere AS) Hopefully i'm not offensive saying that the Camel-Point of view seems to be differing (with the same exception) when the route is started right away with the context. I only get the problem when the route is configured .noAutoStartup() and started eventually. Anyway: Thank you very much for your time... and for that great Book! Martin -- View this message in context: http://camel.465427.n5.nabble.com/Connect-with-WebSphere-MQ-Single-Consumer-allowed-tp3260184p3261737.html Sent from the Camel - Users mailing list archive at Nabble.com.