org.jruby.exceptions.RaiseException

(ConcurrencyError) Detected invalid array contents due to unsynchronized modifications with concurrent users at org.jruby.RubyArray.<<(org/jruby/RubyArray.java:1147) at LogStash::Codecs::Multiline.buffer(file:/opt/logstash/logstash-1.2.2-flatjar.jar!/logstash/codecs/multiline.rb:158) at LogStash::Codecs::Multiline.do_previous(file:/opt/logstash/logstash-1.2.2-flatjar.jar!/logstash/codecs/multiline.rb:179)

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web104

  • via JIRA by A. Huck, 9 months ago
    (ConcurrencyError) Detected invalid array contents due to unsynchronized modifications with concurrent users at org.jruby.RubyArray.<<(org/jruby/RubyArray.java:1147) at LogStash::Codecs::Multiline.buffer(file:/opt/logstash/logstash
  • via GitHub by rachin-fab
    , 7 months ago
    (ConcurrencyError) Detected invalid array contents due to unsynchronized modifications with concurrent users at org.jruby.RubyArray.<<(org/jruby/RubyArray.java:1147) at LogStash::Codecs::Multiline.buffer(file:/opt/logstash
  • (ConcurrencyError) Detected invalid array contents due to unsynchronized modifications with concurrent users at org.jruby.RubyArray.<<(org/jruby/RubyArray.java:1147) at LogStash::Codecs::Multiline.buffer(file:/opt/logstash/logstash.jar
  • Stack trace

    • org.jruby.exceptions.RaiseException: (ConcurrencyError) Detected invalid array contents due to unsynchronized modifications with concurrent users at org.jruby.RubyArray.<<(org/jruby/RubyArray.java:1147) at LogStash::Codecs::Multiline.buffer(file:/opt/logstash/logstash-1.2.2-flatjar.jar!/logstash/codecs/multiline.rb:158) at LogStash::Codecs::Multiline.do_previous(file:/opt/logstash/logstash-1.2.2-flatjar.jar!/logstash/codecs/multiline.rb:179) at org.jruby.RubyMethod.call(org/jruby/RubyMethod.java:132)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    You’re the first here who have seen this exception.