11:46 a.m.
Carsten Lohmann created ISPN-2469:
-------------------------------------
Summary: lock() producing timeout exceptions after nodes have left
Key: ISPN-2469
URL: https://issues.jboss.org/browse/ISPN-2469
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency
Affects Versions: 5.2.0.Beta3
Reporter: Carsten Lohmann
Assignee: Mircea Markus
Attachments: LockAfterNodesLeftTest.java
I have a replicated cache with locking mode set to PESSIMISTIC on which I use explicit
locking before putting some value.
After nodes have left the cluster, this does not work anymore and I get TimeoutExceptions
like:
{noformat}
2012-11-02 11:14:12,057 ERROR [InvocationContextInterceptor]
(LockAfterNodesLeftTest.Putter-0) ISPN000136: Execution error
org.infinispan.util.concurrent.TimeoutException: Could not acquire lock on key on behalf
of transaction GlobalTransaction:<NodeA-31597>:4:local. Lock is being held by
GlobalTransaction:<NodeA-31597>:4:local
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.newTimeoutException(AbstractTxLockingInterceptor.java:230)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.waitForTransactionsToComplete(AbstractTxLockingInterceptor.java:210)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.lockKeyAndCheckOwnership(AbstractTxLockingInterceptor.java:175)
at
org.infinispan.interceptors.locking.PessimisticLockingInterceptor.visitPutKeyValueCommand(PessimisticLockingInterceptor.java:120)
{noformat}
This can be reproduced with the attached unit test.
(Use NUM_NODES_TO_STOP_FOR_TEST=0 to not stop any nodes - the test succeeds in that case)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:46 a.m.
[
https://issues.jboss.org/browse/ISPN-2469?page=com.atlassian.jira.plugin....
]
Carsten Lohmann updated ISPN-2469:
----------------------------------
Attachment: LockAfterNodesLeftTest.java
lock() producing timeout exceptions after nodes have left
---------------------------------------------------------
Key: ISPN-2469
URL: https://issues.jboss.org/browse/ISPN-2469
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency
Affects Versions: 5.2.0.Beta3
Reporter: Carsten Lohmann
Assignee: Mircea Markus
Attachments: LockAfterNodesLeftTest.java
I have a replicated cache with locking mode set to PESSIMISTIC on which I use explicit
locking before putting some value.
After nodes have left the cluster, this does not work anymore and I get TimeoutExceptions
like:
{noformat}
2012-11-02 11:14:12,057 ERROR [InvocationContextInterceptor]
(LockAfterNodesLeftTest.Putter-0) ISPN000136: Execution error
org.infinispan.util.concurrent.TimeoutException: Could not acquire lock on key on behalf
of transaction GlobalTransaction:<NodeA-31597>:4:local. Lock is being held by
GlobalTransaction:<NodeA-31597>:4:local
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.newTimeoutException(AbstractTxLockingInterceptor.java:230)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.waitForTransactionsToComplete(AbstractTxLockingInterceptor.java:210)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.lockKeyAndCheckOwnership(AbstractTxLockingInterceptor.java:175)
at
org.infinispan.interceptors.locking.PessimisticLockingInterceptor.visitPutKeyValueCommand(PessimisticLockingInterceptor.java:120)
{noformat}
This can be reproduced with the attached unit test.
(Use NUM_NODES_TO_STOP_FOR_TEST=0 to not stop any nodes - the test succeeds in that case)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:24 p.m.
[
https://issues.jboss.org/browse/ISPN-2469?page=com.atlassian.jira.plugin....
]
Carsten Lohmann updated ISPN-2469:
----------------------------------
Component/s: Transactions
lock() producing timeout exceptions after nodes have left
---------------------------------------------------------
Key: ISPN-2469
URL: https://issues.jboss.org/browse/ISPN-2469
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency, Transactions
Affects Versions: 5.2.0.Beta3
Reporter: Carsten Lohmann
Assignee: Mircea Markus
Attachments: LockAfterNodesLeftTest.java
I have a replicated cache with locking mode set to PESSIMISTIC on which I use explicit
locking before putting some value.
After nodes have left the cluster, this does not work anymore and I get TimeoutExceptions
like:
{noformat}
2012-11-02 11:14:12,057 ERROR [InvocationContextInterceptor]
(LockAfterNodesLeftTest.Putter-0) ISPN000136: Execution error
org.infinispan.util.concurrent.TimeoutException: Could not acquire lock on key on behalf
of transaction GlobalTransaction:<NodeA-31597>:4:local. Lock is being held by
GlobalTransaction:<NodeA-31597>:4:local
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.newTimeoutException(AbstractTxLockingInterceptor.java:230)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.waitForTransactionsToComplete(AbstractTxLockingInterceptor.java:210)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.lockKeyAndCheckOwnership(AbstractTxLockingInterceptor.java:175)
at
org.infinispan.interceptors.locking.PessimisticLockingInterceptor.visitPutKeyValueCommand(PessimisticLockingInterceptor.java:120)
{noformat}
This can be reproduced with the attached unit test.
(Use NUM_NODES_TO_STOP_FOR_TEST=0 to not stop any nodes - the test succeeds in that case)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:29 p.m.
[
https://issues.jboss.org/browse/ISPN-2469?page=com.atlassian.jira.plugin....
]
Carsten Lohmann commented on ISPN-2469:
---------------------------------------
My naive impression is that in
{noformat}
AbstractTxLockingInterceptor.waitForTransactionsToComplete()
{noformat}
the transactions loop should skip the transaction that is the same as the one from the
given txContext
(so just adding a
{noformat}
!tx.getGlobalTransaction().equals(txContext.getGlobalTransaction())
{noformat}
to the if condition).
And/Or to review whether "TransactionTable.useStrictTopologyIdComparison" should
be reset to 'true' at some point after a node has left and there are no
transactions left that originated in the old topology.
lock() producing timeout exceptions after nodes have left
---------------------------------------------------------
Key: ISPN-2469
URL: https://issues.jboss.org/browse/ISPN-2469
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency, Transactions
Affects Versions: 5.2.0.Beta3
Reporter: Carsten Lohmann
Assignee: Mircea Markus
Attachments: LockAfterNodesLeftTest.java
I have a replicated cache with locking mode set to PESSIMISTIC on which I use explicit
locking before putting some value.
After nodes have left the cluster, this does not work anymore and I get TimeoutExceptions
like:
{noformat}
2012-11-02 11:14:12,057 ERROR [InvocationContextInterceptor]
(LockAfterNodesLeftTest.Putter-0) ISPN000136: Execution error
org.infinispan.util.concurrent.TimeoutException: Could not acquire lock on key on behalf
of transaction GlobalTransaction:<NodeA-31597>:4:local. Lock is being held by
GlobalTransaction:<NodeA-31597>:4:local
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.newTimeoutException(AbstractTxLockingInterceptor.java:230)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.waitForTransactionsToComplete(AbstractTxLockingInterceptor.java:210)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.lockKeyAndCheckOwnership(AbstractTxLockingInterceptor.java:175)
at
org.infinispan.interceptors.locking.PessimisticLockingInterceptor.visitPutKeyValueCommand(PessimisticLockingInterceptor.java:120)
{noformat}
This can be reproduced with the attached unit test.
(Use NUM_NODES_TO_STOP_FOR_TEST=0 to not stop any nodes - the test succeeds in that case)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:45 a.m.
[
https://issues.jboss.org/browse/ISPN-2469?page=com.atlassian.jira.plugin....
]
Mircea Markus updated ISPN-2469:
--------------------------------
Priority: Critical (was: Major)
lock() producing timeout exceptions after nodes have left
---------------------------------------------------------
Key: ISPN-2469
URL: https://issues.jboss.org/browse/ISPN-2469
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency, Transactions
Affects Versions: 5.2.0.Beta3
Reporter: Carsten Lohmann
Assignee: Mircea Markus
Priority: Critical
Fix For: 5.2.0.CR1
Attachments: LockAfterNodesLeftTest.java
I have a replicated cache with locking mode set to PESSIMISTIC on which I use explicit
locking before putting some value.
After nodes have left the cluster, this does not work anymore and I get TimeoutExceptions
like:
{noformat}
2012-11-02 11:14:12,057 ERROR [InvocationContextInterceptor]
(LockAfterNodesLeftTest.Putter-0) ISPN000136: Execution error
org.infinispan.util.concurrent.TimeoutException: Could not acquire lock on key on behalf
of transaction GlobalTransaction:<NodeA-31597>:4:local. Lock is being held by
GlobalTransaction:<NodeA-31597>:4:local
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.newTimeoutException(AbstractTxLockingInterceptor.java:230)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.waitForTransactionsToComplete(AbstractTxLockingInterceptor.java:210)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.lockKeyAndCheckOwnership(AbstractTxLockingInterceptor.java:175)
at
org.infinispan.interceptors.locking.PessimisticLockingInterceptor.visitPutKeyValueCommand(PessimisticLockingInterceptor.java:120)
{noformat}
This can be reproduced with the attached unit test.
(Use NUM_NODES_TO_STOP_FOR_TEST=0 to not stop any nodes - the test succeeds in that case)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:45 a.m.
[
https://issues.jboss.org/browse/ISPN-2469?page=com.atlassian.jira.plugin....
]
Mircea Markus updated ISPN-2469:
--------------------------------
Fix Version/s: 5.2.0.CR1
lock() producing timeout exceptions after nodes have left
---------------------------------------------------------
Key: ISPN-2469
URL: https://issues.jboss.org/browse/ISPN-2469
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency, Transactions
Affects Versions: 5.2.0.Beta3
Reporter: Carsten Lohmann
Assignee: Mircea Markus
Fix For: 5.2.0.CR1
Attachments: LockAfterNodesLeftTest.java
I have a replicated cache with locking mode set to PESSIMISTIC on which I use explicit
locking before putting some value.
After nodes have left the cluster, this does not work anymore and I get TimeoutExceptions
like:
{noformat}
2012-11-02 11:14:12,057 ERROR [InvocationContextInterceptor]
(LockAfterNodesLeftTest.Putter-0) ISPN000136: Execution error
org.infinispan.util.concurrent.TimeoutException: Could not acquire lock on key on behalf
of transaction GlobalTransaction:<NodeA-31597>:4:local. Lock is being held by
GlobalTransaction:<NodeA-31597>:4:local
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.newTimeoutException(AbstractTxLockingInterceptor.java:230)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.waitForTransactionsToComplete(AbstractTxLockingInterceptor.java:210)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.lockKeyAndCheckOwnership(AbstractTxLockingInterceptor.java:175)
at
org.infinispan.interceptors.locking.PessimisticLockingInterceptor.visitPutKeyValueCommand(PessimisticLockingInterceptor.java:120)
{noformat}
This can be reproduced with the attached unit test.
(Use NUM_NODES_TO_STOP_FOR_TEST=0 to not stop any nodes - the test succeeds in that case)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:47 a.m.
[
https://issues.jboss.org/browse/ISPN-2469?page=com.atlassian.jira.plugin....
]
Mircea Markus updated ISPN-2469:
--------------------------------
Fix Version/s: 5.2.0.Final
lock() producing timeout exceptions after nodes have left
---------------------------------------------------------
Key: ISPN-2469
URL: https://issues.jboss.org/browse/ISPN-2469
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency, Transactions
Affects Versions: 5.2.0.Beta3
Reporter: Carsten Lohmann
Assignee: Mircea Markus
Priority: Critical
Fix For: 5.2.0.CR1, 5.2.0.Final
Attachments: LockAfterNodesLeftTest.java
I have a replicated cache with locking mode set to PESSIMISTIC on which I use explicit
locking before putting some value.
After nodes have left the cluster, this does not work anymore and I get TimeoutExceptions
like:
{noformat}
2012-11-02 11:14:12,057 ERROR [InvocationContextInterceptor]
(LockAfterNodesLeftTest.Putter-0) ISPN000136: Execution error
org.infinispan.util.concurrent.TimeoutException: Could not acquire lock on key on behalf
of transaction GlobalTransaction:<NodeA-31597>:4:local. Lock is being held by
GlobalTransaction:<NodeA-31597>:4:local
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.newTimeoutException(AbstractTxLockingInterceptor.java:230)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.waitForTransactionsToComplete(AbstractTxLockingInterceptor.java:210)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.lockKeyAndCheckOwnership(AbstractTxLockingInterceptor.java:175)
at
org.infinispan.interceptors.locking.PessimisticLockingInterceptor.visitPutKeyValueCommand(PessimisticLockingInterceptor.java:120)
{noformat}
This can be reproduced with the attached unit test.
(Use NUM_NODES_TO_STOP_FOR_TEST=0 to not stop any nodes - the test succeeds in that case)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:13 a.m.
[
https://issues.jboss.org/browse/ISPN-2469?page=com.atlassian.jira.plugin....
]
Adrian Nistor commented on ISPN-2469:
-------------------------------------
Carsten, I believe this issue might be a duplicate of ISPN-2410.
To confirm this, could you please try to add a line TestingUtil.waitForRehashToComplete
(...) right after log.debug("Shutdown done") ?
This ensures the rebalancing caused leavers is complete before any more put commands are
executed and avoids issue 2410.
lock() producing timeout exceptions after nodes have left
---------------------------------------------------------
Key: ISPN-2469
URL: https://issues.jboss.org/browse/ISPN-2469
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency, Transactions
Affects Versions: 5.2.0.Beta3
Reporter: Carsten Lohmann
Assignee: Mircea Markus
Priority: Critical
Fix For: 5.2.0.CR1, 5.2.0.Final
Attachments: LockAfterNodesLeftTest.java
I have a replicated cache with locking mode set to PESSIMISTIC on which I use explicit
locking before putting some value.
After nodes have left the cluster, this does not work anymore and I get TimeoutExceptions
like:
{noformat}
2012-11-02 11:14:12,057 ERROR [InvocationContextInterceptor]
(LockAfterNodesLeftTest.Putter-0) ISPN000136: Execution error
org.infinispan.util.concurrent.TimeoutException: Could not acquire lock on key on behalf
of transaction GlobalTransaction:<NodeA-31597>:4:local. Lock is being held by
GlobalTransaction:<NodeA-31597>:4:local
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.newTimeoutException(AbstractTxLockingInterceptor.java:230)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.waitForTransactionsToComplete(AbstractTxLockingInterceptor.java:210)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.lockKeyAndCheckOwnership(AbstractTxLockingInterceptor.java:175)
at
org.infinispan.interceptors.locking.PessimisticLockingInterceptor.visitPutKeyValueCommand(PessimisticLockingInterceptor.java:120)
{noformat}
This can be reproduced with the attached unit test.
(Use NUM_NODES_TO_STOP_FOR_TEST=0 to not stop any nodes - the test succeeds in that case)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:15 a.m.
[
https://issues.jboss.org/browse/ISPN-2469?page=com.atlassian.jira.plugin....
]
Adrian Nistor edited comment on ISPN-2469 at 11/5/12 5:14 AM:
--------------------------------------------------------------
Carsten, I believe this issue might be a duplicate of ISPN-2410.
To confirm this, could you please try to add a line TestingUtil.waitForRehashToComplete
(...) right after log.debug("Shutdown done") ?
This ensures the rebalancing caused by leavers is completed before any more put commands
are executed and avoids issue 2410.
was (Author: anistor):
Carsten, I believe this issue might be a duplicate of ISPN-2410.
To confirm this, could you please try to add a line TestingUtil.waitForRehashToComplete
(...) right after log.debug("Shutdown done") ?
This ensures the rebalancing caused leavers is complete before any more put commands are
executed and avoids issue 2410.
lock() producing timeout exceptions after nodes have left
---------------------------------------------------------
Key: ISPN-2469
URL: https://issues.jboss.org/browse/ISPN-2469
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency, Transactions
Affects Versions: 5.2.0.Beta3
Reporter: Carsten Lohmann
Assignee: Mircea Markus
Priority: Critical
Fix For: 5.2.0.CR1, 5.2.0.Final
Attachments: LockAfterNodesLeftTest.java
I have a replicated cache with locking mode set to PESSIMISTIC on which I use explicit
locking before putting some value.
After nodes have left the cluster, this does not work anymore and I get TimeoutExceptions
like:
{noformat}
2012-11-02 11:14:12,057 ERROR [InvocationContextInterceptor]
(LockAfterNodesLeftTest.Putter-0) ISPN000136: Execution error
org.infinispan.util.concurrent.TimeoutException: Could not acquire lock on key on behalf
of transaction GlobalTransaction:<NodeA-31597>:4:local. Lock is being held by
GlobalTransaction:<NodeA-31597>:4:local
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.newTimeoutException(AbstractTxLockingInterceptor.java:230)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.waitForTransactionsToComplete(AbstractTxLockingInterceptor.java:210)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.lockKeyAndCheckOwnership(AbstractTxLockingInterceptor.java:175)
at
org.infinispan.interceptors.locking.PessimisticLockingInterceptor.visitPutKeyValueCommand(PessimisticLockingInterceptor.java:120)
{noformat}
This can be reproduced with the attached unit test.
(Use NUM_NODES_TO_STOP_FOR_TEST=0 to not stop any nodes - the test succeeds in that case)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:14 p.m.
[
https://issues.jboss.org/browse/ISPN-2469?page=com.atlassian.jira.plugin....
]
Carsten Lohmann commented on ISPN-2469:
---------------------------------------
Invocation of waitForRehashToComplete() does not help.
I had already tried this and also tried to just wait a bit
(TestingUtil.sleepThread(2000)), to no avail.
lock() producing timeout exceptions after nodes have left
---------------------------------------------------------
Key: ISPN-2469
URL: https://issues.jboss.org/browse/ISPN-2469
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency, Transactions
Affects Versions: 5.2.0.Beta3
Reporter: Carsten Lohmann
Assignee: Mircea Markus
Priority: Critical
Fix For: 5.2.0.CR1, 5.2.0.Final
Attachments: LockAfterNodesLeftTest.java
I have a replicated cache with locking mode set to PESSIMISTIC on which I use explicit
locking before putting some value.
After nodes have left the cluster, this does not work anymore and I get TimeoutExceptions
like:
{noformat}
2012-11-02 11:14:12,057 ERROR [InvocationContextInterceptor]
(LockAfterNodesLeftTest.Putter-0) ISPN000136: Execution error
org.infinispan.util.concurrent.TimeoutException: Could not acquire lock on key on behalf
of transaction GlobalTransaction:<NodeA-31597>:4:local. Lock is being held by
GlobalTransaction:<NodeA-31597>:4:local
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.newTimeoutException(AbstractTxLockingInterceptor.java:230)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.waitForTransactionsToComplete(AbstractTxLockingInterceptor.java:210)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.lockKeyAndCheckOwnership(AbstractTxLockingInterceptor.java:175)
at
org.infinispan.interceptors.locking.PessimisticLockingInterceptor.visitPutKeyValueCommand(PessimisticLockingInterceptor.java:120)
{noformat}
This can be reproduced with the attached unit test.
(Use NUM_NODES_TO_STOP_FOR_TEST=0 to not stop any nodes - the test succeeds in that case)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:41 p.m.
[
https://issues.jboss.org/browse/ISPN-2469?page=com.atlassian.jira.plugin....
]
Mircea Markus updated ISPN-2469:
--------------------------------
Assignee: Adrian Nistor (was: Mircea Markus)
lock() producing timeout exceptions after nodes have left
---------------------------------------------------------
Key: ISPN-2469
URL: https://issues.jboss.org/browse/ISPN-2469
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency, Transactions
Affects Versions: 5.2.0.Beta3
Reporter: Carsten Lohmann
Assignee: Adrian Nistor
Priority: Critical
Fix For: 5.2.0.CR1, 5.2.0.Final
Attachments: LockAfterNodesLeftTest.java
I have a replicated cache with locking mode set to PESSIMISTIC on which I use explicit
locking before putting some value.
After nodes have left the cluster, this does not work anymore and I get TimeoutExceptions
like:
{noformat}
2012-11-02 11:14:12,057 ERROR [InvocationContextInterceptor]
(LockAfterNodesLeftTest.Putter-0) ISPN000136: Execution error
org.infinispan.util.concurrent.TimeoutException: Could not acquire lock on key on behalf
of transaction GlobalTransaction:<NodeA-31597>:4:local. Lock is being held by
GlobalTransaction:<NodeA-31597>:4:local
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.newTimeoutException(AbstractTxLockingInterceptor.java:230)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.waitForTransactionsToComplete(AbstractTxLockingInterceptor.java:210)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.lockKeyAndCheckOwnership(AbstractTxLockingInterceptor.java:175)
at
org.infinispan.interceptors.locking.PessimisticLockingInterceptor.visitPutKeyValueCommand(PessimisticLockingInterceptor.java:120)
{noformat}
This can be reproduced with the attached unit test.
(Use NUM_NODES_TO_STOP_FOR_TEST=0 to not stop any nodes - the test succeeds in that case)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:43 a.m.
[
https://issues.jboss.org/browse/ISPN-2469?page=com.atlassian.jira.plugin....
]
Mircea Markus updated ISPN-2469:
--------------------------------
Fix Version/s: 5.2.0.CR1
(was: 5.2.0.Beta4)
lock() producing timeout exceptions after nodes have left
---------------------------------------------------------
Key: ISPN-2469
URL: https://issues.jboss.org/browse/ISPN-2469
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency, Transactions
Affects Versions: 5.2.0.Beta3
Reporter: Carsten Lohmann
Assignee: Adrian Nistor
Priority: Critical
Fix For: 5.2.0.CR1, 5.2.0.Final
Attachments: LockAfterNodesLeftTest.java
I have a replicated cache with locking mode set to PESSIMISTIC on which I use explicit
locking before putting some value.
After nodes have left the cluster, this does not work anymore and I get TimeoutExceptions
like:
{noformat}
2012-11-02 11:14:12,057 ERROR [InvocationContextInterceptor]
(LockAfterNodesLeftTest.Putter-0) ISPN000136: Execution error
org.infinispan.util.concurrent.TimeoutException: Could not acquire lock on key on behalf
of transaction GlobalTransaction:<NodeA-31597>:4:local. Lock is being held by
GlobalTransaction:<NodeA-31597>:4:local
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.newTimeoutException(AbstractTxLockingInterceptor.java:230)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.waitForTransactionsToComplete(AbstractTxLockingInterceptor.java:210)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.lockKeyAndCheckOwnership(AbstractTxLockingInterceptor.java:175)
at
org.infinispan.interceptors.locking.PessimisticLockingInterceptor.visitPutKeyValueCommand(PessimisticLockingInterceptor.java:120)
{noformat}
This can be reproduced with the attached unit test.
(Use NUM_NODES_TO_STOP_FOR_TEST=0 to not stop any nodes - the test succeeds in that case)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:24 p.m.
[
https://issues.jboss.org/browse/ISPN-2469?page=com.atlassian.jira.plugin....
]
Mircea Markus updated ISPN-2469:
--------------------------------
Priority: Blocker (was: Critical)
lock() producing timeout exceptions after nodes have left
---------------------------------------------------------
Key: ISPN-2469
URL: https://issues.jboss.org/browse/ISPN-2469
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency, Transactions
Affects Versions: 5.2.0.Beta3
Reporter: Carsten Lohmann
Assignee: Adrian Nistor
Priority: Blocker
Fix For: 5.2.0.CR1, 5.2.0.Final
Attachments: LockAfterNodesLeftTest.java
I have a replicated cache with locking mode set to PESSIMISTIC on which I use explicit
locking before putting some value.
After nodes have left the cluster, this does not work anymore and I get TimeoutExceptions
like:
{noformat}
2012-11-02 11:14:12,057 ERROR [InvocationContextInterceptor]
(LockAfterNodesLeftTest.Putter-0) ISPN000136: Execution error
org.infinispan.util.concurrent.TimeoutException: Could not acquire lock on key on behalf
of transaction GlobalTransaction:<NodeA-31597>:4:local. Lock is being held by
GlobalTransaction:<NodeA-31597>:4:local
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.newTimeoutException(AbstractTxLockingInterceptor.java:230)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.waitForTransactionsToComplete(AbstractTxLockingInterceptor.java:210)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.lockKeyAndCheckOwnership(AbstractTxLockingInterceptor.java:175)
at
org.infinispan.interceptors.locking.PessimisticLockingInterceptor.visitPutKeyValueCommand(PessimisticLockingInterceptor.java:120)
{noformat}
This can be reproduced with the attached unit test.
(Use NUM_NODES_TO_STOP_FOR_TEST=0 to not stop any nodes - the test succeeds in that case)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:54 a.m.
[
https://issues.jboss.org/browse/ISPN-2469?page=com.atlassian.jira.plugin....
]
Adrian Nistor commented on ISPN-2469:
-------------------------------------
Hi Carsten,
I have run your unit test against 5.2.0.Beta5 and it passes now. It does fail on Beta4, so
I think it's worth merging your unit test for regression.
Your suggestion regarding AbstractTxLockingInterceptor.waitForTransactionsToComplete() was
implemented in ISPN-2410/ISPN-2472. I believe this fixes the issue and can be closed as
duplicate of ISPN-2410. Could you please also try this and confirm?
Thanks!
lock() producing timeout exceptions after nodes have left
---------------------------------------------------------
Key: ISPN-2469
URL: https://issues.jboss.org/browse/ISPN-2469
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency, Transactions
Affects Versions: 5.2.0.Beta3
Reporter: Carsten Lohmann
Assignee: Adrian Nistor
Priority: Blocker
Fix For: 5.2.0.CR1, 5.2.0.Final
Attachments: LockAfterNodesLeftTest.java
I have a replicated cache with locking mode set to PESSIMISTIC on which I use explicit
locking before putting some value.
After nodes have left the cluster, this does not work anymore and I get TimeoutExceptions
like:
{noformat}
2012-11-02 11:14:12,057 ERROR [InvocationContextInterceptor]
(LockAfterNodesLeftTest.Putter-0) ISPN000136: Execution error
org.infinispan.util.concurrent.TimeoutException: Could not acquire lock on key on behalf
of transaction GlobalTransaction:<NodeA-31597>:4:local. Lock is being held by
GlobalTransaction:<NodeA-31597>:4:local
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.newTimeoutException(AbstractTxLockingInterceptor.java:230)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.waitForTransactionsToComplete(AbstractTxLockingInterceptor.java:210)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.lockKeyAndCheckOwnership(AbstractTxLockingInterceptor.java:175)
at
org.infinispan.interceptors.locking.PessimisticLockingInterceptor.visitPutKeyValueCommand(PessimisticLockingInterceptor.java:120)
{noformat}
This can be reproduced with the attached unit test.
(Use NUM_NODES_TO_STOP_FOR_TEST=0 to not stop any nodes - the test succeeds in that case)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:43 p.m.
[
https://issues.jboss.org/browse/ISPN-2469?page=com.atlassian.jira.plugin....
]
Adrian Nistor updated ISPN-2469:
--------------------------------
Fix Version/s: (was: 5.2.0.Final)
(was: 5.2.0.CR1)
lock() producing timeout exceptions after nodes have left
---------------------------------------------------------
Key: ISPN-2469
URL: https://issues.jboss.org/browse/ISPN-2469
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency, Transactions
Affects Versions: 5.2.0.Beta3
Reporter: Carsten Lohmann
Assignee: Adrian Nistor
Priority: Blocker
Attachments: LockAfterNodesLeftTest.java
I have a replicated cache with locking mode set to PESSIMISTIC on which I use explicit
locking before putting some value.
After nodes have left the cluster, this does not work anymore and I get TimeoutExceptions
like:
{noformat}
2012-11-02 11:14:12,057 ERROR [InvocationContextInterceptor]
(LockAfterNodesLeftTest.Putter-0) ISPN000136: Execution error
org.infinispan.util.concurrent.TimeoutException: Could not acquire lock on key on behalf
of transaction GlobalTransaction:<NodeA-31597>:4:local. Lock is being held by
GlobalTransaction:<NodeA-31597>:4:local
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.newTimeoutException(AbstractTxLockingInterceptor.java:230)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.waitForTransactionsToComplete(AbstractTxLockingInterceptor.java:210)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.lockKeyAndCheckOwnership(AbstractTxLockingInterceptor.java:175)
at
org.infinispan.interceptors.locking.PessimisticLockingInterceptor.visitPutKeyValueCommand(PessimisticLockingInterceptor.java:120)
{noformat}
This can be reproduced with the attached unit test.
(Use NUM_NODES_TO_STOP_FOR_TEST=0 to not stop any nodes - the test succeeds in that case)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:43 p.m.
[
https://issues.jboss.org/browse/ISPN-2469?page=com.atlassian.jira.plugin....
]
Adrian Nistor commented on ISPN-2469:
-------------------------------------
After closer analysis, this is not a duplicate of ISPN-2410/ISPN-2472 but the fix is the
one suggested by Carsten, which is already included in ISPN-2472. Can close it now.
lock() producing timeout exceptions after nodes have left
---------------------------------------------------------
Key: ISPN-2469
URL: https://issues.jboss.org/browse/ISPN-2469
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency, Transactions
Affects Versions: 5.2.0.Beta3
Reporter: Carsten Lohmann
Assignee: Adrian Nistor
Priority: Blocker
Attachments: LockAfterNodesLeftTest.java
I have a replicated cache with locking mode set to PESSIMISTIC on which I use explicit
locking before putting some value.
After nodes have left the cluster, this does not work anymore and I get TimeoutExceptions
like:
{noformat}
2012-11-02 11:14:12,057 ERROR [InvocationContextInterceptor]
(LockAfterNodesLeftTest.Putter-0) ISPN000136: Execution error
org.infinispan.util.concurrent.TimeoutException: Could not acquire lock on key on behalf
of transaction GlobalTransaction:<NodeA-31597>:4:local. Lock is being held by
GlobalTransaction:<NodeA-31597>:4:local
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.newTimeoutException(AbstractTxLockingInterceptor.java:230)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.waitForTransactionsToComplete(AbstractTxLockingInterceptor.java:210)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.lockKeyAndCheckOwnership(AbstractTxLockingInterceptor.java:175)
at
org.infinispan.interceptors.locking.PessimisticLockingInterceptor.visitPutKeyValueCommand(PessimisticLockingInterceptor.java:120)
{noformat}
This can be reproduced with the attached unit test.
(Use NUM_NODES_TO_STOP_FOR_TEST=0 to not stop any nodes - the test succeeds in that case)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:45 p.m.
[
https://issues.jboss.org/browse/ISPN-2469?page=com.atlassian.jira.plugin....
]
Adrian Nistor resolved ISPN-2469.
---------------------------------
Resolution: Done
Fix already incorporated in ISPN-2472.
lock() producing timeout exceptions after nodes have left
---------------------------------------------------------
Key: ISPN-2469
URL: https://issues.jboss.org/browse/ISPN-2469
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency, Transactions
Affects Versions: 5.2.0.Beta3
Reporter: Carsten Lohmann
Assignee: Adrian Nistor
Priority: Blocker
Attachments: LockAfterNodesLeftTest.java
I have a replicated cache with locking mode set to PESSIMISTIC on which I use explicit
locking before putting some value.
After nodes have left the cluster, this does not work anymore and I get TimeoutExceptions
like:
{noformat}
2012-11-02 11:14:12,057 ERROR [InvocationContextInterceptor]
(LockAfterNodesLeftTest.Putter-0) ISPN000136: Execution error
org.infinispan.util.concurrent.TimeoutException: Could not acquire lock on key on behalf
of transaction GlobalTransaction:<NodeA-31597>:4:local. Lock is being held by
GlobalTransaction:<NodeA-31597>:4:local
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.newTimeoutException(AbstractTxLockingInterceptor.java:230)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.waitForTransactionsToComplete(AbstractTxLockingInterceptor.java:210)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.lockKeyAndCheckOwnership(AbstractTxLockingInterceptor.java:175)
at
org.infinispan.interceptors.locking.PessimisticLockingInterceptor.visitPutKeyValueCommand(PessimisticLockingInterceptor.java:120)
{noformat}
This can be reproduced with the attached unit test.
(Use NUM_NODES_TO_STOP_FOR_TEST=0 to not stop any nodes - the test succeeds in that case)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:20 p.m.
[
https://issues.jboss.org/browse/ISPN-2469?page=com.atlassian.jira.plugin....
]
Mircea Markus updated ISPN-2469:
--------------------------------
Fix Version/s: 5.2.0.Beta5
lock() producing timeout exceptions after nodes have left
---------------------------------------------------------
Key: ISPN-2469
URL: https://issues.jboss.org/browse/ISPN-2469
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency, Transactions
Affects Versions: 5.2.0.Beta3
Reporter: Carsten Lohmann
Assignee: Adrian Nistor
Priority: Blocker
Fix For: 5.2.0.Beta5
Attachments: LockAfterNodesLeftTest.java
I have a replicated cache with locking mode set to PESSIMISTIC on which I use explicit
locking before putting some value.
After nodes have left the cluster, this does not work anymore and I get TimeoutExceptions
like:
{noformat}
2012-11-02 11:14:12,057 ERROR [InvocationContextInterceptor]
(LockAfterNodesLeftTest.Putter-0) ISPN000136: Execution error
org.infinispan.util.concurrent.TimeoutException: Could not acquire lock on key on behalf
of transaction GlobalTransaction:<NodeA-31597>:4:local. Lock is being held by
GlobalTransaction:<NodeA-31597>:4:local
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.newTimeoutException(AbstractTxLockingInterceptor.java:230)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.waitForTransactionsToComplete(AbstractTxLockingInterceptor.java:210)
at
org.infinispan.interceptors.locking.AbstractTxLockingInterceptor.lockKeyAndCheckOwnership(AbstractTxLockingInterceptor.java:175)
at
org.infinispan.interceptors.locking.PessimisticLockingInterceptor.visitPutKeyValueCommand(PessimisticLockingInterceptor.java:120)
{noformat}
This can be reproduced with the attached unit test.
(Use NUM_NODES_TO_STOP_FOR_TEST=0 to not stop any nodes - the test succeeds in that case)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4160
days inactive
4192
days old
infinispan-issues@lists.jboss.org
17 comments
3 participants
participants (3)
-
Adrian Nistor (JIRA) -
Carsten Lohmann (JIRA)
-
Mircea Markus (JIRA)