Exception when enqeuing instrumentation results crashes the instrumentation reporting

[dgrnbrg]

I have been able to reproduce this issue: after this exception, the riemann internal stats stop reporting.

Exception in thread "Thread-16" java.util.concurrent.RejectedExecutionException: Task clojure.core$bound_fn_STAR_$fn__4110@70678f2c rejected from java.util.concurrent.ThreadPoolExecutor@48b4da9b[Running, pool size = 4, active threads = 4, queued tasks = 10000, completed tasks = 879966]
    at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2013)
    at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:816)
    at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1337)
    at riemann.service.ExecutorServiceService.execute(service.clj:155)
    at riemann.streams$execute_on$stream__8289.invoke(streams.clj:228)
    at riemann.core$stream_BANG_$fn__9856.invoke(core.clj:18)
    at riemann.core$stream_BANG_.invoke(core.clj:17)
    at riemann.core$instrumentation_service$measure__9865.invoke(core.clj:43)
    at riemann.service.ThreadService$thread_service_runner__7794$fn__7795.invoke(service.clj:64)
    at riemann.service.ThreadService$thread_service_runner__7794.invoke(service.clj:63)
    at clojure.lang.AFn.run(AFn.java:24)
    at java.lang.Thread.run(Thread.java:722)

[stanislas]

Hello :)

Is it possible that you encountered this issue with Riemann 0.2.2? The commit 763dee1 seems to solve the problem and was the first commit for the 0.2.3 release. Furthermore, the line information from the stack trace is consistent with the code at the 0.2.2 tag.

[dgrnbrg]

Yes, I believe that's correct. Upgrading fixed the issue. Thanks!

On Friday, April 4, 2014, stanislas [email protected] wrote:

Hello :)

Is it possible that you encountered this issue with Riemann 0.2.2? The
commit 763dee1763dee1d202af8006dfeaafdfb14ebe4723ce7feseems to solve the problem and was the first commit for the 0.2.3 release.
Furthermore, the line information from the stack trace is consistent with
the code at the 0.2.2 https://github.com/aphyr/riemann/tree/0.2.2 tag.

Reply to this email directly or view it on GitHubhttps://github.com//issues/313#issuecomment-39558097
.

[aphyr]

Wonderful; thanks for digging, dgrnbrg & stansislas :)