Hi Are you http payloads big? The Camel stream cache will spool to disk for > 64kb, and when it does that, it will automatic cleanup the disk when the routing is done. I could be that when wire tapping the big streams will just copy the reference to the disk file, and so when the routing is done the disk file is deleted and the wire tap can no longer access the file content.
You can control the threads hold for that. See the streaming caching doc page An alternative is to just convert the payload to a String asap from jetty convertBodyTo(String.class) ... wireTap ... Then there is no problems. On Fri, Apr 27, 2012 at 3:31 AM, mccabejj <[email protected]> wrote: > Thanks Claus. You are correct the messages are stream based, and the > behavior I've noticed seems to fit in precisely with the > http://camel.apache.org/stream-caching.html documentation . > > Per your advice I have tried reconfiguring both the Camel Context and the > individual routes to have streamCache="true" (both the main route and the > WireTap). Unfortunately in both cases the behavior was the same. A varying > % of the transactions end up not logging due to an empty body. A certain % > also end up returning an empty or partial HTTP response to the client. If I > disable "logging" by removing the WireTap everything processes normally. I > have verified this using SOAPUI assertions. Lastly it seems that the > failure % goes up the faster the transactions process. A simple thing like > changing the log level to WARN instead of DEBUG will have an impact. > > I feel like I've got this configured correctly, but there must be something > I'm missing. > > One thing I may try is moving the processor that prepares the message for > logging to the WireTap instead of in the LogRequest route per the > http://camel.apache.org/wire-tap.html documentation (either by using > processorRef or onPrepareRef). I'm not sure if that would make a difference > or not. > > Let me know if there are other suggestions or comments. Thanks all. > > JM > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Http-Route-with-WireTap-Question-Issue-tp5666526p5669042.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- CamelOne 2012 Conference, May 15-16, 2012: http://camelone.com FuseSource Email: [email protected] Web: http://fusesource.com Twitter: davsclaus, fusenews Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
