# Exception in pipelineworker

**URL:** <https://discuss.elastic.co/t/exception-in-pipelineworker/124369>\
**Category:** Logstash\
**Created:** [March 16, 2018, 9:18pm UTC](https://discuss.elastic.co/t/exception-in-pipelineworker/124369 "2018-03-16T21:18:43Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![franck.lefebure](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/franck.lefebure/32/24332_2.png) [@franck.lefebure](https://discuss.elastic.co/u/franck.lefebure)\
**Post date:** [March 16, 2018, 9:18pm UTC](https://discuss.elastic.co/t/exception-in-pipelineworker/124369/1 "2018-03-16T21:18:43Z")

</div>

Hi,  
I have several times / day this exception on a oracle jdbc input :

`[2018-03-16T03:30:29,368][ERROR][logstash.pipeline] Exception in pipelineworker, the pipeline stopped processing new events, please check your filter configuration and restart Logstash. {"exception"=>"Closed Connection", "backtrace"=>["oracle.jdbc.driver.PhysicalConnection.needLine(oracle/jdbc/driver/PhysicalConnection.java:5389)"...`

For the moment I don't undestand this problem with Oracle, So I trap this exception with a monit script which restarts the logstash process

But It looks like theses restarts make me lose messages.

So I enabled persistent queues in logstash (5.6.4) conf  
But with theses perstistent queue enabled I meet this persistent error :

`[2018-03-16T17:05:02,303][ERROR][logstash.pipeline] Exception in pipelineworker, the pipeline stopped processing new events, please check your filter configuration and restart Logstash. {"exception"=>"comparison of String with LogStash::Timestamp failed", "backtrace"=>["org/jruby/RubyComparable.java:167:in`\<'", "org/jruby/RubyString.java:1889:in `<'", "(eval):23763:in`initialize'", "org/jruby/RubyArray.java:1613:in `each'", "(eval):23761:in`initialize'", "org/jruby/RubyProc.java:281:in `call'", "(eval):23780:in`initialize'", "org/jruby/RubyArray.java:1613:in `each'", "(eval):23775:in`initialize'", "org/jruby/RubyProc.java:281:in `call'", "(eval):23796:in`initialize'", "org/jruby/RubyArray.java:1613:in `each'", "(eval):23791:in`initialize'", "org/jruby/RubyProc.java:281:in `call'", "(eval):23813:in`initialize'", "org/jruby/RubyArray.java:1613:in `each'", "(eval):23808:in`initialize'", "org/jruby/RubyProc.java:281:in `call'", "(eval):3949:in`filter\_func'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:398:in `filter_batch'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:379:in`worker\_loop'", "/usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:342:in `start_workers'"]}`

Its weird, but if i disable persistent queues this error disappears

How can I dig with this issue ?

---

<div class="post-metadata">

**Author:** ![yaauie](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yaauie/32/23363_2.png) [@yaauie](https://discuss.elastic.co/u/yaauie)\
**Post date:** [March 17, 2018, 8:55am UTC](https://discuss.elastic.co/t/exception-in-pipelineworker/124369/2 "2018-03-17T08:55:49Z")

</div>

Reporting the exception as an issue in the project would be the best way to get it tracked down: [https://github.com/elastic/logstash](https://github.com/elastic/logstash)

---

<div class="post-metadata">

**Author:** ![franck.lefebure](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/franck.lefebure/32/24332_2.png) [@franck.lefebure](https://discuss.elastic.co/u/franck.lefebure)\
**Post date:** [March 19, 2018, 4:34pm UTC](https://discuss.elastic.co/t/exception-in-pipelineworker/124369/3 "2018-03-19T16:34:31Z")

</div>

I Found the root error who was in one of the filters

( _if [date] \< [string] { }_ )

It's confusing that the symptom of this mis-configuration appears only when persistent queues are activated.

---

<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:** [April 16, 2018, 4:34pm UTC](https://discuss.elastic.co/t/exception-in-pipelineworker/124369/4 "2018-04-16T16:34:42Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.