Try and test with latest Camel release.
On Wed, Mar 5, 2014 at 7:02 AM, simafengyun <yifeng....@citi.com> wrote: > Hi, > > Thanks for your quick reponse. > > I used camel 2.10.4. > > Sorry, I didn't introduce my issue in detail. > > Actually, in the route marketDataRoute, it get message from jms queue, and > the jms message will be encapsulated to java object in the jmsProcessor > them the object will be sent to seda queue. > > <camel:route id="marketDataRoute"> > <from ref="marketDataQueue" /> > <to id="ToJmsProcessor" uri="jmsProcessor"/> > <to uri="toMarshal" /> > </camel:route> > > in the route jaxbRoute, it just get the java object from seda queue, then > marshall the data to xml. > > these objects are not shared, they are independent objects. > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/jaxb-non-thread-safe-issue-tp5748274p5748313.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- 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
