Here is my sample config:
<bean class="com.ibm.mq.jms.MQConnectionFactory"
depends-on="mqEnvironmentInvoker">
<property name="hostName" value="${rts.mq.hostname}" />
<property name="queueManager" value="${rts.mq.queueManager}"
/>
<property name="port" value="${rts.mq.port}" />
<property name="CCSID" value="${rts.mq.ccsid:819}" />
<property name="channel" value="${rts.mq.channel}" />
<property name="useConnectionPooling"
value="${rts.mq.useConnectionPooling}" />
<property name="targetClientMatching" value="false" />
<property name="transportType">
<util:constant
static-field="com.ibm.msg.client.wmq.WMQConstants.WMQ_CM_CLIENT" />
</property>
2011/6/27 Sven Zethelius <sv...@expedia.com>
> Sorry, I didn't look at the stack trace close enough. That is during a
> send, in the camel RedeliveryErrorHandler, so disregard my previous
> statement. To handle it, you'd need to replace the RedeliveryErrorHandler
> with one that will catch exceptions (e.g. wrap that processor)
>
> -----Original Message-----
> From: Sven Zethelius
> Sent: Monday, June 27, 2011 8:13 AM
> To: users@camel.apache.org
> Subject: RE: Unable to catch exception from Camel.
>
> Actually you won't be able to catch the exception, since this is caught and
> handled in Spring-JMS AbstractPollingMessageListenerContainer. It's not
> retry, so much as just constantly polling the destination regardless of
> success or failure. You may be able to install an ErrorHandler, although I
> haven't found a good way yet since Camel creates the
> MessageListenerContainer for you.
>
> -----Original Message-----
> From: Ashwin Karpe [mailto:aka...@fusesource.com]
> Sent: Monday, June 27, 2011 7:54 AM
> To: users@camel.apache.org
> Subject: Re: Unable to catch exception from Camel.
>
> Hi,
>
> Looks like your route is not getting established and the exceptionListener
> is not kicking in since the idea is to catch JMS exceptions once the route
> is established/started.
>
> The exception is being thrown while trying to establish the Connection to a
> given queue, prior to the route being started. You will need to catch the
> exception in your main since the exceptionListener is activated upon route
> startup...
>
> Cheers,
>
> Ashwin...
>
> -----
> ---------------------------------------------------------
> Ashwin Karpe
> Apache Camel Committer & Sr Principal Consultant
> FUSESource (a Progress Software Corporation subsidiary)
> http://fusesource.com
>
> Blog: http://opensourceknowledge.blogspot.com
> CamelOne 2011: http://fusesource.com/camel2011
> ---------------------------------------------------------
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Unable-to-catch-exception-from-Camel-tp4528048p4528704.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
--
--
David J. M. Karlsen - http://www.linkedin.com/in/davidkarlsen
