Hi
Just wanted to note that the bug is now fixed in the next release of
Camel - 1.6.1 and 2.0
Thanks for reporting.
On Tue, Mar 17, 2009 at 9:28 AM, Claus Ibsen claus.ib...@gmail.com wrote:
Hi
A quick test shows:
JMX disabled:
EventDrivenConsumerRoute[Endpoint[direct:start] -
Wow nice job! I'll make sure that I try 1.6.1 soon.
Thanks a lot Claus.
--
View this message in context:
http://www.nabble.com/StreamCaching-in-Camel-1.6-tp22305654p22581500.html
Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.
On Fri, Mar 6, 2009 at 1:46 PM, _Jens jens.riemschnei...@icw.de wrote:
Hi,
first of all, thanks to both of you, Gert and Willem, for the quick replies.
I saw that the jira was already fixed, great job.
Does this mean that the methods for disabling stream caching will be removed
in the
Hi Claus,
yes, it seems to have an effect because the lifecycle-strategy is different
when disabling JMX. The Constructor of the DefaultCamelContext uses either
DefaultLifecycleStrategy or InstrumentationLifecycleStrategy. This also has
influence on the error handling strategy.
Jens
--
View
Jens,
Stream caching is turned on automatically when you use a
DeadLetterChannel as the error handler. Because the Exchange might be
redelivered or sent to the DLQ destination, we have to cache it before
we send it into the DLC. Adding an errorHandler(noErrorHandler()); to
the configure()
Hi
Just as Gert said.
In CXF , we will cache the big message into the File instead of the memory.
I think we could do the same thing in Camel.
I just filled a JIRA[2] for it.
[1] http://www.nabble.com/Re%3A-StreamCaching-in-Camel-1.6-to22305858.html
[2] https://issues.apache.org/activemq
