[infinispan-dev] Why no use async listener executor?
Galder Zamarreño
galder at redhat.com
Fri Oct 7 03:05:08 EDT 2011
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 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 rehash task and TransactionTable.StaleTransactionCleanup submits a tasks to break locks.
>>>>
>>>> Did the people that wrote these listeners (Dan & Mircea respectively) consider defining listeners to be called asynchronously? i.e. @Listener(sync = false)
>>> this can work indeed for BaseStateTransferManagerImpl.ViewChangeListener? This seems like a small change - can you modify that in the scope of ISPN-1396 or do you want me to look into it?
>>
>> BaseStateTransferManagerImpl.ViewChangeListener? Dan seems to disagree. You meant TransactionTable.StaleTransactionCleanup instead?
> yes indeed :-)
Ok. I'll get this changed as part of ISPN-1396.
>
>
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache
More information about the infinispan-dev
mailing list