Hi
I have a situation where I process create and update events for various
business objects, customer for example. The create event may fail when
invoking a remote webservice and then the message goes to a dead_letter
queue. All good so far.
However, all subsequent update events related to the sa
Hi
OK, I see. Of course the fileconsumer may impose an order on consumation.
However, it may very well happen that several files (in the right order)
will become ready for consumation within the same readLockTimeout-period and
these files *could* be processed in one go.
However, it is probably no
Hi
The setting maxMessagesPerPoll is actually respected but the files will only
be processed one by one with a delay matching readLockTimeout. This
behaviour is happening because the method acquireExclusiveReadLock in
FileChangedExclusiveReadLockStrategy effectively calls
Thread.sleep(checkInterva
Hi
Usually the file-endpoint (File2) allows for processing more than one file
per poll by setting the property maxMessagesPerPoll.
However, when also using readLock=changed, then the file-consumer does not
consume more than one file per poll, regardless of the value specified for
maxMessagesPerP
Thanks, I see the fix is schedulded for 2.9.2.
In the meantime I manage by *not* mocking all endpoints and creating the
mock endpoints manually in my tests.
/Henrik
--
View this message in context:
http://camel.465427.n5.nabble.com/Error-using-apache-cxf-w-Camel-2-9-1-tp5560906p5567659.html
Sen
Thanks. JIRA created: https://issues.apache.org/jira/browse/CAMEL-5084
https://issues.apache.org/jira/browse/CAMEL-5084
--
View this message in context:
http://camel.465427.n5.nabble.com/Error-using-apache-cxf-w-Camel-2-9-1-tp5560906p5564943.html
Sent from the Camel - Users mailing list archive
Hi
I have created a small example showing the error:
http://camel.465427.n5.nabble.com/file/n5564327/hefiso-test.zip
hefiso-test.zip
If I change the camel version to 2.9.0 (in the pom.xml), then the test works
as expected... but not with 2.9.1.
The InterceptSendToEndpoint comes from mocking
I only use a mocked endpoint in my test:
The problem still exists if I remove the mocked endpoint and
InterceptSendToEndpoint is still in the StackTrace... I do not know the
origin of InterceptSendToEndpoint in the stacktrace, but perhaps it comes
from using ? However, I really don't know :-/
Hi
When upgrading from Apache Camel 2.9.0 to 2.9.1 I suddently get an error
when using camel-cxf endpoints.
I have defined this endpoint:
and use it in this route:
When running my JUnit tests (extending CamelSpringTestSupport) I get this
exception:
When I debug my test I see that the method
