So ideally camel-ruby should set that JVM system property if not already set? so you get the thread safe out of the box?
On Fri, Nov 28, 2014 at 11:04 AM, Christoph Spenler <christoph.spen...@worldline.com> wrote: > I used JRuby 1.7.13 which comes with camel-ruby 2.14.0. > When I override the version with 1.7.16 it works. > > You have to set the "org.jruby.embed.localcontext.scope" system property to > "threadsafe", otherwise it is not guaranteed that the different bodies are > processed by the ruby script. In many cases only one of the bodies sent to > the language endpoint is processed twice. > > Thanks a lot, > Christoph > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/NPE-with-language-ruby-and-concurrentConsumers-tp5759703p5759757.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 hawtio: http://hawt.io/ fabric8: http://fabric8.io/