Re: Incompatibility in wireTap() between 2.9.0 and 2.9.1/2.9.2

2012-05-08 Thread Claus Ibsen
And in your custom thread pool, you need to set the rejection policy you want to use. for example the Abort from the JDK java.util.concurrent.ThreadPoolExecutor.AbortPolicy On Tue, May 8, 2012 at 4:17 PM, Claus Ibsen wrote: > On Tue, May 8, 2012 at 4:15 PM, Thomas Johansen wrote: >> Hi, >> >>

Re: Incompatibility in wireTap() between 2.9.0 and 2.9.1/2.9.2

2012-05-08 Thread Claus Ibsen
On Tue, May 8, 2012 at 4:15 PM, Thomas Johansen wrote: > Hi, > > There's obviously a difference in how the wireTap()-processor handles > exceptions in 2.9.0 and 2.9.1/2.9.2. > In 2.9.0, when the wireTap() encounters a RejectedExecutionException on its > ExecutorService, the exception is swallowed.

Incompatibility in wireTap() between 2.9.0 and 2.9.1/2.9.2

2012-05-08 Thread Thomas Johansen
Hi, There's obviously a difference in how the wireTap()-processor handles exceptions in 2.9.0 and 2.9.1/2.9.2. In 2.9.0, when the wireTap() encounters a RejectedExecutionException on its ExecutorService, the exception is swallowed. In 2.9.1/2.9.2 the exception is propagated to the errorHandler of