# No logging of runtime exceptions in rivers

**URL:** <https://discuss.elastic.co/t/no-logging-of-runtime-exceptions-in-rivers/4942>\
**Category:** Elasticsearch\
**Created:** [July 25, 2011, 9:49am UTC](https://discuss.elastic.co/t/no-logging-of-runtime-exceptions-in-rivers/4942 "2011-07-25T09:49:52Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alexander\_Reelsen](https://avatars.discourse-cdn.com/v4/letter/a/85e7bf/32.png) [@Alexander\_Reelsen](https://discuss.elastic.co/u/Alexander_Reelsen)\
**Post date:** [July 25, 2011, 9:49am UTC](https://discuss.elastic.co/t/no-logging-of-runtime-exceptions-in-rivers/4942/1 "2011-07-25T09:49:52Z")

</div>

Hi there,

We just hit a stupid problem on our elasticsearch installation with  
our self written river.

The river is quite similar to the couchdb one, connecting to a host  
and getting some data  
I am rereading the configuration on every call of the slurper thread,  
as it can be disabled at runtime or the interval to query the host  
should be changed, someone possibly might misconfigure it, resulting  
in some exception, for example a NumberFormatException.

However runtime exceptions in rivers seem not to be caught in any way,  
resulting in dying of the thread without any notice. Is this intended?

Apart from that the river functionality is dead cool, importing data  
until it can be found is now a matter of seconds in our platform.

Regards, Alexander

---

<div class="post-metadata">

**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:** [July 25, 2011, 11:37am UTC](https://discuss.elastic.co/t/no-logging-of-runtime-exceptions-in-rivers/4942/2 "2011-07-25T11:37:29Z")

</div>

Where was this failure propagated to? If its thrown from a thread you  
created, there is nothing elasticsearch can do about it...

On Mon, Jul 25, 2011 at 12:49 PM, Alexander Reelsen \<  
[alexander.reelsen@googlemail.com](mailto:alexander.reelsen@googlemail.com)\> wrote:

> Hi there,
> 
> We just hit a stupid problem on our elasticsearch installation with  
> our self written river.
> 
> The river is quite similar to the couchdb one, connecting to a host  
> and getting some data  
> I am rereading the configuration on every call of the slurper thread,  
> as it can be disabled at runtime or the interval to query the host  
> should be changed, someone possibly might misconfigure it, resulting  
> in some exception, for example a NumberFormatException.
> 
> However runtime exceptions in rivers seem not to be caught in any way,  
> resulting in dying of the thread without any notice. Is this intended?
> 
> Apart from that the river functionality is dead cool, importing data  
> until it can be found is now a matter of seconds in our platform.
> 
> Regards, Alexander

---

<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, 3:59am UTC](https://discuss.elastic.co/t/no-logging-of-runtime-exceptions-in-rivers/4942/3 "2017-07-06T03:59:35Z")

</div>

Closed on July 6, 2017, 3:59am UTC