rubyjit.Cabin

:Outputs::IO$$\=\^\^_0ECBA4B605298C45B0B8A6C0E3990F2D99834468.block_0$RUBY$__file__(file:/opt/logstash/logstash.jar!/cabin/outputs/io.rb:54) at rubyjit$Cabin::Outputs::IO$$\=\^\^_0ECBA4B605298C45B0B8A6C0E3990F2D99834468$block_0$RUBY$__file__.call(rubyjit$Cabin::Outputs::IO$$\=\^\^_0ECBA4B605298C45B0B8A6C0E3990F2D99834468$block_0$RUBY$__file__)

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 web10

  • via JIRA by Martin Crespo, 9 months ago
    :Outputs::IO$$\=\^\^_0ECBA4B605298C45B0B8A6C0E3990F2D99834468.block_0$RUBY$__file__(file:/opt/logstash/logstash.jar!/cabin/outputs/io.rb:54) at rubyjit$Cabin::Outputs::IO$$\=\^\^_0ECBA4B605298C45B0B8A6C0E3990F2D99834468$block_0$RUBY$__file__.call(rubyjit$Cabin::Outputs::IO$$\=\^\^_0ECBA4B605298C45B0B8A6C0E3990F2D99834468$block_0$RUBY$__file__)
  • :Outputs::IO$$\=\^\^_a759d2d46347217e5f0d618914b90c91265cea161442407170.block_0$RUBY$__file__(/opt/logstash-2.3.2/vendor/bundle/jruby/1.9/gems/cabin-0.8.1/lib/cabin/outputs/io.rb:52) at rubyjit$Cabin::Outputs::IO
  • Stack trace

    • rubyjit.Cabin: :Outputs::IO$$\=\^\^_0ECBA4B605298C45B0B8A6C0E3990F2D99834468.block_0$RUBY$__file__(file:/opt/logstash/logstash.jar!/cabin/outputs/io.rb:54) at rubyjit$Cabin::Outputs::IO$$\=\^\^_0ECBA4B605298C45B0B8A6C0E3990F2D99834468$block_0$RUBY$__file__.call(rubyjit$Cabin::Outputs::IO$$\=\^\^_0ECBA4B605298C45B0B8A6C0E3990F2D99834468$block_0$RUBY$__file__) at org.jruby.runtime.CompiledBlock19.yield(CompiledBlock19.java:135) at org.jruby.runtime.Block.yield(Block.java:142) at org.jruby.ext.thread.Mutex.synchronize(Mutex.java:149) at org.jruby.ext.thread.Mutex$INVOKER$i$0$0$synchronize.call(Mutex$INVOKER$i$0$0$synchronize.gen) at org.jruby.runtime.callsite.CachingCallSite.callBlock(CachingCallSite.java:143) at org.jruby.runtime.callsite.CachingCallSite.callIter(CachingCallSite.java:154)

    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.