Hey guys,
Re: https://issues.jboss.org/browse/ISPN-1396
While looking into this, I've discovered that we have been creating
executors in cache level components, where we're calling submit from
@Listener implementations.
For example, BaseStateTransferManagerImpl.ViewChangeListener
On Oct 6, 2011, at 5:48 PM, Mircea Markus wrote:
On 6 Oct 2011, at 15:52, Galder Zamarreño wrote:
On Oct 6, 2011, at 4:04 PM, Mircea Markus wrote:
On 5 Oct 2011, at 16:53, Galder Zamarreño wrote:
Hey guys,
Re: https://issues.jboss.org/browse/ISPN-1396
While looking into
Btw, state transfer and lock break service's executors are based around the
concept of having a single thread running for each of the executors and either
discarding any other requests (i.e. view changes) while there's an executor in
use.
So, how do these carry on functioning the same way when
Galder, I didn't know about @Listener(sync = false), but a separate
executor makes sense for state transfer because I didn't want
concurrent state transfers and I could set it up to automatically
cancels any state transfer task that's waiting in the queue.
For the StaleTransactionCleanup I
On Oct 6, 2011, at 12:26 PM, Dan Berindei wrote:
Galder, I didn't know about @Listener(sync = false),
Now you know :)
but a separate
executor makes sense for state transfer because I didn't want
concurrent state transfers and I could set it up to automatically
cancels any state transfer
Hey guys,
Re: https://issues.jboss.org/browse/ISPN-1396
While looking into this, I've discovered that we have been creating executors
in cache level components, where we're calling submit from @Listener
implementations.
For example, BaseStateTransferManagerImpl.ViewChangeListener submits a
