# ActiveMQ River? **URL:** \ **Category:** Elasticsearch\ **Created:** [October 14, 2010, 4:12pm UTC](https://discuss.elastic.co/t/activemq-river/3442 "2010-10-14T16:12:39Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Stephen\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephen_2/32/3274_2.png) [@Stephen\_2](https://discuss.elastic.co/u/Stephen_2)\ **Post date:** [October 14, 2010, 4:12pm UTC](https://discuss.elastic.co/t/activemq-river/3442/1 "2010-10-14T16:12:39Z")
Hey guys, My company is interested in implementing ElasticSearch for a fairly large dataset, and things would be much easier if we could publish messages to an ActiveMQ (since we're using Enterprise Java) that ES would listen on. Do folks have an idea of how hard it would be to implement this plugin? We may be willing to provide some development time, but a rough idea of complexity would help our planning process. Thanks a bunch! Stephen Starkey. ---
**Author:** ![kimchy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/kimchy/32/44952_2.png) [@kimchy](https://discuss.elastic.co/u/kimchy)\ **Post date:** [October 14, 2010, 4:33pm UTC](https://discuss.elastic.co/t/activemq-river/3442/2 "2010-10-14T16:33:40Z")
I would suggest having a look at the RabbitMQ river plugin, its pretty simple, and adapting it to ActiveMQ. Once the code is there, we can help with making it an official plugin. On Thu, Oct 14, 2010 at 6:12 PM, Stephen [scstarkey@gmail.com](mailto:scstarkey@gmail.com) wrote: > Hey guys, > > My company is interested in implementing Elasticsearch for a fairly > large dataset, and things would be much easier if we could publish > messages to an ActiveMQ (since we're using Enterprise Java) that ES > would listen on. > > Do folks have an idea of how hard it would be to implement this > plugin? We may be willing to provide some development time, but a > rough idea of complexity would help our planning process. > > Thanks a bunch! > > Stephen Starkey. ---
**Author:** ![Mahendra\_M](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mahendra_m/32/3128_2.png) [@Mahendra\_M](https://discuss.elastic.co/u/Mahendra_M)\ **Post date:** [October 14, 2010, 4:40pm UTC](https://discuss.elastic.co/t/activemq-river/3442/3 "2010-10-14T16:40:14Z")
Hi, My experience with JMS is very limited, so my reply may be fully wrong. Elasticsearch has a RabbitMQ (AMQP) river plugin. JMS is pretty similar to AMQP. So, you can write a new river plugin for JMS by using the RabbitMQ river plugin as a reference. I believe it may not be too tough to do, specially if you are an expert in JMS. A slightly less attractive alternative would be to use an AMQP/JMS bridge in between - [GitHub - imatix/openamq-jms: Java JMS client for OpenAMQ and other AMQP servers](http://github.com/imatix/openamq-jms) (this works with RabbitMQ, but with AMQP spec 0.8.x and not 0.9-1) Regards, Mahendra On Thu, Oct 14, 2010 at 9:42 PM, Stephen [scstarkey@gmail.com](mailto:scstarkey@gmail.com) wrote: > Hey guys, > > My company is interested in implementing Elasticsearch for a fairly > large dataset, and things would be much easier if we could publish > messages to an ActiveMQ (since we're using Enterprise Java) that ES > would listen on. > > Do folks have an idea of how hard it would be to implement this > plugin? We may be willing to provide some development time, but a > rough idea of complexity would help our planning process. > > Thanks a bunch! > > Stephen Starkey. -- Mahendra [http://twitter.com/mahendra](http://twitter.com/mahendra) ---
**Author:** ![Stephen\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephen_2/32/3274_2.png) [@Stephen\_2](https://discuss.elastic.co/u/Stephen_2)\ **Post date:** [October 15, 2010, 5:12pm UTC](https://discuss.elastic.co/t/activemq-river/3442/4 "2010-10-15T17:12:14Z")
Thanks! We'll take a look when we start planning the project. On Oct 14, 11:40 am, Mahendra M [mahendr...@gmail.com](mailto:mahendr...@gmail.com) wrote: > Hi, > > My experience with JMS is very limited, so my reply may be fully wrong. > > Elasticsearch has a RabbitMQ (AMQP) river plugin. JMS is pretty > similar to AMQP. So, you can write a new river plugin for JMS by using > the RabbitMQ river plugin as a reference. I believe it may not be too > tough to do, specially if you are an expert in JMS. > > A slightly less attractive alternative would be to use an AMQP/JMS > bridge in between -[GitHub - imatix/openamq-jms: Java JMS client for OpenAMQ and other AMQP servers](http://github.com/imatix/openamq-jms)(this works > with RabbitMQ, but with AMQP spec 0.8.x and not 0.9-1) > > Regards, > Mahendra > > On Thu, Oct 14, 2010 at 9:42 PM, Stephen [scstar...@gmail.com](mailto:scstar...@gmail.com) wrote: > > > Hey guys, > > > My company is interested in implementing Elasticsearch for a fairly > > large dataset, and things would be much easier if we could publish > > messages to an ActiveMQ (since we're using Enterprise Java) that ES > > would listen on. > > > Do folks have an idea of how hard it would be to implement this > > plugin? We may be willing to provide some development time, but a > > rough idea of complexity would help our planning process. > > > Thanks a bunch! > > > Stephen Starkey. > > -- > Mahendra > > [http://twitter.com/mahendra](http://twitter.com/mahendra) ---
**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, 4:17am UTC](https://discuss.elastic.co/t/activemq-river/3442/5 "2017-07-06T04:17:59Z")