Return-Path: 
 <users-return-17234-apmail-camel-users-archive=camel.apache.org@camel.apache.org>
Delivered-To: apmail-camel-users-archive@www.apache.org
Received: (qmail 28624 invoked from network); 8 Dec 2010 10:04:23 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 8 Dec 2010 10:04:23 -0000
Received: (qmail 63966 invoked by uid 500); 8 Dec 2010 10:04:22 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 63917 invoked by uid 500); 8 Dec 2010 10:04:22 -0000
Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@camel.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@camel.apache.org>
List-Post: <mailto:users@camel.apache.org>
List-Id: <users.camel.apache.org>
Reply-To: users@camel.apache.org
Delivered-To: mailing list users@camel.apache.org
Received: (qmail 63735 invoked by uid 99); 8 Dec 2010 10:04:21 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Dec 2010 10:04:21 +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; Wed, 08 Dec 2010 10:04:16 +0000
Received: from sam.nabble.com ([192.168.236.26])
	by kuber.nabble.com with esmtp (Exim 4.63)
	(envelope-from <martinh@innoq.com>)
	id 1PQGsN-0004PM-CB
	for users@camel.apache.org; Wed, 08 Dec 2010 02:03:55 -0800
Date: Wed, 8 Dec 2010 02:03:55 -0800 (PST)
From: waterback <martinh@innoq.com>
To: users@camel.apache.org
Message-ID: <1291802635358-3297118.post@n5.nabble.com>
In-Reply-To: 
 <OF8D03ED07.18341F73-ONCA2577F1.008216AC-CA2577F2.001BD1CE@email.zurich.com>
References: 
 <OF8D03ED07.18341F73-ONCA2577F1.008216AC-CA2577F2.001BD1CE@email.zurich.com>
Subject: Re: Camel Websphere MQ Error 2012
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit


Hi Marbor,

so to say obviously wrong is a lot... But i had some success with WebSphere
and WebSphere MQ and Camel and not using too much of those
WebSphere-Configurations for Queues.

I've seen in your Spring-Config, that you have those Queues configured and
you look them up via JNDI.

As far as what i could experience that's not necessary when you know the
Queue's name.

Just have the Connection Factory looked up via JNDI maybe like this:

	<bean id="txman"
		class="org.springframework.transaction.jta.WebSphereUowTransactionManager"
/>

	<jee:jndi-lookup id="jmshostcf" jndi-name="java:comp/env/jms/vslmqmgr"
		cache="true" />
		
	<bean id="ibmmqzap" class="org.apache.camel.component.jms.JmsComponent">
		<property name="connectionFactory" ref="jmshostcf" />
		<property name="transactionManager" ref="txman" />
		<property name="transacted" value="true" />
	</bean>

And then you could configure your routes like this:
     ....
     .to("ibmmqzap:queue:${zap.s2.jms.outq}?cacheLevelName=CACHE_NONE")

while "zap.s2.jms.outq" defines the queue name... (and don't forget that
cacheLevel-Stuff!)

As you can see no need to lookup the queue via jndi. 
But I have no experience with the way you tried it. Sorry, i can't tell, if
this should work or not.

This is code from my project, running on a WebSphere 6.1 with WMQ and Camel
2.2 (but that should make no difference to your 2.5 in that regard)

Hopefully that'll help you.



-- 
View this message in context: http://camel.465427.n5.nabble.com/Camel-Websphere-MQ-Error-2012-tp3295312p3297118.html
Sent from the Camel - Users mailing list archive at Nabble.com.