Hi Christoph!
I raised the JIRA https://issues.apache.org/jira/browse/CAMEL-8201 and start
working on it.
I could successfully check, the issue is in Camel and not in JRuby. Add
yourself as watcher on the JIRA to keep you up to date...
Best,
Christian
--
View this message in context:
Yes Claus,
thread safety out of the box would be nice.
We spent last week digging into some massive performance regression with
Camel Ruby and parallel processing:
when processing 200 messages in parallel (5 concurrent consumers)
- memory consumption increased from 30MB (Camel 2.8.0) to 90MB
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
Hi,
after moving from Camel 2.8 to 2.14 I am facing a problem with the language
component and ruby scripts. With concurrentConsumer 1, a NPE is thrown by
the RubyInstanceConfig class:
java.lang.NullPointerException
at org.jruby.RubyInstanceConfig.init(RubyInstanceConfig.java:1432)
Which version of JRuby are you using?
I just ran the test in Camel master (2.15-SNAPSHOT) with JDK8 and JDK7, all
tests are passed.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
It’s look like an issue of JRuby, I reproduced the issue with JRuby 1.7.13, and
the test was passed with JRuby 1.7.16.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
