I recently had a failure in my log-indexing cluster wherein
ElasticSearch ceased reading from its RabbitMQ river, and has been
continually giving RefreshFailedExceptions (showing an
IllegalStateException, caused by an OutOfMemoryError) as the cause.
When in this state, the JVM does not shut itself down properly on
The error itself doesn't bother me nearly so much as not having an
automated means to recover from it; if I could configure RabbitMQ to
always exit in such cases, for instance, the outer process supervision
layer could restart it.