9:34 p.m.
Mircea Markus created ISPN-2466:
-----------------------------------
Summary: Unlock called twice doesn't behave correctly
Key: ISPN-2466
URL: https://issues.jboss.org/browse/ISPN-2466
Project: Infinispan
Issue Type: Feature Request
Components: Locking and Concurrency
Affects Versions: 5.2.0.Beta3
Reporter: Mircea Markus
Assignee: Manik Surtani
Fix For: 5.2.0.CR1
Taken from ISPN-2458:
<snip>
When the lock is acquired after the first unlock, the second unlock fails with
IllegalMonitorStateException in OwnableReentrantLock.tryAcquire(...), but the reference
count is still decremented in AbstractPerEntryLockContainer.releaseLock(...). This results
in further IllegalStateException: Negative reference count for lock.
</snip>
Even if the ISE occurs, the lock counter should not be affected.
--
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
9:34 p.m.
[
https://issues.jboss.org/browse/ISPN-2466?page=com.atlassian.jira.plugin....
]
Mircea Markus updated ISPN-2466:
--------------------------------
Priority: Critical (was: Major)
Unlock called twice doesn't behave correctly
--------------------------------------------
Key: ISPN-2466
URL: https://issues.jboss.org/browse/ISPN-2466
Project: Infinispan
Issue Type: Feature Request
Components: Locking and Concurrency
Affects Versions: 5.2.0.Beta3
Reporter: Mircea Markus
Assignee: Manik Surtani
Priority: Critical
Fix For: 5.2.0.CR1
Taken from ISPN-2458:
<snip>
When the lock is acquired after the first unlock, the second unlock fails with
IllegalMonitorStateException in OwnableReentrantLock.tryAcquire(...), but the reference
count is still decremented in AbstractPerEntryLockContainer.releaseLock(...). This results
in further IllegalStateException: Negative reference count for lock.
</snip>
Even if the ISE occurs, the lock counter should not be affected.
--
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:07 a.m.
[
https://issues.jboss.org/browse/ISPN-2466?page=com.atlassian.jira.plugin....
]
Radim Vansa updated ISPN-2466:
------------------------------
Issue Type: Bug (was: Feature Request)
Unlock called twice doesn't behave correctly
--------------------------------------------
Key: ISPN-2466
URL: https://issues.jboss.org/browse/ISPN-2466
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency
Affects Versions: 5.2.0.Beta3
Reporter: Mircea Markus
Assignee: Manik Surtani
Priority: Critical
Fix For: 5.2.0.CR1
Taken from ISPN-2458:
<snip>
When the lock is acquired after the first unlock, the second unlock fails with
IllegalMonitorStateException in OwnableReentrantLock.tryAcquire(...), but the reference
count is still decremented in AbstractPerEntryLockContainer.releaseLock(...). This results
in further IllegalStateException: Negative reference count for lock.
</snip>
Even if the ISE occurs, the lock counter should not be affected.
--
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:17 p.m.
[
https://issues.jboss.org/browse/ISPN-2466?page=com.atlassian.jira.plugin....
]
Manik Surtani updated ISPN-2466:
--------------------------------
Description:
Taken from ISPN-2458:
{quote}
When the lock is acquired after the first unlock, the second unlock fails with
IllegalMonitorStateException in OwnableReentrantLock.tryAcquire(...), but the reference
count is still decremented in AbstractPerEntryLockContainer.releaseLock(...). This results
in further IllegalStateException: Negative reference count for lock.
{quote}
If the ISE occurs, the lock counter should not be affected.
was:
Taken from ISPN-2458:
<snip>
When the lock is acquired after the first unlock, the second unlock fails with
IllegalMonitorStateException in OwnableReentrantLock.tryAcquire(...), but the reference
count is still decremented in AbstractPerEntryLockContainer.releaseLock(...). This results
in further IllegalStateException: Negative reference count for lock.
</snip>
Even if the ISE occurs, the lock counter should not be affected.
Unlock called twice doesn't behave correctly
--------------------------------------------
Key: ISPN-2466
URL: https://issues.jboss.org/browse/ISPN-2466
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency
Affects Versions: 5.2.0.Beta3
Reporter: Mircea Markus
Assignee: Manik Surtani
Priority: Critical
Fix For: 5.2.0.CR1
Taken from ISPN-2458:
{quote}
When the lock is acquired after the first unlock, the second unlock fails with
IllegalMonitorStateException in OwnableReentrantLock.tryAcquire(...), but the reference
count is still decremented in AbstractPerEntryLockContainer.releaseLock(...). This results
in further IllegalStateException: Negative reference count for lock.
{quote}
If the ISE occurs, the lock counter should not be affected.
--
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:17 p.m.
[
https://issues.jboss.org/browse/ISPN-2466?page=com.atlassian.jira.plugin....
]
Manik Surtani updated ISPN-2466:
--------------------------------
Description:
Taken from ISPN-2458:
{quote}
When the lock is acquired after the first unlock, the second unlock fails with an
{{IllegalMonitorStateException}} in {{OwnableReentrantLock.tryAcquire(...)}}, but the
reference count is still decremented in
{{AbstractPerEntryLockContainer.releaseLock(...)}}. This results in further
{{IllegalStateException: Negative reference count for lock}}.
{quote}
If the ISE occurs, the lock counter should not be affected.
was:
Taken from ISPN-2458:
{quote}
When the lock is acquired after the first unlock, the second unlock fails with
IllegalMonitorStateException in OwnableReentrantLock.tryAcquire(...), but the reference
count is still decremented in AbstractPerEntryLockContainer.releaseLock(...). This results
in further IllegalStateException: Negative reference count for lock.
{quote}
If the ISE occurs, the lock counter should not be affected.
Unlock called twice doesn't behave correctly
--------------------------------------------
Key: ISPN-2466
URL: https://issues.jboss.org/browse/ISPN-2466
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency
Affects Versions: 5.2.0.Beta3
Reporter: Mircea Markus
Assignee: Manik Surtani
Priority: Critical
Fix For: 5.2.0.CR1
Taken from ISPN-2458:
{quote}
When the lock is acquired after the first unlock, the second unlock fails with an
{{IllegalMonitorStateException}} in {{OwnableReentrantLock.tryAcquire(...)}}, but the
reference count is still decremented in
{{AbstractPerEntryLockContainer.releaseLock(...)}}. This results in further
{{IllegalStateException: Negative reference count for lock}}.
{quote}
If the ISE occurs, the lock counter should not be affected.
--
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:45 p.m.
New subject: [JBoss JIRA] (ISPN-2466) Repeated unlocking causes errors with reference counting
[
https://issues.jboss.org/browse/ISPN-2466?page=com.atlassian.jira.plugin....
]
Manik Surtani updated ISPN-2466:
--------------------------------
Summary: Repeated unlocking causes errors with reference counting (was: Unlock called
twice doesn't behave correctly)
Repeated unlocking causes errors with reference counting
--------------------------------------------------------
Key: ISPN-2466
URL: https://issues.jboss.org/browse/ISPN-2466
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency
Affects Versions: 5.2.0.Beta3
Reporter: Mircea Markus
Assignee: Manik Surtani
Priority: Critical
Fix For: 5.2.0.CR1
Taken from ISPN-2458:
{quote}
When the lock is acquired after the first unlock, the second unlock fails with an
{{IllegalMonitorStateException}} in {{OwnableReentrantLock.tryAcquire(...)}}, but the
reference count is still decremented in
{{AbstractPerEntryLockContainer.releaseLock(...)}}. This results in further
{{IllegalStateException: Negative reference count for lock}}.
{quote}
If the ISE occurs, the lock counter should not be affected.
--
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:47 p.m.
New subject: [JBoss JIRA] (ISPN-2466) Repeated unlocking causes errors with reference counting
[
https://issues.jboss.org/browse/ISPN-2466?page=com.atlassian.jira.plugin....
]
Manik Surtani updated ISPN-2466:
--------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/1447
Repeated unlocking causes errors with reference counting
--------------------------------------------------------
Key: ISPN-2466
URL: https://issues.jboss.org/browse/ISPN-2466
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency
Affects Versions: 5.2.0.Beta3
Reporter: Mircea Markus
Assignee: Manik Surtani
Priority: Critical
Fix For: 5.2.0.CR1
Taken from ISPN-2458:
{quote}
When the lock is acquired after the first unlock, the second unlock fails with an
{{IllegalMonitorStateException}} in {{OwnableReentrantLock.tryAcquire(...)}}, but the
reference count is still decremented in
{{AbstractPerEntryLockContainer.releaseLock(...)}}. This results in further
{{IllegalStateException: Negative reference count for lock}}.
{quote}
If the ISE occurs, the lock counter should not be affected.
--
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
2:50 p.m.
New subject: [JBoss JIRA] (ISPN-2466) Repeated unlocking causes errors with reference counting
[
https://issues.jboss.org/browse/ISPN-2466?page=com.atlassian.jira.plugin....
]
Dan Berindei updated ISPN-2466:
-------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
Fix integrated in master.
Repeated unlocking causes errors with reference counting
--------------------------------------------------------
Key: ISPN-2466
URL: https://issues.jboss.org/browse/ISPN-2466
Project: Infinispan
Issue Type: Bug
Components: Locking and Concurrency
Affects Versions: 5.2.0.Beta3
Reporter: Mircea Markus
Assignee: Manik Surtani
Priority: Critical
Fix For: 5.2.0.CR1
Taken from ISPN-2458:
{quote}
When the lock is acquired after the first unlock, the second unlock fails with an
{{IllegalMonitorStateException}} in {{OwnableReentrantLock.tryAcquire(...)}}, but the
reference count is still decremented in
{{AbstractPerEntryLockContainer.releaseLock(...)}}. This results in further
{{IllegalStateException: Negative reference count for lock}}.
{quote}
If the ISE occurs, the lock counter should not be affected.
--
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
4193
days inactive
4194
days old
infinispan-issues@lists.jboss.org
7 comments
4 participants
participants (4)
-
Dan Berindei (JIRA) -
Manik Surtani (JIRA)
-
Mircea Markus (JIRA)
-
Radim Vansa (JIRA)