Hi,
I am pretty much inclined to say that the transacted routes the exception
handler doesn't work. I am not sure whether anybody else has checked this
out. Apparently no transacted routes, the handler works fine.
--
View this message in context:
http://camel.465427.n5.nabble.com/Problem-with-
Hi
I've just tested the route following two scenarios and I as far I can see,
the handler works but only when the instruction is removed
from the route.
I wrote down a test bean "testBean" which it throws an exception and I
tested that the route below works and the exceptions are caught. Okay,
okay, you mean the log4j appender I guess. So far what I have is this
log4j.rootLogger=INFO, console, logfile
log4j.logger.org.apache.activemq.spring=WARN
log4j.logger.org.apache.activemq.web.handler=WARN
log4j.logger.org.springframework=WARN
log4j.logger.org.apache.xbean=WARN
log4j.logger.org.apa
Good news Please could you provide more information about the scenarios
you test?. Did you handle java.sql.SQLException?. What kind of environment
did you test it.?. Could you please attach the whole dependency tree running
in your tests for your handlers (Database, Spring, etc...)?
--
Vie
Thank you,
The only thing i can say is that this camel.xml file works on Camel 2.7.0
nicely. All the scenarios work as they meant to be. On camel 2.12.X the
exceptions seem not working, the other scenarios work though and the route
insert data into the database okay
--
View this message in conte
Yes, you are right as far I can see. it's correct that there is a double
exception inside of the telemetryFailureProcessor when the message is not
valid **but** when the message is valid, the exception still comes up!. Even
though the processor is removed from the route, the java.sql.SQLException i
I posted to you both a copy of the whole camel.xml. It's a working copy on
Camel 2.7.0, but for some reason I got the problems described above on Camel
2.12.1.
Please feel free to contact me to get more information
--
View this message in context:
http://camel.465427.n5.nabble.com/Problem-with-
Hi,
I switched and with no luck!. Camel still doesn't
catch any exception. I am tried with java.lang.Exception and
java.sql.SQLException. The funniest part is that it works with older
versions !
--
View this message in context:
http://camel.465427.n5.nabble.com/Problem-with-exception-handle
Hi,
It was just to check on this thread to see whether this is an issue.
Does anybody know a workaround for this problem?, Is this a Camel issue?
Thanks
--
View this message in context:
http://camel.465427.n5.nabble.com/Problem-with-exception-handler-onException-on-Camel-2-12-X-routes-tp57
Thank you for your reply!
I am afraid but it seems not working with even 2.13-SNAPSHOT. I've even
changed the exception to java.lang.Exception and still is not catching these
exceptions.
The exception should be caught when there is no connection to the database.
That's how it works on Camel 2.7.
Hi,
I've just upgraded from Camel 2.7.0 (ActiveMQ 5.5.0) to 2.12.1 (ActiveMQ
5.9.0) and it seems the exception handler is broken in somehow. This DSL
route works nicely on 2.7.0 but it doesn't work on 2.12.X. I also posted the
ActiveMQ 5.9 exception.
I've also noticed that other routes using excep
Awesome!!
thanks for the clues. It works!
Final configuration is something like this:
application/xml
POST
http://server:8080/authservice"/>
Just to post part of the output!
2011-09-08 13:38:26,814 | INFO | Apache Camel 2.7.0 (CamelContext: camel)
started in 0.873 seconds | org.apache.camel.spring.SpringCamelContext | main
2011-09-08 13:38:44,997 | INFO | basic authentication scheme selected |
org.apache.commons.httpclient.auth.AuthC
Hi,
I just wanted to check Camel 2.7 HTTP component to route JMS message payload
to a HTTP service. The configuration below works fine, but the service
requires to be authenticated.
POST
http://server:8080/service"/>
So, I am us
14 matches
Mail list logo
