]
Manik Surtani commented on JBCACHE-326:
---------------------------------------
I would have thought the concurrent stack would solve this. Let's push this to 3.0.0
for now and most likely close it once we're closer to finishing with the 2.x.x
series.
Create the concept of a "priority queue" to speed execution
of certain remote method invocations
------------------------------------------------------------------------------------------------
Key: JBCACHE-326
URL:
http://jira.jboss.com/jira/browse/JBCACHE-326
Project: JBoss Cache
Issue Type: Task
Security Level: Public(Everyone can see)
Reporter: Brian Stansberry
Assigned To: Vladimir Blagojevic
Fix For: 3.x
Change the handling of requests in JBossCache (another interceptor on top of
ReplicationInterceptor):
- Create 2 queues (of MethodCall objects), one thread for each queue
- The regular MethodCalls like put(), remove() etc go into the default queue (A), where
they are processed according to order (FIFO)
- The special calls like block(), _getState(), commit() or acks for PREPARE/COMMIT calls
go into the other (priority) queue (B), these calls *CAN* be received out of sequence
- This way, an _getState() would always be processed and would be able to (1) stop the
processing of queue A and (2) force- release any locks held
by on the tree.
_ This way commit() calls can promptly release locks, without having to wait behind other
prepare calls.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: