# Updated to logstash 2.2.2 now my plugin crashes

**URL:** <https://discuss.elastic.co/t/updated-to-logstash-2-2-2-now-my-plugin-crashes/42412>\
**Category:** Logstash\
**Created:** [February 22, 2016, 5:19pm UTC](https://discuss.elastic.co/t/updated-to-logstash-2-2-2-now-my-plugin-crashes/42412 "2016-02-22T17:19:55Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![CamJN](https://avatars.discourse-cdn.com/v4/letter/c/5f8ce5/32.png) [@CamJN](https://discuss.elastic.co/u/CamJN)\
**Post date:** [February 22, 2016, 5:19pm UTC](https://discuss.elastic.co/t/updated-to-logstash-2-2-2-now-my-plugin-crashes/42412/1 "2016-02-22T17:19:55Z")

</div>

I have a fork of the influxdb output plugin that was working great untill I updated to logstash 2.2.2, now I get the following error. Unfortunately there's no indication what was being looked up when the NameError got thrown in `const_missing`. And it's thrown in the java code so I can't just add extra logging like I would if it was in ruby.

I suspect it has something to do with my adding https support, as it doesn't happen if I leave it as http. But since it was working up until the latest update I'm just wondering what could be going on?

```
Failed to flush outgoing items {:outgoing_count=>100, :exception=>"NameError", :backtrace=>["org/jruby/RubyModule.java:2745:in `const_missing'", "/usr/local/Cellar/logstash/2.2.2/libexec/vendor/local_gems/2ebdd6fb/logstash-output-influxdb-2.0.2/lib/logstash/outputs/influxdb.rb:188:in `post'", "/usr/local/Cellar/logstash/2.2.2/libexec/vendor/local_gems/2ebdd6fb/logstash-output-influxdb-2.0.2/lib/logstash/outputs/influxdb.rb:181:in `flush'", "/usr/local/Cellar/logstash/2.2.2/libexec/vendor/bundle/jruby/1.9/gems/stud-0.0.22/lib/stud/buffer.rb:219:in `buffer_flush'", "org/jruby/RubyHash.java:1342:in `each'", "/usr/local/Cellar/logstash/2.2.2/libexec/vendor/bundle/jruby/1.9/gems/stud-0.0.22/lib/stud/buffer.rb:216:in `buffer_flush'", "/usr/local/Cellar/logstash/2.2.2/libexec/vendor/bundle/jruby/1.9/gems/stud-0.0.22/lib/stud/buffer.rb:193:in `buffer_flush'", "/usr/local/Cellar/logstash/2.2.2/libexec/vendor/bundle/jruby/1.9/gems/stud-0.0.22/lib/stud/buffer.rb:159:in `buffer_receive'", "/usr/local/Cellar/logstash/2.2.2/libexec/vendor/local_gems/2ebdd6fb/logstash-output-influxdb-2.0.2/lib/logstash/outputs/influxdb.rb:175:in `receive'", "/usr/local/Cellar/logstash/2.2.2/libexec/vendor/bundle/jruby/1.9/gems/logstash-core-2.2.2-java/lib/logstash/outputs/base.rb:83:in `multi_receive'", "org/jruby/RubyArray.java:1613:in `each'", "/usr/local/Cellar/logstash/2.2.2/libexec/vendor/bundle/jruby/1.9/gems/logstash-core-2.2.2-java/lib/logstash/outputs/base.rb:83:in `multi_receive'", "/usr/local/Cellar/logstash/2.2.2/libexec/vendor/bundle/jruby/1.9/gems/logstash-core-2.2.2-java/lib/logstash/output_delegator.rb:119:in `worker_multi_receive'", "/usr/local/Cellar/logstash/2.2.2/libexec/vendor/bundle/jruby/1.9/gems/logstash-core-2.2.2-java/lib/logstash/output_delegator.rb:65:in `multi_receive'", "/usr/local/Cellar/logstash/2.2.2/libexec/vendor/bundle/jruby/1.9/gems/logstash-core-2.2.2-java/lib/logstash/pipeline.rb:290:in `output_batch'", "org/jruby/RubyHash.java:1342:in `each'", "/usr/local/Cellar/logstash/2.2.2/libexec/vendor/bundle/jruby/1.9/gems/logstash-core-2.2.2-java/lib/logstash/pipeline.rb:290:in `output_batch'", "/usr/local/Cellar/logstash/2.2.2/libexec/vendor/bundle/jruby/1.9/gems/logstash-core-2.2.2-java/lib/logstash/pipeline.rb:221:in `worker_loop'", "/usr/local/Cellar/logstash/2.2.2/libexec/vendor/bundle/jruby/1.9/gems/logstash-core-2.2.2-java/lib/logstash/pipeline.rb:190:in `start_workers'"], :level=>:warn}

```

jruby line: [http://rxr.whitequark.org/jruby/source/src/org/jruby/RubyModule.java?v=1.7.23#2745](http://rxr.whitequark.org/jruby/source/src/org/jruby/RubyModule.java?v=1.7.23#2745)  
my code: [https://github.com/CamJN/logstash-output-influxdb/blob/master/lib/logstash/outputs/influxdb.rb#L188](https://github.com/CamJN/logstash-output-influxdb/blob/master/lib/logstash/outputs/influxdb.rb#L188)  
java version `1.8.0_72`  
Java(TM) SE Runtime Environment `build 1.8.0_72-b15`  
Java HotSpot(TM) 64-Bit Server VM `build 25.72-b15, mixed mode`  
plugin built with `/usr/local/Cellar/logstash/2.2.2/libexec/vendor/jruby/bin/gem build logstash-output-influxdb.gemspec`  
plugin installed with `/usr/local/bin/logstash-plugin install logstash-output-influxdb-2.0.2.gem`

---

<div class="post-metadata">

**Author:** ![CamJN](https://avatars.discourse-cdn.com/v4/letter/c/5f8ce5/32.png) [@CamJN](https://discuss.elastic.co/u/CamJN)\
**Post date:** [February 22, 2016, 7:18pm UTC](https://discuss.elastic.co/t/updated-to-logstash-2-2-2-now-my-plugin-crashes/42412/2 "2016-02-22T19:18:14Z")

</div>

Nevermind, forgot to scope ManticoreException to Manticore::. weird that the gem builds with errors like that, and that if you don't hit that code path everything's fine. Oh well, dynamic languages c'est la vie.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 6, 2017, 5:10am UTC](https://discuss.elastic.co/t/updated-to-logstash-2-2-2-now-my-plugin-crashes/42412/3 "2017-07-06T05:10:15Z")

</div>