[JBoss JIRA] Created: (ISPN-922) Flags not being sent along with RpcCommands fail to affect remote InvocationContext
8:24 a.m.
Flags not being sent along with RpcCommands fail to affect remote InvocationContext
-----------------------------------------------------------------------------------
Key: ISPN-922
URL: https://issues.jboss.org/browse/ISPN-922
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency, RPC
Affects Versions: 4.2.0.Final, 4.1.0.Final, 4.0.0.Final
Reporter: Sanne Grinovero
Assignee: Manik Surtani
Fix For: 4.2.1.Final, 5.0.0.ALPHA3
Using the following sequence, using REPL_SYNC:
[thread-A] nodeOne.put(K1, V1);
[thread-B] nodeTwo.startBatch();
[thread-B] nodeTwo.remove(K1);
[thread-A] nodeOne.withFlags(Flag.SKIP_LOCKING).remove(K1);
At the last line, thread-B is blocked waiting to end the batch to
after thread-A finished. This results in thread-A to throw a
"org.infinispan.util.concurrent.TimeoutException: Unable to acquire
lock after [500 milliseconds] on key"
Still if I run the same sequence of operation on two different threads
on the same node, this will work just fine and not throw any error:
[thread-A] nodeOne.put(K1, V1);
[thread-B] nodeOne.startBatch();
[thread-B] nodeOne.remove(K1);
[thread-A] nodeOne.withFlags(Flag.SKIP_LOCKING).remove(K1);
Looking into
org.infinispan.interceptors.ReplicationInterceptor.handleCrudMethod(InvocationContext,
WriteCommand), it seems that any Flag is not sent to remove nodes.
Actually the whole org.infinispan.remoting.rpc.RpcManager interface is
not interested in Flags.
Test being send soon to GitHub.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:46 a.m.
New subject: [JBoss JIRA] Commented: (ISPN-922) Flags not being sent along with RpcCommands fail to affect remote InvocationContext
[
https://issues.jboss.org/browse/ISPN-922?page=com.atlassian.jira.plugin.s...
]
Sanne Grinovero commented on ISPN-922:
--------------------------------------
Tests and some cleanup: https://github.com/Sanne/infinispan/tree/ISPN-922
Flags not being sent along with RpcCommands fail to affect remote
InvocationContext
-----------------------------------------------------------------------------------
Key: ISPN-922
URL: https://issues.jboss.org/browse/ISPN-922
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency, RPC
Affects Versions: 4.0.0.Final, 4.1.0.Final, 4.2.0.Final
Reporter: Sanne Grinovero
Assignee: Manik Surtani
Fix For: 4.2.1.Final, 5.0.0.ALPHA3
Using the following sequence, using REPL_SYNC:
[thread-A] nodeOne.put(K1, V1);
[thread-B] nodeTwo.startBatch();
[thread-B] nodeTwo.remove(K1);
[thread-A] nodeOne.withFlags(Flag.SKIP_LOCKING).remove(K1);
At the last line, thread-B is blocked waiting to end the batch to
after thread-A finished. This results in thread-A to throw a
"org.infinispan.util.concurrent.TimeoutException: Unable to acquire
lock after [500 milliseconds] on key"
Still if I run the same sequence of operation on two different threads
on the same node, this will work just fine and not throw any error:
[thread-A] nodeOne.put(K1, V1);
[thread-B] nodeOne.startBatch();
[thread-B] nodeOne.remove(K1);
[thread-A] nodeOne.withFlags(Flag.SKIP_LOCKING).remove(K1);
Looking into
org.infinispan.interceptors.ReplicationInterceptor.handleCrudMethod(InvocationContext,
WriteCommand), it seems that any Flag is not sent to remove nodes.
Actually the whole org.infinispan.remoting.rpc.RpcManager interface is
not interested in Flags.
Test being send soon to GitHub.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:20 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-922) Flags not being sent along with RpcCommands fail to affect remote InvocationContext
[
https://issues.jboss.org/browse/ISPN-922?page=com.atlassian.jira.plugin.s...
]
Manik Surtani updated ISPN-922:
-------------------------------
Priority: Critical (was: Major)
Flags not being sent along with RpcCommands fail to affect remote
InvocationContext
-----------------------------------------------------------------------------------
Key: ISPN-922
URL: https://issues.jboss.org/browse/ISPN-922
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency, RPC
Affects Versions: 4.0.0.Final, 4.1.0.Final, 4.2.0.Final
Reporter: Sanne Grinovero
Assignee: Manik Surtani
Priority: Critical
Fix For: 4.2.1.Final, 5.0.0.ALPHA3
Using the following sequence, using REPL_SYNC:
[thread-A] nodeOne.put(K1, V1);
[thread-B] nodeTwo.startBatch();
[thread-B] nodeTwo.remove(K1);
[thread-A] nodeOne.withFlags(Flag.SKIP_LOCKING).remove(K1);
At the last line, thread-B is blocked waiting to end the batch to
after thread-A finished. This results in thread-A to throw a
"org.infinispan.util.concurrent.TimeoutException: Unable to acquire
lock after [500 milliseconds] on key"
Still if I run the same sequence of operation on two different threads
on the same node, this will work just fine and not throw any error:
[thread-A] nodeOne.put(K1, V1);
[thread-B] nodeOne.startBatch();
[thread-B] nodeOne.remove(K1);
[thread-A] nodeOne.withFlags(Flag.SKIP_LOCKING).remove(K1);
Looking into
org.infinispan.interceptors.ReplicationInterceptor.handleCrudMethod(InvocationContext,
WriteCommand), it seems that any Flag is not sent to remove nodes.
Actually the whole org.infinispan.remoting.rpc.RpcManager interface is
not interested in Flags.
Test being send soon to GitHub.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:24 a.m.
New subject: [JBoss JIRA] Assigned: (ISPN-922) Flags not being sent along with RpcCommands fail to affect remote InvocationContext
[
https://issues.jboss.org/browse/ISPN-922?page=com.atlassian.jira.plugin.s...
]
Sanne Grinovero reassigned ISPN-922:
------------------------------------
Assignee: Sanne Grinovero (was: Manik Surtani)
Flags not being sent along with RpcCommands fail to affect remote
InvocationContext
-----------------------------------------------------------------------------------
Key: ISPN-922
URL: https://issues.jboss.org/browse/ISPN-922
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency, RPC
Affects Versions: 4.0.0.Final, 4.1.0.Final, 4.2.0.Final
Reporter: Sanne Grinovero
Assignee: Sanne Grinovero
Priority: Critical
Fix For: 4.2.1.Final, 5.0.0.ALPHA3
Using the following sequence, using REPL_SYNC:
[thread-A] nodeOne.put(K1, V1);
[thread-B] nodeTwo.startBatch();
[thread-B] nodeTwo.remove(K1);
[thread-A] nodeOne.withFlags(Flag.SKIP_LOCKING).remove(K1);
At the last line, thread-B is blocked waiting to end the batch to
after thread-A finished. This results in thread-A to throw a
"org.infinispan.util.concurrent.TimeoutException: Unable to acquire
lock after [500 milliseconds] on key"
Still if I run the same sequence of operation on two different threads
on the same node, this will work just fine and not throw any error:
[thread-A] nodeOne.put(K1, V1);
[thread-B] nodeOne.startBatch();
[thread-B] nodeOne.remove(K1);
[thread-A] nodeOne.withFlags(Flag.SKIP_LOCKING).remove(K1);
Looking into
org.infinispan.interceptors.ReplicationInterceptor.handleCrudMethod(InvocationContext,
WriteCommand), it seems that any Flag is not sent to remove nodes.
Actually the whole org.infinispan.remoting.rpc.RpcManager interface is
not interested in Flags.
Test being send soon to GitHub.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:38 a.m.
New subject: [JBoss JIRA] Commented: (ISPN-922) Flags not being sent along with RpcCommands fail to affect remote InvocationContext
[
https://issues.jboss.org/browse/ISPN-922?page=com.atlassian.jira.plugin.s...
]
Sanne Grinovero commented on ISPN-922:
--------------------------------------
I'm adding the Flags as additional parameters of each AbstractDataCommand.
Still the InboundInvocationHandlerImpl and many other places where the Command could be
resumed on the remote node, use a null InvocationContext; basically I'd have to take
care of each place to create a proper context to copy the flags to their intended place
again.
This approach screws up at MultipleRpcCommand, where a single ic is used for multiple
commands being received - so in fact it seems more appropriate for each Command to check
for both context flags, and if the context is null to consider instead it's own
internal flags. breaks many assumptions - ideas?
Flags not being sent along with RpcCommands fail to affect remote
InvocationContext
-----------------------------------------------------------------------------------
Key: ISPN-922
URL: https://issues.jboss.org/browse/ISPN-922
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency, RPC
Affects Versions: 4.0.0.Final, 4.1.0.Final, 4.2.0.Final
Reporter: Sanne Grinovero
Assignee: Sanne Grinovero
Priority: Critical
Fix For: 4.2.1.Final, 5.0.0.ALPHA3
Using the following sequence, using REPL_SYNC:
[thread-A] nodeOne.put(K1, V1);
[thread-B] nodeTwo.startBatch();
[thread-B] nodeTwo.remove(K1);
[thread-A] nodeOne.withFlags(Flag.SKIP_LOCKING).remove(K1);
At the last line, thread-B is blocked waiting to end the batch to
after thread-A finished. This results in thread-A to throw a
"org.infinispan.util.concurrent.TimeoutException: Unable to acquire
lock after [500 milliseconds] on key"
Still if I run the same sequence of operation on two different threads
on the same node, this will work just fine and not throw any error:
[thread-A] nodeOne.put(K1, V1);
[thread-B] nodeOne.startBatch();
[thread-B] nodeOne.remove(K1);
[thread-A] nodeOne.withFlags(Flag.SKIP_LOCKING).remove(K1);
Looking into
org.infinispan.interceptors.ReplicationInterceptor.handleCrudMethod(InvocationContext,
WriteCommand), it seems that any Flag is not sent to remove nodes.
Actually the whole org.infinispan.remoting.rpc.RpcManager interface is
not interested in Flags.
Test being send soon to GitHub.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:52 p.m.
New subject: [JBoss JIRA] Commented: (ISPN-922) Flags not being sent along with RpcCommands fail to affect remote InvocationContext
[
https://issues.jboss.org/browse/ISPN-922?page=com.atlassian.jira.plugin.s...
]
Sanne Grinovero commented on ISPN-922:
--------------------------------------
https://github.com/infinispan/infinispan/pull/164
https://github.com/infinispan/infinispan/pull/163
Flags not being sent along with RpcCommands fail to affect remote
InvocationContext
-----------------------------------------------------------------------------------
Key: ISPN-922
URL: https://issues.jboss.org/browse/ISPN-922
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency, RPC
Affects Versions: 4.0.0.Final, 4.1.0.Final, 4.2.0.Final
Reporter: Sanne Grinovero
Assignee: Sanne Grinovero
Priority: Critical
Fix For: 4.2.1.Final, 5.0.0.ALPHA3
Using the following sequence, using REPL_SYNC:
[thread-A] nodeOne.put(K1, V1);
[thread-B] nodeTwo.startBatch();
[thread-B] nodeTwo.remove(K1);
[thread-A] nodeOne.withFlags(Flag.SKIP_LOCKING).remove(K1);
At the last line, thread-B is blocked waiting to end the batch to
after thread-A finished. This results in thread-A to throw a
"org.infinispan.util.concurrent.TimeoutException: Unable to acquire
lock after [500 milliseconds] on key"
Still if I run the same sequence of operation on two different threads
on the same node, this will work just fine and not throw any error:
[thread-A] nodeOne.put(K1, V1);
[thread-B] nodeOne.startBatch();
[thread-B] nodeOne.remove(K1);
[thread-A] nodeOne.withFlags(Flag.SKIP_LOCKING).remove(K1);
Looking into
org.infinispan.interceptors.ReplicationInterceptor.handleCrudMethod(InvocationContext,
WriteCommand), it seems that any Flag is not sent to remove nodes.
Actually the whole org.infinispan.remoting.rpc.RpcManager interface is
not interested in Flags.
Test being send soon to GitHub.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:26 a.m.
New subject: [JBoss JIRA] Updated: (ISPN-922) Flags not being sent along with RpcCommands fail to affect remote InvocationContext
[
https://issues.jboss.org/browse/ISPN-922?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño updated ISPN-922:
----------------------------------
Fix Version/s: 4.2.1.CR2
5.0.0.Final
Affects Version/s: (was: 4.0.0.Final)
(was: 4.1.0.Final)
Flags not being sent along with RpcCommands fail to affect remote
InvocationContext
-----------------------------------------------------------------------------------
Key: ISPN-922
URL: https://issues.jboss.org/browse/ISPN-922
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency, RPC
Affects Versions: 4.2.0.Final
Reporter: Sanne Grinovero
Assignee: Sanne Grinovero
Priority: Critical
Fix For: 4.2.1.CR2, 4.2.1.Final, 5.0.0.ALPHA3, 5.0.0.Final
Using the following sequence, using REPL_SYNC:
[thread-A] nodeOne.put(K1, V1);
[thread-B] nodeTwo.startBatch();
[thread-B] nodeTwo.remove(K1);
[thread-A] nodeOne.withFlags(Flag.SKIP_LOCKING).remove(K1);
At the last line, thread-B is blocked waiting to end the batch to
after thread-A finished. This results in thread-A to throw a
"org.infinispan.util.concurrent.TimeoutException: Unable to acquire
lock after [500 milliseconds] on key"
Still if I run the same sequence of operation on two different threads
on the same node, this will work just fine and not throw any error:
[thread-A] nodeOne.put(K1, V1);
[thread-B] nodeOne.startBatch();
[thread-B] nodeOne.remove(K1);
[thread-A] nodeOne.withFlags(Flag.SKIP_LOCKING).remove(K1);
Looking into
org.infinispan.interceptors.ReplicationInterceptor.handleCrudMethod(InvocationContext,
WriteCommand), it seems that any Flag is not sent to remove nodes.
Actually the whole org.infinispan.remoting.rpc.RpcManager interface is
not interested in Flags.
Test being send soon to GitHub.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:24 a.m.
New subject: [JBoss JIRA] Resolved: (ISPN-922) Flags not being sent along with RpcCommands fail to affect remote InvocationContext
[
https://issues.jboss.org/browse/ISPN-922?page=com.atlassian.jira.plugin.s...
]
Sanne Grinovero resolved ISPN-922.
----------------------------------
Resolution: Done
Flags not being sent along with RpcCommands fail to affect remote
InvocationContext
-----------------------------------------------------------------------------------
Key: ISPN-922
URL: https://issues.jboss.org/browse/ISPN-922
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency, RPC
Affects Versions: 4.2.0.Final
Reporter: Sanne Grinovero
Assignee: Sanne Grinovero
Priority: Critical
Fix For: 4.2.1.CR2, 4.2.1.Final, 5.0.0.ALPHA3, 5.0.0.Final
Using the following sequence, using REPL_SYNC:
[thread-A] nodeOne.put(K1, V1);
[thread-B] nodeTwo.startBatch();
[thread-B] nodeTwo.remove(K1);
[thread-A] nodeOne.withFlags(Flag.SKIP_LOCKING).remove(K1);
At the last line, thread-B is blocked waiting to end the batch to
after thread-A finished. This results in thread-A to throw a
"org.infinispan.util.concurrent.TimeoutException: Unable to acquire
lock after [500 milliseconds] on key"
Still if I run the same sequence of operation on two different threads
on the same node, this will work just fine and not throw any error:
[thread-A] nodeOne.put(K1, V1);
[thread-B] nodeOne.startBatch();
[thread-B] nodeOne.remove(K1);
[thread-A] nodeOne.withFlags(Flag.SKIP_LOCKING).remove(K1);
Looking into
org.infinispan.interceptors.ReplicationInterceptor.handleCrudMethod(InvocationContext,
WriteCommand), it seems that any Flag is not sent to remove nodes.
Actually the whole org.infinispan.remoting.rpc.RpcManager interface is
not interested in Flags.
Test being send soon to GitHub.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:42 a.m.
New subject: [JBoss JIRA] Reopened: (ISPN-922) Flags not being sent along with RpcCommands fail to affect remote InvocationContext
[
https://issues.jboss.org/browse/ISPN-922?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño reopened ISPN-922:
-----------------------------------
Flags not being sent along with RpcCommands fail to affect remote
InvocationContext
-----------------------------------------------------------------------------------
Key: ISPN-922
URL: https://issues.jboss.org/browse/ISPN-922
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency, RPC
Affects Versions: 4.2.0.Final
Reporter: Sanne Grinovero
Assignee: Sanne Grinovero
Priority: Critical
Fix For: 4.2.1.CR2, 4.2.1.Final, 5.0.0.ALPHA3, 5.0.0.Final
Using the following sequence, using REPL_SYNC:
[thread-A] nodeOne.put(K1, V1);
[thread-B] nodeTwo.startBatch();
[thread-B] nodeTwo.remove(K1);
[thread-A] nodeOne.withFlags(Flag.SKIP_LOCKING).remove(K1);
At the last line, thread-B is blocked waiting to end the batch to
after thread-A finished. This results in thread-A to throw a
"org.infinispan.util.concurrent.TimeoutException: Unable to acquire
lock after [500 milliseconds] on key"
Still if I run the same sequence of operation on two different threads
on the same node, this will work just fine and not throw any error:
[thread-A] nodeOne.put(K1, V1);
[thread-B] nodeOne.startBatch();
[thread-B] nodeOne.remove(K1);
[thread-A] nodeOne.withFlags(Flag.SKIP_LOCKING).remove(K1);
Looking into
org.infinispan.interceptors.ReplicationInterceptor.handleCrudMethod(InvocationContext,
WriteCommand), it seems that any Flag is not sent to remove nodes.
Actually the whole org.infinispan.remoting.rpc.RpcManager interface is
not interested in Flags.
Test being send soon to GitHub.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:44 a.m.
New subject: [JBoss JIRA] Commented: (ISPN-922) Flags not being sent along with RpcCommands fail to affect remote InvocationContext
[
https://issues.jboss.org/browse/ISPN-922?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño commented on ISPN-922:
---------------------------------------
Reopening cos this change breaks Infinispan 4.2.x:
[ERROR]
/Users/z/Go/code/infinispan.git/tree/src/main/java/org/infinispan/tree/TreeContext.java:[76,3]
method does not override or implement a method from a supertype
FlagContainer.isFlagsUninitialized() was removed but org.infinispan.tree.TreeContext has
not been modified accordingly.
Flags not being sent along with RpcCommands fail to affect remote
InvocationContext
-----------------------------------------------------------------------------------
Key: ISPN-922
URL: https://issues.jboss.org/browse/ISPN-922
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency, RPC
Affects Versions: 4.2.0.Final
Reporter: Sanne Grinovero
Assignee: Sanne Grinovero
Priority: Critical
Fix For: 4.2.1.CR2, 4.2.1.Final, 5.0.0.ALPHA3, 5.0.0.Final
Using the following sequence, using REPL_SYNC:
[thread-A] nodeOne.put(K1, V1);
[thread-B] nodeTwo.startBatch();
[thread-B] nodeTwo.remove(K1);
[thread-A] nodeOne.withFlags(Flag.SKIP_LOCKING).remove(K1);
At the last line, thread-B is blocked waiting to end the batch to
after thread-A finished. This results in thread-A to throw a
"org.infinispan.util.concurrent.TimeoutException: Unable to acquire
lock after [500 milliseconds] on key"
Still if I run the same sequence of operation on two different threads
on the same node, this will work just fine and not throw any error:
[thread-A] nodeOne.put(K1, V1);
[thread-B] nodeOne.startBatch();
[thread-B] nodeOne.remove(K1);
[thread-A] nodeOne.withFlags(Flag.SKIP_LOCKING).remove(K1);
Looking into
org.infinispan.interceptors.ReplicationInterceptor.handleCrudMethod(InvocationContext,
WriteCommand), it seems that any Flag is not sent to remove nodes.
Actually the whole org.infinispan.remoting.rpc.RpcManager interface is
not interested in Flags.
Test being send soon to GitHub.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:44 a.m.
New subject: [JBoss JIRA] Commented: (ISPN-922) Flags not being sent along with RpcCommands fail to affect remote InvocationContext
[
https://issues.jboss.org/browse/ISPN-922?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño commented on ISPN-922:
---------------------------------------
Check master as well.
Flags not being sent along with RpcCommands fail to affect remote
InvocationContext
-----------------------------------------------------------------------------------
Key: ISPN-922
URL: https://issues.jboss.org/browse/ISPN-922
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency, RPC
Affects Versions: 4.2.0.Final
Reporter: Sanne Grinovero
Assignee: Sanne Grinovero
Priority: Critical
Fix For: 4.2.1.CR2, 4.2.1.Final, 5.0.0.ALPHA3, 5.0.0.Final
Using the following sequence, using REPL_SYNC:
[thread-A] nodeOne.put(K1, V1);
[thread-B] nodeTwo.startBatch();
[thread-B] nodeTwo.remove(K1);
[thread-A] nodeOne.withFlags(Flag.SKIP_LOCKING).remove(K1);
At the last line, thread-B is blocked waiting to end the batch to
after thread-A finished. This results in thread-A to throw a
"org.infinispan.util.concurrent.TimeoutException: Unable to acquire
lock after [500 milliseconds] on key"
Still if I run the same sequence of operation on two different threads
on the same node, this will work just fine and not throw any error:
[thread-A] nodeOne.put(K1, V1);
[thread-B] nodeOne.startBatch();
[thread-B] nodeOne.remove(K1);
[thread-A] nodeOne.withFlags(Flag.SKIP_LOCKING).remove(K1);
Looking into
org.infinispan.interceptors.ReplicationInterceptor.handleCrudMethod(InvocationContext,
WriteCommand), it seems that any Flag is not sent to remove nodes.
Actually the whole org.infinispan.remoting.rpc.RpcManager interface is
not interested in Flags.
Test being send soon to GitHub.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:13 a.m.
New subject: [JBoss JIRA] Commented: (ISPN-922) Flags not being sent along with RpcCommands fail to affect remote InvocationContext
[
https://issues.jboss.org/browse/ISPN-922?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño commented on ISPN-922:
---------------------------------------
Seems like Mircea fixed it now: https://github.com/infinispan/infinispan/pull/172
Flags not being sent along with RpcCommands fail to affect remote
InvocationContext
-----------------------------------------------------------------------------------
Key: ISPN-922
URL: https://issues.jboss.org/browse/ISPN-922
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency, RPC
Affects Versions: 4.2.0.Final
Reporter: Sanne Grinovero
Assignee: Sanne Grinovero
Priority: Critical
Fix For: 4.2.1.CR2, 4.2.1.Final, 5.0.0.ALPHA3, 5.0.0.Final
Using the following sequence, using REPL_SYNC:
[thread-A] nodeOne.put(K1, V1);
[thread-B] nodeTwo.startBatch();
[thread-B] nodeTwo.remove(K1);
[thread-A] nodeOne.withFlags(Flag.SKIP_LOCKING).remove(K1);
At the last line, thread-B is blocked waiting to end the batch to
after thread-A finished. This results in thread-A to throw a
"org.infinispan.util.concurrent.TimeoutException: Unable to acquire
lock after [500 milliseconds] on key"
Still if I run the same sequence of operation on two different threads
on the same node, this will work just fine and not throw any error:
[thread-A] nodeOne.put(K1, V1);
[thread-B] nodeOne.startBatch();
[thread-B] nodeOne.remove(K1);
[thread-A] nodeOne.withFlags(Flag.SKIP_LOCKING).remove(K1);
Looking into
org.infinispan.interceptors.ReplicationInterceptor.handleCrudMethod(InvocationContext,
WriteCommand), it seems that any Flag is not sent to remove nodes.
Actually the whole org.infinispan.remoting.rpc.RpcManager interface is
not interested in Flags.
Test being send soon to GitHub.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:13 a.m.
New subject: [JBoss JIRA] Resolved: (ISPN-922) Flags not being sent along with RpcCommands fail to affect remote InvocationContext
[
https://issues.jboss.org/browse/ISPN-922?page=com.atlassian.jira.plugin.s...
]
Galder Zamarreño resolved ISPN-922.
-----------------------------------
Resolution: Done
Flags not being sent along with RpcCommands fail to affect remote
InvocationContext
-----------------------------------------------------------------------------------
Key: ISPN-922
URL: https://issues.jboss.org/browse/ISPN-922
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency, RPC
Affects Versions: 4.2.0.Final
Reporter: Sanne Grinovero
Assignee: Sanne Grinovero
Priority: Critical
Fix For: 4.2.1.CR2, 4.2.1.Final, 5.0.0.ALPHA3, 5.0.0.Final
Using the following sequence, using REPL_SYNC:
[thread-A] nodeOne.put(K1, V1);
[thread-B] nodeTwo.startBatch();
[thread-B] nodeTwo.remove(K1);
[thread-A] nodeOne.withFlags(Flag.SKIP_LOCKING).remove(K1);
At the last line, thread-B is blocked waiting to end the batch to
after thread-A finished. This results in thread-A to throw a
"org.infinispan.util.concurrent.TimeoutException: Unable to acquire
lock after [500 milliseconds] on key"
Still if I run the same sequence of operation on two different threads
on the same node, this will work just fine and not throw any error:
[thread-A] nodeOne.put(K1, V1);
[thread-B] nodeOne.startBatch();
[thread-B] nodeOne.remove(K1);
[thread-A] nodeOne.withFlags(Flag.SKIP_LOCKING).remove(K1);
Looking into
org.infinispan.interceptors.ReplicationInterceptor.handleCrudMethod(InvocationContext,
WriteCommand), it seems that any Flag is not sent to remove nodes.
Actually the whole org.infinispan.remoting.rpc.RpcManager interface is
not interested in Flags.
Test being send soon to GitHub.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5059
days inactive
5066
days old
infinispan-issues@lists.jboss.org
12 comments
3 participants
participants (3)
-
Galder Zamarreño (JIRA) -
Manik Surtani (JIRA)
-
Sanne Grinovero (JIRA)