I made a new test with delaying jms provider system responses by 20s, and
seems that responses are being processed cuncurrently, probably because I
have multiple consumer threads calling direct route:
Case 1: Jms (InOnly, maxConsumers=10) - Split (pool of 10-20 threads) -
Custom
Hello,
I have a problem with concurrently sending messages to InOut jms destination
and processing replies using Camel 2.6.0. I cannot upgrade because of java
1.5. As I undestand, in such case there is only 1 consumer listening for the
replies. I tried using thread dsl, but it didn't help,
Hello,
I'm using Camel with Servicemix (2.7.1.fuse-00-43).
The problem happens when setting synchronous=true - to
uri=cxf:bean:cxfBean / invocation hangs for 60 or more seconds with no
obvious reason. The operation in WSDL is a one-way operation. I have also
tried defining CXF bus, and using URL
Hello,
I'm using Camel with Servicemix (2.7.1.fuse-00-43) with the following route:
The problems is when a system exception is thrown from
CashManagementV01Endpoint, like
org.apache.xml.security.encryption.XMLEncryptionException: Illegal key
size (the full stacktrace is below - the reason is
Our Camel version is camel-core (2.7.1.fuse-00-43). We use Camel with
Servicemix.
I have just tested with valid message, and then invalid, here is the log
(all statements are printed):
2011-12-08 14:38:24,588 | DEBUG | customerpaymentstatusreportv03.MainRouteEE
|
I have just tried to throw an exception explicitly:
* route id=customerpaymentstatusreportv03.MainRouteEE*
from ref=queue_ee /
transacted ref=PROPAGATION_REQUIRED /
setExchangePattern pattern=InOnly /
to
Thank you.
But this unit test is a little different than the original problem, the
exception should be thrown from the foo route before reaching the other
route. Could you please change the unit test and check the output?
--
View this message in context:
Hello,
I have an issue similar to one described at the bottom of
https://issues.apache.org/jira/browse/CAMEL-3277
I'm using Camel 2.7.0 with ServiceMix, and a spring-DSL-based Camel context
with one Java bean.
A route reads messages (requests) from Jetty http endpoint, then a couple of
Xpath
Hello,
We have an issue with Camel JMS component when after receiving a timeout
(org.apache.camel.ExchangeTimedOutException) the exception's getMessage()
always contains the whole Exchange.toString() method's content, which means
it always exposes all sensitive headers that were set before
