# Logstash JMS Input Plugin - Oracle AQ buffered messages support

**URL:** <https://discuss.elastic.co/t/logstash-jms-input-plugin-oracle-aq-buffered-messages-support/164256>\
**Category:** Logstash\
**Created:** [January 15, 2019, 7:47am UTC](https://discuss.elastic.co/t/logstash-jms-input-plugin-oracle-aq-buffered-messages-support/164256 "2019-01-15T07:47:30Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![i-kovalyov](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/i-kovalyov/32/39870_2.png) [@i-kovalyov](https://discuss.elastic.co/u/i-kovalyov)\
**Post date:** [January 15, 2019, 7:47am UTC](https://discuss.elastic.co/t/logstash-jms-input-plugin-oracle-aq-buffered-messages-support/164256/1 "2019-01-15T07:47:30Z")

</div>

Hello.

I want to support Oracle AQ buffered messages in jms input plugin and discuss here implementation details.

What is appropriate way for this enhancement in configuration options?

Maybe vendor\_options (or something similar) with type "hash"?  
For Oracle AQ buffered messages vendor\_options with value {"buffered\_messages"=\>"true"} can be used.

Any other ideas?

---

<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:** [February 12, 2019, 7:47am UTC](https://discuss.elastic.co/t/logstash-jms-input-plugin-oracle-aq-buffered-messages-support/164256/2 "2019-02-12T07:47:39Z")

</div>

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