On Tue, Dec 14, 2010 at 9:50 AM, Raidwan <[email protected]> wrote: > > Hi All, > > Just to inform that i had meet a serious problem with servicemix 3.3.2 and > camel by using the wireTap (by defining route in spring format, not in java) > Messages sent in copy by the wireTap was quietly trunked or transformed and > so un-usable... That was not every time : aleatory. (sorry for my bad > english) > So i finally used the wireTap of servicemix-eip and then every thing gone > right...
You most likely need to convert the payload to a non stream type before sending to the wire tap. (for example String) Or enable stream caching. http://camel.apache.org/stream-caching.html This avoids problems with concurrent access to the stream (from wiretap and from the continued original exchange). Since JBI uses XML with streams, its encouraged to enable stream caching in Camel when using JBI and Camel together. > > Raid > -- > View this message in context: > http://servicemix.396122.n5.nabble.com/Servicemix-3-3-2-servicemix-Camel-2-2-0-wireTap-issue-tp3304240p3304240.html > Sent from the ServiceMix - User mailing list archive at Nabble.com. > -- Claus Ibsen ----------------- FuseSource Email: [email protected] Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.blogspot.com/ Author of Camel in Action: http://www.manning.com/ibsen/
