Mailing-List: contact camel-user-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-user@activemq.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: Camel Exception Handling
Date: Sat, 12 Jul 2008 12:03:56 +0200
Message-ID: <4C1FB9C00D24A140906239533638C4D204BD85D7@EXVS04.exserver.dk>
In-Reply-To: <18417527.post@talk.nabble.com>
Thread-Topic: Camel Exception Handling
Thread-Index: Acjj/g+F3lZsEh63Qgup1OYWfNszOQAB2C8w
From: "Claus Ibsen" <ci@silverbullet.dk>
To: <camel-user@activemq.apache.org>

Hi

I do think the redelivery it's the responsibility of the backing system. =
And in your case it's ActiveMQ 5.1. If you were on WebSphereMQ then you =
had to configure WebSphere how it should handle redeliveries.

So you should configure ActiveMQ how it should handle redeliverings, =
delays, its error queue etc. In fact it also has a redeliveryPolicy tag=20

The stuff in Camel was added as a baseline for further improvements. =
What Camel only can do is to add some additional delays, if for instance =
configuring the backing system is very hard. Then Camel at least will be =
able to do delays.=20


Med venlig hilsen
=20
Claus Ibsen
......................................
Silverbullet
Skovsg=E5rdsv=E6nget 21
8362 H=F8rning
Tlf. +45 2962 7576
Web: www.silverbullet.dk

-----Original Message-----
From: michaellear [mailto:mikelear@condotta.co.uk]=20
Sent: 12. juli 2008 11:04
To: camel-user@activemq.apache.org
Subject: Camel Exception Handling


Hi=20

  I'm still struging with the transaction hadnling in Camel. No matter =
what
I try and can't seem to get any different behaviour than a message =
failing
retrying the default amount of times and then been forwared onto the
activeMQ.DLQ. I've tried most different examples and sugestions from the
forums but it I can't seem to change the behaviour. Below is my XML and =
java
code to show the configuration

<beans xmlns=3D"http://www.springframework.org/schema/beans"
	xmlns:amq=3D"http://activemq.apache.org/schema/core"
	xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance"
	xsi:schemaLocation=3D"http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
  http://activemq.apache.org/schema/core
http://activemq.apache.org/schema/core/activemq-core.xsd  =20
  http://activemq.apache.org/camel/schema/spring
http://activemq.apache.org/camel/schema/spring/camel-spring.xsd">

	<bean id=3D"myProcessor" class=3D"MyProcessor" />

	<camelContext id=3D"camel"
		xmlns=3D"http://activemq.apache.org/camel/schema/spring">
		<package>com.SpringTest</package>
	</camelContext>

	<!-- configuration of the transaction error handler -->
	<bean id=3D"redeliveryPolicyConfig"
		class=3D"org.apache.camel.processor.RedeliveryPolicy">
		<!-- try up till 5 times -->
		<property name=3D"maximumRedeliveries" value=3D"50" />
		<!-- wait 5 seconds at first redelivery -->
		<property name=3D"initialRedeliveryDelay" value=3D"5000" />
		<!-- increas the wait time for each redelivery -->
		<property name=3D"useExponentialBackOff" value=3D"true" />
		<!-- wait at most 30 seconds between redelivery -->
		<property name=3D"maximumRedeliveryDelay" value=3D"30000" />
	</bean>

	<bean id=3D"required"
		class=3D"org.apache.camel.spring.spi.SpringTransactionPolicy">
		<constructor-arg>
			<bean
				=
class=3D"org.springframework.transaction.support.TransactionTemplate">
				<property name=3D"transactionManager"
					ref=3D"jmsTransactionManager" />
				<property name=3D"propagationBehaviorName"
					value=3D"PROPAGATION_REQUIRES_NEW" />
			</bean>
		</constructor-arg>
	</bean>


	<!-- the standard spring transaction template for required -->
	<bean id=3D"jmsTransactionTemplate"
		class=3D"org.springframework.transaction.support.TransactionTemplate">
		<property name=3D"transactionManager" ref=3D"jmsTransactionManager" />
	</bean>

	<!-- the transaction error handle we refer to from the route -->
	<bean id=3D"transactionErrorHandler"
		class=3D"org.apache.camel.spring.spi.TransactionErrorHandlerBuilder">
		<property name=3D"transactionTemplate"
			ref=3D"jmsTransactionTemplate" />
		<!-- here we refer to the configurations of the error handler -->
		<property name=3D"redeliveryPolicy" ref=3D"redeliveryPolicyConfig" />
	</bean>

	<bean id=3D"jmsConnectionFactory"
		class=3D"org.apache.activemq.ActiveMQConnectionFactory">
		<property name=3D"brokerURL" value=3D"tcp://localhost:61616" />
	</bean>

	<bean id=3D"jmsTransactionManager"
		class=3D"org.springframework.jms.connection.JmsTransactionManager">
		<property name=3D"connectionFactory" ref=3D"jmsConnectionFactory" />
	</bean>

	<bean id=3D"jmsConfig"
		class=3D"org.apache.camel.component.jms.JmsConfiguration">
		<property name=3D"connectionFactory" ref=3D"jmsConnectionFactory" />
		<property name=3D"transactionManager" ref=3D"jmsTransactionManager" />
		<property name=3D"transacted" value=3D"true" />
		<property name=3D"concurrentConsumers" value=3D"1" />
	</bean>

	<bean id=3D"activemq"
		class=3D"org.apache.camel.component.jms.JmsComponent">
		<property name=3D"configuration" ref=3D"jmsConfig" />
	</bean>

	<bean id=3D"noErrorHandler"
		class=3D"org.apache.camel.builder.NoErrorHandlerBuilder" />


</bean>

Here is my java code for the RouteBuilder package

configure()

    	errorHandler(loggingErrorHandler());=20
    	exception(Exception.class).to("jms:queue:TestQueue.exception"); =20

    	from("jms:queue:TestQueue")
    	.policy( (SpringTransactionPolicy)ctx.getBean("required"))
    	.process( (Processor)ctx.getBean("myProcessor"));


and here is the java code for MyProcessor which just throws and =
exception

public class MyProcessor implements Processor {


	public void process(Exchange exchange) throws Exception {
		throw new Exception("Forced Exception");
	}
}


As I say no matter what I try and I can't seem to get a different =
behaviour
I can see by the log file that if I change the errorhandler I don't get =
the
call to the DeadLetter classes but it still appears on there. But I can
never get any exception to appear on the exception queue infact the =
queue is
never created.=20

I'm using ActiveMQ 5.1 and the latest SNAPSHOT of Camel. Any help would =
be
greatly appreaciated I've been trying different combinations and looking =
at
the code for this for the last two days with no success.

Thanks

Mike
--=20
View this message in context: =
http://www.nabble.com/Camel-Exception-Handling-tp18417527s22882p18417527.=
html
Sent from the Camel - Users mailing list archive at Nabble.com.