Sorry forgot to mention that ${zap.s2.jms.outq}
is a Property-Placeholder in Spring-Config.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-Websphere-MQ-Error-2012-tp3295312p3297122.html
Sent from the Camel - Users mailing list archive at Nabble.com.
http://camel.465427.n5.nabble.com/Camel-Websphere-MQ-Error-2012-tp3295312p3297118.html
Sent from the Camel - Users mailing list archive at Nabble.com.
7;m leaning towards this being a Websphere MQ issue. I'm going to raise a
support request when I get back from holidays.
Thanks,
Mark
Mark Borner
Java Developer - ZStream Xpress
From:
Claus Ibsen
To:
users@camel.apache.org
Date:
07/12/2010 07:36 PM
Subject:
Re: Camel Websphere MQ Error
Obviously you should check out first with IBM what that MQ error code means.
On Tue, Dec 7, 2010 at 6:03 AM, Mark Borner wrote:
>
> Hi all:
>
> I've been reading up on how to configure Camel for use under Websphere and
> Websphere MQ. I've gotten things working except for a nagging error:
> co
Hi all:
I've been reading up on how to configure Camel for use under Websphere and
Websphere MQ. I've gotten things working except for a nagging error:
com.ibm.mq.MQException: MQJE001: Completion Code 2, Reason 2012
The route that is having the problem is reading from a DB and putting the
me
