# ActiveMQ River Configuration

**URL:** <https://discuss.elastic.co/t/activemq-river-configuration/11587>\
**Category:** Elasticsearch\
**Created:** [April 15, 2013, 1:53pm UTC](https://discuss.elastic.co/t/activemq-river-configuration/11587 "2013-04-15T13:53:03Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Ashraf\_Sarhan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ashraf_sarhan/32/2360_2.png) [@Ashraf\_Sarhan](https://discuss.elastic.co/u/Ashraf_Sarhan)\
**Post date:** [April 15, 2013, 1:53pm UTC](https://discuss.elastic.co/t/activemq-river-configuration/11587/1 "2013-04-15T13:53:03Z")

</div>

I start to configure an ActiveMQ river, i'm already installed the ActiveMQ  
plugin but i feel confused about how to make it working, the documentation  
was so brief, Actually, i follow exactly the steps of creating a new river  
but i don't know what are the following steps to follow?

Note:

1- I have the an ActiveMQ server up and running and i tested it using a  
simple JMS app to push a message into a queue.

2- I created a new river using:

curl -XPUT 'localhost:9200/my\_index/myindex\_river/\_meta' -d '{ "type" : "activemq", "activemq" : { "user" : "guest", "pass" : "guest", "brokerUrl" : "failover://tcp://localhost:61616", "sourceType" : "queue", "sourceName" : "elasticsearch", "consumerName" : "activemq\_elasticsearch\_river\_myindex\_river", "durable" : false, "filter" : "" }, "index" : { "bulk\_size" : 100, "bulk\_timeout" : "10ms" } }'

3- After creating the previous river, i could not get it's status using (curl -XGET 'localhost:9200/my\_index/\_status'), it give me the index status, not the created river.

4- I could not delete it using (curl -XDELETE 'localhost:9200/\_river/myindex\_river')

Please, any help to get me the right road with ActiveMQ river configuration with the elasticsearch.

Thanks,  
Ashraf Sarhan

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [April 15, 2013, 2:36pm UTC](https://discuss.elastic.co/t/activemq-river-configuration/11587/2 "2013-04-15T14:36:57Z")

</div>

You need to create the river in \_river "index". Not in "my\_index".

--  
David 😉  
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 15 avr. 2013 à 15:53, Ashraf Sarhan [ashraf.sarhan@silicon-nile.com](mailto:ashraf.sarhan@silicon-nile.com) a écrit :

> I start to configure an ActiveMQ river, i'm already installed the ActiveMQ plugin but i feel confused about how to make it working, the documentation was so brief, Actually, i follow exactly the steps of creating a new river but i don't know what are the following steps to follow?
> 
> Note:
> 
> 1- I have the an ActiveMQ server up and running and i tested it using a simple JMS app to push a message into a queue.
> 
> 2- I created a new river using:  
> curl -XPUT 'localhost:9200/my\_index/myindex\_river/\_meta' -d '{  
> "type" : "activemq",  
> "activemq" : {  
> "user" : "guest",  
> "pass" : "guest",  
> "brokerUrl" : "failover://tcp://localhost:61616",  
> "sourceType" : "queue",  
> "sourceName" : "elasticsearch",  
> "consumerName" : "activemq\_elasticsearch\_river\_myindex\_river",  
> "durable" : false,  
> "filter" : ""  
> },  
> "index" : {  
> "bulk\_size" : 100,  
> "bulk\_timeout" : "10ms"  
> }  
> }'
> 
> 3- After creating the previous river, i could not get it's status using (curl -XGET 'localhost:9200/my\_index/\_status'), it give me the index status, not the created river.
> 
> 4- I could not delete it using (curl -XDELETE 'localhost:9200/\_river/myindex\_river')
> 
> Please, any help to get me the right road with ActiveMQ river configuration with the elasticsearch.
> 
> Thanks,  
> Ashraf Sarhan
> 
> --  
> You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Ashraf\_Sarhan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ashraf_sarhan/32/2360_2.png) [@Ashraf\_Sarhan](https://discuss.elastic.co/u/Ashraf_Sarhan)\
**Post date:** [April 15, 2013, 3:01pm UTC](https://discuss.elastic.co/t/activemq-river-configuration/11587/3 "2013-04-15T15:01:38Z")

</div>

Hello, David

Firstly, thanks for your response. 🙂

Actually, I'm just created a river in the \_river index but actually, i  
could not figure out what i can do after that? Also, Why i could not create  
a river in another index ?

Thanks,  
Ashraf Sarhan

On Monday, April 15, 2013 4:36:57 PM UTC+2, David Pilato wrote:

> You need to create the river in \_river "index". Not in "my\_index".
> 
> --  
> David 😉  
> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> 
> Le 15 avr. 2013 à 15:53, Ashraf Sarhan \<[ashraf...@silicon-nile.com](mailto:ashraf...@silicon-nile.com)\<javascript:\>\>  
> a écrit :
> 
> I start to configure an ActiveMQ river, i'm already installed the ActiveMQ  
> plugin but i feel confused about how to make it working, the documentation  
> was so brief, Actually, i follow exactly the steps of creating a new river  
> but i don't know what are the following steps to follow?
> 
> Note:
> 
> 1- I have the an ActiveMQ server up and running and i tested it using a  
> simple JMS app to push a message into a queue.
> 
> 2- I created a new river using:
> 
> curl -XPUT 'localhost:9200/my\_index/myindex\_river/\_meta' -d '{ "type" : "activemq", "activemq" : { "user" : "guest", "pass" : "guest", "brokerUrl" : "failover://tcp://localhost:61616", "sourceType" : "queue", "sourceName" : "elasticsearch", "consumerName" : "activemq\_elasticsearch\_river\_myindex\_river", "durable" : false, "filter" : "" }, "index" : { "bulk\_size" : 100, "bulk\_timeout" : "10ms" } }'
> 
> 3- After creating the previous river, i could not get it's status using (curl -XGET 'localhost:9200/my\_index/\_status'), it give me the index status, not the created river.
> 
> 4- I could not delete it using (curl -XDELETE 'localhost:9200/\_river/myindex\_river')
> 
> Please, any help to get me the right road with ActiveMQ river configuration with the elasticsearch.
> 
> Thanks,  
> Ashraf Sarhan
> 
> --  
> You received this message because you are subscribed to the Google Groups  
> "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an  
> email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \<javascript:\>.  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [April 15, 2013, 4:02pm UTC](https://discuss.elastic.co/t/activemq-river-configuration/11587/4 "2013-04-15T16:02:50Z")

</div>

You must create rivers in \_river index.  
But, you can ask for rivers to send docs in whatever index you want (default to rivername).

It's not documented for this river.  
See [GitHub - dadoonet/fscrawler: Elasticsearch File System Crawler (FS Crawler)](https://github.com/dadoonet/fsriver)  
$ curl -XPUT 'localhost:9200/\_river/mynewriver/\_meta' -d '{ "type": "fs", "fs": { "name": "My tmp2 dir", "url": "/tmp2", "update\_rate": 3600000, "includes": ["_.doc" , "_.xls", "\*.pdf"] }, "index": { "index": "mydocs", "type": "doc", "bulk\_size": 50 } }'  
Look at index.index and index.type

## HTH

David 😉  
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 15 avr. 2013 à 17:01, Ashraf Sarhan [ashraf.sarhan@silicon-nile.com](mailto:ashraf.sarhan@silicon-nile.com) a écrit :

> Hello, David
> 
> Firstly, thanks for your response. 🙂
> 
> Actually, I'm just created a river in the \_river index but actually, i could not figure out what i can do after that? Also, Why i could not create a river in another index ?
> 
> Thanks,  
> Ashraf Sarhan
> 
> On Monday, April 15, 2013 4:36:57 PM UTC+2, David Pilato wrote:
> 
> > You need to create the river in \_river "index". Not in "my\_index".
> > 
> > --  
> > David 😉  
> > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> > 
> > Le 15 avr. 2013 à 15:53, Ashraf Sarhan [ashraf...@silicon-nile.com](mailto:ashraf...@silicon-nile.com) a écrit :
> > 
> > > I start to configure an ActiveMQ river, i'm already installed the ActiveMQ plugin but i feel confused about how to make it working, the documentation was so brief, Actually, i follow exactly the steps of creating a new river but i don't know what are the following steps to follow?
> > > 
> > > Note:
> > > 
> > > 1- I have the an ActiveMQ server up and running and i tested it using a simple JMS app to push a message into a queue.
> > > 
> > > 2- I created a new river using:  
> > > curl -XPUT 'localhost:9200/my\_index/myindex\_river/\_meta' -d '{  
> > > "type" : "activemq",  
> > > "activemq" : {  
> > > "user" : "guest",  
> > > "pass" : "guest",  
> > > "brokerUrl" : "failover://tcp://localhost:61616",  
> > > "sourceType" : "queue",  
> > > "sourceName" : "elasticsearch",  
> > > "consumerName" : "activemq\_elasticsearch\_river\_myindex\_river",  
> > > "durable" : false,  
> > > "filter" : ""  
> > > },  
> > > "index" : {  
> > > "bulk\_size" : 100,  
> > > "bulk\_timeout" : "10ms"  
> > > }  
> > > }'
> > > 
> > > 3- After creating the previous river, i could not get it's status using (curl -XGET 'localhost:9200/my\_index/\_status'), it give me the index status, not the created river.
> > > 
> > > 4- I could not delete it using (curl -XDELETE 'localhost:9200/\_river/myindex\_river')
> > > 
> > > Please, any help to get me the right road with ActiveMQ river configuration with the elasticsearch.
> > > 
> > > Thanks,  
> > > Ashraf Sarhan
> > > 
> > > --  
> > > You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
> > > To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com).  
> > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).  
> > > --  
> > > You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
> > > To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Ashraf\_Sarhan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ashraf_sarhan/32/2360_2.png) [@Ashraf\_Sarhan](https://discuss.elastic.co/u/Ashraf_Sarhan)\
**Post date:** [April 15, 2013, 4:26pm UTC](https://discuss.elastic.co/t/activemq-river-configuration/11587/5 "2013-04-15T16:26:23Z")

</div>

Actually, I'm not using a file system data for ES but my data is coming  
from the Nutch crawler so i planned to use the ActiveMQ to send the data  
from nutch to the ES, i found the ActiveMQ ES plugin to achieve that. While  
i'm going with it, i stopped, trying to get the ActiveMQ plugin work. I'm  
just need any guide to get that plugin work.

So, Do you think that there is any other solution for my case, David ?

Thanks,  
Ashraf Sarhan

On Monday, April 15, 2013 6:02:50 PM UTC+2, David Pilato wrote:

> You must create rivers in \_river index.  
> But, you can ask for rivers to send docs in whatever index you want  
> (default to rivername).
> 
> It's not documented for this river.  
> See [GitHub - dadoonet/fscrawler: Elasticsearch File System Crawler (FS Crawler)](https://github.com/dadoonet/fsriver)
> 
> $ curl -XPUT 'localhost:9200/\_river/mynewriver/\_meta' -d '{ "type": "fs", "fs": { "name": "My tmp2 dir", "url": "/tmp2", "update\_rate": 3600000, "includes": ["_.doc" , "_.xls", "\*.pdf"] }, "index": { "index": "mydocs", "type": "doc", "bulk\_size": 50 }}'
> 
> Look at index.index and index.type
> 
> ## HTH
> 
> David 😉  
> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> 
> Le 15 avr. 2013 à 17:01, Ashraf Sarhan \<[ashraf...@silicon-nile.com](mailto:ashraf...@silicon-nile.com)\<javascript:\>\>  
> a écrit :
> 
> Hello, David
> 
> Firstly, thanks for your response. 🙂
> 
> Actually, I'm just created a river in the \_river index but actually, i  
> could not figure out what i can do after that? Also, Why i could not create  
> a river in another index ?
> 
> Thanks,  
> Ashraf Sarhan
> 
> On Monday, April 15, 2013 4:36:57 PM UTC+2, David Pilato wrote:
> 
> > You need to create the river in \_river "index". Not in "my\_index".
> > 
> > --  
> > David 😉  
> > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> > 
> > Le 15 avr. 2013 à 15:53, Ashraf Sarhan [ashraf...@silicon-nile.com](mailto:ashraf...@silicon-nile.com) a  
> > écrit :
> > 
> > I start to configure an ActiveMQ river, i'm already installed the  
> > ActiveMQ plugin but i feel confused about how to make it working, the  
> > documentation was so brief, Actually, i follow exactly the steps of  
> > creating a new river but i don't know what are the following steps to  
> > follow?
> > 
> > Note:
> > 
> > 1- I have the an ActiveMQ server up and running and i tested it using a  
> > simple JMS app to push a message into a queue.
> > 
> > 2- I created a new river using:
> > 
> > curl -XPUT 'localhost:9200/my\_index/myindex\_river/\_meta' -d '{ "type" : "activemq", "activemq" : { "user" : "guest", "pass" : "guest", "brokerUrl" : "failover://tcp://localhost:61616", "sourceType" : "queue", "sourceName" : "elasticsearch", "consumerName" : "activemq\_elasticsearch\_river\_myindex\_river", "durable" : false, "filter" : "" }, "index" : { "bulk\_size" : 100, "bulk\_timeout" : "10ms" } }'
> > 
> > 3- After creating the previous river, i could not get it's status using (curl -XGET 'localhost:9200/my\_index/\_status'), it give me the index status, not the created river.
> > 
> > 4- I could not delete it using (curl -XDELETE 'localhost:9200/\_river/myindex\_river')
> > 
> > Please, any help to get me the right road with ActiveMQ river configuration with the elasticsearch.
> > 
> > Thanks,  
> > Ashraf Sarhan
> > 
> > --  
> > You received this message because you are subscribed to the Google Groups  
> > "elasticsearch" group.  
> > To unsubscribe from this group and stop receiving emails from it, send an  
> > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com).  
> > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > 
> > --  
> > You received this message because you are subscribed to the Google Groups  
> > "elasticsearch" group.  
> > To unsubscribe from this group and stop receiving emails from it, send an  
> > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \<javascript:\>.  
> > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [April 15, 2013, 6:03pm UTC](https://discuss.elastic.co/t/activemq-river-configuration/11587/6 "2013-04-15T18:03:16Z")

</div>

I know that you are using ActiveMQ and not FS river.  
I was just meaning that you need to define your river under \_river index and set in it:  
index.index: yourindexname  
index.type: yourtype

Just follow the doc: [GitHub - domdorn/elasticsearch-river-activemq: An ActiveMQ River implementation for ElasticSearch](https://github.com/domdorn/elasticsearch-river-activemq/)  
curl -XPUT 'localhost:9200/\_river/name\_of\_your\_river/_meta' -d '{ "type" : "activemq", "activemq" : { "user" : "guest", "pass" : "guest", "brokerUrl" : "failover://tcp://localhost:61616", "sourceType" : "queue", "sourceName" : "elasticsearch", "consumerName" : "activemq\_elasticsearch\_river_" + rivername, "durable" : false, "filter" : "" }, "index" : { "bulk\_size" : 100, "bulk\_timeout" : "10ms" } }'

--  
David 😉  
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs

Le 15 avr. 2013 à 18:26, Ashraf Sarhan [ashraf.sarhan@silicon-nile.com](mailto:ashraf.sarhan@silicon-nile.com) a écrit :

> Actually, I'm not using a file system data for ES but my data is coming from the Nutch crawler so i planned to use the ActiveMQ to send the data from nutch to the ES, i found the ActiveMQ ES plugin to achieve that. While i'm going with it, i stopped, trying to get the ActiveMQ plugin work. I'm just need any guide to get that plugin work.
> 
> So, Do you think that there is any other solution for my case, David ?
> 
> Thanks,  
> Ashraf Sarhan
> 
> On Monday, April 15, 2013 6:02:50 PM UTC+2, David Pilato wrote:
> 
> > You must create rivers in \_river index.  
> > But, you can ask for rivers to send docs in whatever index you want (default to rivername).
> > 
> > It's not documented for this river.  
> > See [GitHub - dadoonet/fscrawler: Elasticsearch File System Crawler (FS Crawler)](https://github.com/dadoonet/fsriver)  
> > $ curl -XPUT 'localhost:9200/\_river/mynewriver/\_meta' -d '{ "type": "fs", "fs": { "name": "My tmp2 dir", "url": "/tmp2", "update\_rate": 3600000, "includes": ["_.doc" , "_.xls", "\*.pdf"] }, "index": { "index": "mydocs", "type": "doc", "bulk\_size": 50 } }'  
> > Look at index.index and index.type
> > 
> > ## HTH
> > 
> > David 😉  
> > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> > 
> > Le 15 avr. 2013 à 17:01, Ashraf Sarhan [ashraf...@silicon-nile.com](mailto:ashraf...@silicon-nile.com) a écrit :
> > 
> > > Hello, David
> > > 
> > > Firstly, thanks for your response. 🙂
> > > 
> > > Actually, I'm just created a river in the \_river index but actually, i could not figure out what i can do after that? Also, Why i could not create a river in another index ?
> > > 
> > > Thanks,  
> > > Ashraf Sarhan
> > > 
> > > On Monday, April 15, 2013 4:36:57 PM UTC+2, David Pilato wrote:
> > > 
> > > > You need to create the river in \_river "index". Not in "my\_index".
> > > > 
> > > > --  
> > > > David 😉  
> > > > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> > > > 
> > > > Le 15 avr. 2013 à 15:53, Ashraf Sarhan [ashraf...@silicon-nile.com](mailto:ashraf...@silicon-nile.com) a écrit :
> > > > 
> > > > > I start to configure an ActiveMQ river, i'm already installed the ActiveMQ plugin but i feel confused about how to make it working, the documentation was so brief, Actually, i follow exactly the steps of creating a new river but i don't know what are the following steps to follow?
> > > > > 
> > > > > Note:
> > > > > 
> > > > > 1- I have the an ActiveMQ server up and running and i tested it using a simple JMS app to push a message into a queue.
> > > > > 
> > > > > 2- I created a new river using:  
> > > > > curl -XPUT 'localhost:9200/my\_index/myindex\_river/\_meta' -d '{  
> > > > > "type" : "activemq",  
> > > > > "activemq" : {  
> > > > > "user" : "guest",  
> > > > > "pass" : "guest",  
> > > > > "brokerUrl" : "failover://tcp://localhost:61616",  
> > > > > "sourceType" : "queue",  
> > > > > "sourceName" : "elasticsearch",  
> > > > > "consumerName" : "activemq\_elasticsearch\_river\_myindex\_river",  
> > > > > "durable" : false,  
> > > > > "filter" : ""  
> > > > > },  
> > > > > "index" : {  
> > > > > "bulk\_size" : 100,  
> > > > > "bulk\_timeout" : "10ms"  
> > > > > }  
> > > > > }'
> > > > > 
> > > > > 3- After creating the previous river, i could not get it's status using (curl -XGET 'localhost:9200/my\_index/\_status'), it give me the index status, not the created river.
> > > > > 
> > > > > 4- I could not delete it using (curl -XDELETE 'localhost:9200/\_river/myindex\_river')
> > > > > 
> > > > > Please, any help to get me the right road with ActiveMQ river configuration with the elasticsearch.
> > > > > 
> > > > > Thanks,  
> > > > > Ashraf Sarhan
> > > > > 
> > > > > --  
> > > > > You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
> > > > > To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com).  
> > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).  
> > > > > --  
> > > > > You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
> > > > > To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com).  
> > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).  
> > > > > --  
> > > > > You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
> > > > > To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![Ashraf\_Sarhan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ashraf_sarhan/32/2360_2.png) [@Ashraf\_Sarhan](https://discuss.elastic.co/u/Ashraf_Sarhan)\
**Post date:** [April 16, 2013, 1:54pm UTC](https://discuss.elastic.co/t/activemq-river-configuration/11587/7 "2013-04-16T13:54:27Z")

</div>

Actually, I do exactly what did you mention but i did not get any result. I  
need more information, please.

On Monday, April 15, 2013 8:03:16 PM UTC+2, David Pilato wrote:

> I know that you are using ActiveMQ and not FS river.  
> I was just meaning that you need to define your river under \_river index  
> and set in it:  
> index.index: yourindexname  
> index.type: yourtype
> 
> Just follow the doc:  
> [GitHub - domdorn/elasticsearch-river-activemq: An ActiveMQ River implementation for ElasticSearch](https://github.com/domdorn/elasticsearch-river-activemq/)
> 
> curl -XPUT 'localhost:9200/\_river/name\_of\_your\_river/_meta' -d '{ "type" : "activemq", "activemq" : { "user" : "guest", "pass" : "guest", "brokerUrl" : "failover://tcp://localhost:61616", "sourceType" : "queue", "sourceName" : "elasticsearch", "consumerName" : "activemq\_elasticsearch\_river_" + rivername, "durable" : false, "filter" : "" }, "index" : { "bulk\_size" : 100, "bulk\_timeout" : "10ms" } }'
> 
> --  
> David 😉  
> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> 
> Le 15 avr. 2013 à 18:26, Ashraf Sarhan \<[ashraf...@silicon-nile.com](mailto:ashraf...@silicon-nile.com)\<javascript:\>\>  
> a écrit :
> 
> Actually, I'm not using a file system data for ES but my data is coming  
> from the Nutch crawler so i planned to use the ActiveMQ to send the data  
> from nutch to the ES, i found the ActiveMQ ES plugin to achieve that. While  
> i'm going with it, i stopped, trying to get the ActiveMQ plugin work. I'm  
> just need any guide to get that plugin work.
> 
> So, Do you think that there is any other solution for my case, David ?
> 
> Thanks,  
> Ashraf Sarhan
> 
> On Monday, April 15, 2013 6:02:50 PM UTC+2, David Pilato wrote:
> 
> > You must create rivers in \_river index.  
> > But, you can ask for rivers to send docs in whatever index you want  
> > (default to rivername).
> > 
> > It's not documented for this river.  
> > See [GitHub - dadoonet/fscrawler: Elasticsearch File System Crawler (FS Crawler)](https://github.com/dadoonet/fsriver)
> > 
> > $ curl -XPUT 'localhost:9200/\_river/mynewriver/\_meta' -d '{ "type": "fs", "fs": { "name": "My tmp2 dir", "url": "/tmp2", "update\_rate": 3600000, "includes": ["_.doc" , "_.xls", "\*.pdf"] }, "index": { "index": "mydocs", "type": "doc", "bulk\_size": 50 }}'
> > 
> > Look at index.index and index.type
> > 
> > ## HTH
> > 
> > David 😉  
> > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> > 
> > Le 15 avr. 2013 à 17:01, Ashraf Sarhan [ashraf...@silicon-nile.com](mailto:ashraf...@silicon-nile.com) a  
> > écrit :
> > 
> > Hello, David
> > 
> > Firstly, thanks for your response. 🙂
> > 
> > Actually, I'm just created a river in the \_river index but actually, i  
> > could not figure out what i can do after that? Also, Why i could not create  
> > a river in another index ?
> > 
> > Thanks,  
> > Ashraf Sarhan
> > 
> > On Monday, April 15, 2013 4:36:57 PM UTC+2, David Pilato wrote:
> > 
> > > You need to create the river in \_river "index". Not in "my\_index".
> > > 
> > > --  
> > > David 😉  
> > > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> > > 
> > > Le 15 avr. 2013 à 15:53, Ashraf Sarhan [ashraf...@silicon-nile.com](mailto:ashraf...@silicon-nile.com) a  
> > > écrit :
> > > 
> > > I start to configure an ActiveMQ river, i'm already installed the  
> > > ActiveMQ plugin but i feel confused about how to make it working, the  
> > > documentation was so brief, Actually, i follow exactly the steps of  
> > > creating a new river but i don't know what are the following steps to  
> > > follow?
> > > 
> > > Note:
> > > 
> > > 1- I have the an ActiveMQ server up and running and i tested it using a  
> > > simple JMS app to push a message into a queue.
> > > 
> > > 2- I created a new river using:
> > > 
> > > curl -XPUT 'localhost:9200/my\_index/myindex\_river/\_meta' -d '{ "type" : "activemq", "activemq" : { "user" : "guest", "pass" : "guest", "brokerUrl" : "failover://tcp://localhost:61616", "sourceType" : "queue", "sourceName" : "elasticsearch", "consumerName" : "activemq\_elasticsearch\_river\_myindex\_river", "durable" : false, "filter" : "" }, "index" : { "bulk\_size" : 100, "bulk\_timeout" : "10ms" } }'
> > > 
> > > 3- After creating the previous river, i could not get it's status using (curl -XGET 'localhost:9200/my\_index/\_status'), it give me the index status, not the created river.
> > > 
> > > 4- I could not delete it using (curl -XDELETE 'localhost:9200/\_river/myindex\_river')
> > > 
> > > Please, any help to get me the right road with ActiveMQ river configuration with the elasticsearch.
> > > 
> > > Thanks,  
> > > Ashraf Sarhan
> > > 
> > > --  
> > > You received this message because you are subscribed to the Google  
> > > Groups "elasticsearch" group.  
> > > To unsubscribe from this group and stop receiving emails from it, send  
> > > an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com).  
> > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > > 
> > > --  
> > > You received this message because you are subscribed to the Google Groups  
> > > "elasticsearch" group.  
> > > To unsubscribe from this group and stop receiving emails from it, send an  
> > > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com).  
> > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > 
> > --  
> > You received this message because you are subscribed to the Google Groups  
> > "elasticsearch" group.  
> > To unsubscribe from this group and stop receiving emails from it, send an  
> > email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com) \<javascript:\>.  
> > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<div class="post-metadata">

**Author:** ![dadoonet](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dadoonet/32/137187_2.png) [@dadoonet](https://discuss.elastic.co/u/dadoonet)\
**Post date:** [April 16, 2013, 5:24pm UTC](https://discuss.elastic.co/t/activemq-river-configuration/11587/8 "2013-04-16T17:24:52Z")

</div>

I answered here: [Elasticsearch ActiveMQ River Configuration - Stack Overflow](http://stackoverflow.com/questions/16039700/elasticsearch-activemq-river-configuration/16043264#16043264)

--  
David Pilato | Technical Advocate | [Elasticsearch.com](http://Elasticsearch.com)  
@dadoonet | @elasticsearchfr | @scrutmydocs

Le 16 avr. 2013 à 15:54, Ashraf Sarhan [ashraf.sarhan@silicon-nile.com](mailto:ashraf.sarhan@silicon-nile.com) a écrit :

> Actually, I do exactly what did you mention but i did not get any result. I need more information, please.
> 
> On Monday, April 15, 2013 8:03:16 PM UTC+2, David Pilato wrote:  
> I know that you are using ActiveMQ and not FS river.  
> I was just meaning that you need to define your river under \_river index and set in it:  
> index.index: yourindexname  
> index.type: yourtype
> 
> Just follow the doc: [GitHub - domdorn/elasticsearch-river-activemq: An ActiveMQ River implementation for ElasticSearch](https://github.com/domdorn/elasticsearch-river-activemq/)  
> curl -XPUT 'localhost:9200/\_river/name\_of\_your\_river/_meta' -d '{ "type" : "activemq", "activemq" : { "user" : "guest", "pass" : "guest", "brokerUrl" : "failover://tcp://localhost:61616", "sourceType" : "queue", "sourceName" : "elasticsearch", "consumerName" : "activemq\_elasticsearch\_river_" + rivername, "durable" : false, "filter" : "" }, "index" : { "bulk\_size" : 100, "bulk\_timeout" : "10ms" } }'
> 
> --  
> David 😉  
> Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> 
> Le 15 avr. 2013 à 18:26, Ashraf Sarhan [ashraf...@silicon-nile.com](mailto:ashraf...@silicon-nile.com) a écrit :
> 
> > Actually, I'm not using a file system data for ES but my data is coming from the Nutch crawler so i planned to use the ActiveMQ to send the data from nutch to the ES, i found the ActiveMQ ES plugin to achieve that. While i'm going with it, i stopped, trying to get the ActiveMQ plugin work. I'm just need any guide to get that plugin work.
> > 
> > So, Do you think that there is any other solution for my case, David ?
> > 
> > Thanks,  
> > Ashraf Sarhan
> > 
> > On Monday, April 15, 2013 6:02:50 PM UTC+2, David Pilato wrote:  
> > You must create rivers in \_river index.  
> > But, you can ask for rivers to send docs in whatever index you want (default to rivername).
> > 
> > It's not documented for this river.  
> > See [GitHub - dadoonet/fscrawler: Elasticsearch File System Crawler (FS Crawler)](https://github.com/dadoonet/fsriver)  
> > $ curl -XPUT 'localhost:9200/\_river/mynewriver/\_meta' -d '{ "type": "fs", "fs": { "name": "My tmp2 dir", "url": "/tmp2", "update\_rate": 3600000, "includes": ["_.doc" , "_.xls", "\*.pdf"] }, "index": { "index": "mydocs", "type": "doc", "bulk\_size": 50 } }'  
> > Look at index.index and index.type
> > 
> > ## HTH
> > 
> > David 😉  
> > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> > 
> > Le 15 avr. 2013 à 17:01, Ashraf Sarhan [ashraf...@silicon-nile.com](mailto:ashraf...@silicon-nile.com) a écrit :
> > 
> > > Hello, David
> > > 
> > > Firstly, thanks for your response. 🙂
> > > 
> > > Actually, I'm just created a river in the \_river index but actually, i could not figure out what i can do after that? Also, Why i could not create a river in another index ?
> > > 
> > > Thanks,  
> > > Ashraf Sarhan
> > > 
> > > On Monday, April 15, 2013 4:36:57 PM UTC+2, David Pilato wrote:  
> > > You need to create the river in \_river "index". Not in "my\_index".
> > > 
> > > --  
> > > David 😉  
> > > Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
> > > 
> > > Le 15 avr. 2013 à 15:53, Ashraf Sarhan [ashraf...@silicon-nile.com](mailto:ashraf...@silicon-nile.com) a écrit :
> > > 
> > > > I start to configure an ActiveMQ river, i'm already installed the ActiveMQ plugin but i feel confused about how to make it working, the documentation was so brief, Actually, i follow exactly the steps of creating a new river but i don't know what are the following steps to follow?
> > > > 
> > > > Note:
> > > > 
> > > > 1- I have the an ActiveMQ server up and running and i tested it using a simple JMS app to push a message into a queue.
> > > > 
> > > > 2- I created a new river using:  
> > > > curl -XPUT 'localhost:9200/my\_index/myindex\_river/\_meta' -d '{  
> > > > "type" : "activemq",  
> > > > "activemq" : {  
> > > > "user" : "guest",  
> > > > "pass" : "guest",  
> > > > "brokerUrl" : "failover://tcp://localhost:61616",  
> > > > "sourceType" : "queue",  
> > > > "sourceName" : "elasticsearch",  
> > > > "consumerName" : "activemq\_elasticsearch\_river\_myindex\_river",  
> > > > "durable" : false,  
> > > > "filter" : ""  
> > > > },  
> > > > "index" : {  
> > > > "bulk\_size" : 100,  
> > > > "bulk\_timeout" : "10ms"  
> > > > }  
> > > > }'
> > > > 
> > > > 3- After creating the previous river, i could not get it's status using (curl -XGET 'localhost:9200/my\_index/\_status'), it give me the index status, not the created river.
> > > > 
> > > > 4- I could not delete it using (curl -XDELETE 'localhost:9200/\_river/myindex\_river')
> > > > 
> > > > Please, any help to get me the right road with ActiveMQ river configuration with the elasticsearch.
> > > > 
> > > > Thanks,  
> > > > Ashraf Sarhan
> > > > 
> > > > --  
> > > > You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
> > > > To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com).  
> > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > > 
> > > --  
> > > You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
> > > To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com).  
> > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> > 
> > --  
> > You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
> > To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearc...@googlegroups.com](mailto:elasticsearc...@googlegroups.com).  
> > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).
> 
> --  
> You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
> To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
> For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out).

---

<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, 2:40am UTC](https://discuss.elastic.co/t/activemq-river-configuration/11587/9 "2017-07-06T02:40:54Z")

</div>


