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 null. http://camel.apache.org/stream-caching On Thu, Feb 13, 2014 at 9:29 AM, Rural Hunter <ruralhun...@gmail.com> wrote: > 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).to(INDEX_QUEUE); > from(UPDATE_QUEUE).wireTap(INDEX_QUEUE) > .unmarshal().json(JsonLibrary.Gson, IndexDoc.class) > .to(MY_STORE); > from(STORE_QUEUE).unmarshal().json(JsonLibrary.Gson, > IndexDoc.class).to(MY_STORE); > > δΊ 2014/2/13 15:36, Claus Ibsen ει: > >> Hi >> >> Can you post your Camel route? >> >> > -- Claus Ibsen ----------------- Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen Make your Camel applications look hawt, try: http://hawt.io
