Hi,
this is a known issue see
https://issues.apache.org/jira/browse/CAMEL-7055 and is fixed in
2.12.3
Regards Franz
On Thu, Feb 13, 2014 at 5:03 AM, Rural Hunter wrote:
> Hi,
>
> I'm using Camel 2.12.2 and enabled stream caching with this code:
> context.setStreamCaching(true);
>
> Sometimes I
it looks life the stream has been closed and thus destroyed but it was re-used.
For the dev community, I think camel's CachedOutputStream is hard to
use as it targets for a single owner usage compared to cxf's one which
does reference counting for opened connections to support multiple
threads rea
The message is quite big comparing with others not causing problem.
δΊ 2014/2/13 17:00, Claus Ibsen ει:
btw any idea of the size of the message when you hit that NPE? Are the
message big, or small?
Mind the stream cache has a overflow to disk for bigger messages. I
suspect the NPE is when a stre
btw any idea of the size of the message when you hit that NPE? Are the
message big, or small?
Mind the stream cache has a overflow to disk for bigger messages. I
suspect the NPE is when a stream overflows from memory to disk, and
somewhere on the way the temporary file to use for disk overflow is
It's like this:
from(NEW_QUEUE).unmarshal().json(JsonLibrary.Gson, IndexDoc.class)
.process(new Processor1())
.process(new Processor2())
.process(new Processor3())
.process(new Processor4())
.process(new Processor5())
.process(new Processor6()).wireTap(MY_STORE)
.marshal().json(JsonLibrary.Gson).t
Hi
Can you post your Camel route?
On Thu, Feb 13, 2014 at 5:03 AM, Rural Hunter wrote:
> Hi,
>
> I'm using Camel 2.12.2 and enabled stream caching with this code:
> context.setStreamCaching(true);
>
> Sometimes I got NullPointerException related to stream cache:
>
> Stacktrace
>
