Changes

• Prevent running into a OutOfMemoryError when Elasticsearch is not available. This could previously happen, because the queue of the thread pool that asynchronously sends request traces to Elasticsearch was unbound. Now it is limited to hold at most 1000 elements. This limit is configurable via the configuration key stagemonitor.threadPools.queueCapacityLimit. See stagemonitor/stagemonitor-mailinglist#16
• A unknown resource path in Resteasy now does not lead to a 500 status code anymore. Instead the expected status 404 is returned. See #101 (thx @johnlcox)