Hi,
in my project I use 3 routes (each route connects to one SMSC using
camel-smpp).
Problem is that if one SMSC is down, smpp connection cannot be created so
respective route cannot be started and this lead to camel shutdown.
Is there any option how to ignore routes (remove them from context),
Hi,
thank you for your advice. Unfortunately it does not helped (or I am doing
something wrong).
I tried it but with no success.
My current configuration is:
Created CAMEL-3853.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-context-shutdown-after-route-with-smpp-initialization-failure-tp4291032p4295714.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Dear,
I have two applications deployed to tomcat as two separate wars. Application
1 wants to send message to application 2 using VM component. Documentation
says, that camel-core.jar has to be on the system/boot classpath.
I have stored camel-core-2.7.0.jar in $CATALINA_HOME/lib restarted tomcat
Willem Thanks for advise.
Currently my applications are working together. Steps that had to be done
for camel 2.7.0 and tomcat 7.0.6 are:
1. place camel-core, log4j, slf4j-api, slf4j-log4j12 and commons-management
into $CATALINA_HOME/lib
2. remove mentioned jars from both war files
--
View this
Hi,
I am facing the same issue with jsmpp used by camel-smpp. Please, have you
already found solution for this?
As I am looking inside jsmpp, when it fails to connect during reconnect
executorService.shutdown(); is called inside PDUReaderWorker. So threadpool
should be released. But it looks like
