[JBoss JIRA] Created: (JBCACHE-1183) Acquired WL lock could be not released after async transaction rolback
2:44 a.m.
Acquired WL lock could be not released after async transaction rolback
----------------------------------------------------------------------
Key: JBCACHE-1183
URL: http://jira.jboss.com/jira/browse/JBCACHE-1183
Project: JBoss Cache
Issue Type: Bug
Security Level: Public (Everyone can see)
Environment: WindowsXP, jdk150_06
Reporter: Jacek Halat
Assigned To: Manik Surtani
In some cases on weblogic (and other servers where transaction manager with async
transaction rollback after timeout is used) acquired WL can be not released. Only way to
release lock is stop/start cche again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:50 a.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-1183) Acquired WL lock could be not released after async transaction rolback
[ http://jira.jboss.com/jira/browse/JBCACHE-1183?page=all ]
Jacek Halat updated JBCACHE-1183:
---------------------------------
Attachment: AsyncRollbackTxLockTest.java
To observe this issue simulate heavy-load by adding
if ("Thread-0".equals(Thread.currentThread().getName()) &&
node.getFqn().toString().equals("/a"))
Thread.sleep(1500);
in first line of PessimistickLockInterceptor.recordNodeLock() method.
Acquired WL lock could be not released after async transaction
rolback
----------------------------------------------------------------------
Key: JBCACHE-1183
URL: http://jira.jboss.com/jira/browse/JBCACHE-1183
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Environment: WindowsXP, jdk150_06
Reporter: Jacek Halat
Assigned To: Manik Surtani
Attachments: AsyncRollbackTxLockTest.java
In some cases on weblogic (and other servers where transaction manager with async
transaction rollback after timeout is used) acquired WL can be not released. Only way to
release lock is stop/start cche again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:49 p.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-1183) Acquired WL lock could be not released after async transaction rolback
[ http://jira.jboss.com/jira/browse/JBCACHE-1183?page=all ]
Manik Surtani updated JBCACHE-1183:
-----------------------------------
Fix Version/s: 1.4.1.SP5
2.1.0.GA
Affects Version/s: 1.4.1.SP4
2.0.0.GA
Complexity: High
See org.jboss.cache.transaction.AsyncRollbackTxLockTest in both 1.4.x and HEAD
Acquired WL lock could be not released after async transaction
rolback
----------------------------------------------------------------------
Key: JBCACHE-1183
URL: http://jira.jboss.com/jira/browse/JBCACHE-1183
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.0.0.GA, 1.4.1.SP4
Environment: WindowsXP, jdk150_06
Reporter: Jacek Halat
Assigned To: Manik Surtani
Fix For: 2.1.0.GA, 1.4.1.SP5
Attachments: AsyncRollbackTxLockTest.java
In some cases on weblogic (and other servers where transaction manager with async
transaction rollback after timeout is used) acquired WL can be not released. Only way to
release lock is stop/start cche again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:14 p.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-1183) Acquired WL lock could be not released after async transaction rollback
[ http://jira.jboss.com/jira/browse/JBCACHE-1183?page=all ]
Manik Surtani updated JBCACHE-1183:
-----------------------------------
Summary: Acquired WL lock could be not released after async transaction rollback
(was: Acquired WL lock could be not released after async transaction rolback)
Acquired WL lock could be not released after async transaction
rollback
-----------------------------------------------------------------------
Key: JBCACHE-1183
URL: http://jira.jboss.com/jira/browse/JBCACHE-1183
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.4.1.SP4, 2.0.0.GA
Environment: WindowsXP, jdk150_06
Reporter: Jacek Halat
Assigned To: Manik Surtani
Fix For: 1.4.1.SP5, 2.1.0.GA
Attachments: AsyncRollbackTxLockTest.java
In some cases on weblogic (and other servers where transaction manager with async
transaction rollback after timeout is used) acquired WL can be not released. Only way to
release lock is stop/start cche again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:43 p.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-1183) Acquired WL lock could be not released after async transaction rollback
[ http://jira.jboss.com/jira/browse/JBCACHE-1183?page=all ]
Manik Surtani updated JBCACHE-1183:
-----------------------------------
Fix Version/s: 1.4.1.SP6
(was: 1.4.1.SP5)
Acquired WL lock could be not released after async transaction
rollback
-----------------------------------------------------------------------
Key: JBCACHE-1183
URL: http://jira.jboss.com/jira/browse/JBCACHE-1183
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.4.1.SP4, 2.0.0.GA
Environment: WindowsXP, jdk150_06
Reporter: Jacek Halat
Assigned To: Manik Surtani
Fix For: 1.4.1.SP6, 2.1.0.GA
Attachments: AsyncRollbackTxLockTest.java
In some cases on weblogic (and other servers where transaction manager with async
transaction rollback after timeout is used) acquired WL can be not released. Only way to
release lock is stop/start cche again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:49 p.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-1183) Acquired WL lock could be not released after async transaction rollback
[ http://jira.jboss.com/jira/browse/JBCACHE-1183?page=all ]
Manik Surtani updated JBCACHE-1183:
-----------------------------------
Fix Version/s: (was: 2.1.0.GA)
Not observed in trunk (2.1.0)
Acquired WL lock could be not released after async transaction
rollback
-----------------------------------------------------------------------
Key: JBCACHE-1183
URL: http://jira.jboss.com/jira/browse/JBCACHE-1183
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.0.0.GA, 1.4.1.SP4
Environment: WindowsXP, jdk150_06
Reporter: Jacek Halat
Assigned To: Manik Surtani
Fix For: 1.4.1.SP6
Attachments: AsyncRollbackTxLockTest.java
In some cases on weblogic (and other servers where transaction manager with async
transaction rollback after timeout is used) acquired WL can be not released. Only way to
release lock is stop/start cche again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:51 p.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-1183) Acquired WL lock could be not released after async transaction rollback
[ http://jira.jboss.com/jira/browse/JBCACHE-1183?page=all ]
Manik Surtani updated JBCACHE-1183:
-----------------------------------
Fix Version/s: 1.4.1.SP7
2.1.0.GA
(was: 1.4.1.SP6)
Acquired WL lock could be not released after async transaction
rollback
-----------------------------------------------------------------------
Key: JBCACHE-1183
URL: http://jira.jboss.com/jira/browse/JBCACHE-1183
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.0.0.GA, 1.4.1.SP4
Environment: WindowsXP, jdk150_06
Reporter: Jacek Halat
Assigned To: Manik Surtani
Fix For: 1.4.1.SP7
Attachments: AsyncRollbackTxLockTest.java
In some cases on weblogic (and other servers where transaction manager with async
transaction rollback after timeout is used) acquired WL can be not released. Only way to
release lock is stop/start cche again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:51 p.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-1183) Acquired WL lock could be not released after async transaction rollback
[ http://jira.jboss.com/jira/browse/JBCACHE-1183?page=all ]
Manik Surtani updated JBCACHE-1183:
-----------------------------------
Fix Version/s: (was: 2.1.0.GA)
Acquired WL lock could be not released after async transaction
rollback
-----------------------------------------------------------------------
Key: JBCACHE-1183
URL: http://jira.jboss.com/jira/browse/JBCACHE-1183
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 2.0.0.GA, 1.4.1.SP4
Environment: WindowsXP, jdk150_06
Reporter: Jacek Halat
Assigned To: Manik Surtani
Fix For: 1.4.1.SP7
Attachments: AsyncRollbackTxLockTest.java
In some cases on weblogic (and other servers where transaction manager with async
transaction rollback after timeout is used) acquired WL can be not released. Only way to
release lock is stop/start cche again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:08 p.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-1183) Acquired WL lock could be not released after async transaction rollback
[ http://jira.jboss.com/jira/browse/JBCACHE-1183?page=all ]
Manik Surtani updated JBCACHE-1183:
-----------------------------------
Fix Version/s: 1.4.1.SP8
(was: 1.4.1.SP7)
Acquired WL lock could be not released after async transaction
rollback
-----------------------------------------------------------------------
Key: JBCACHE-1183
URL: http://jira.jboss.com/jira/browse/JBCACHE-1183
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.4.1.SP4, 2.0.0.GA
Environment: WindowsXP, jdk150_06
Reporter: Jacek Halat
Assigned To: Manik Surtani
Fix For: 1.4.1.SP8
Attachments: AsyncRollbackTxLockTest.java
In some cases on weblogic (and other servers where transaction manager with async
transaction rollback after timeout is used) acquired WL can be not released. Only way to
release lock is stop/start cche again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:38 p.m.
New subject: [JBoss JIRA] Updated: (JBCACHE-1183) Acquired WL lock could be not released after async transaction rollback
[ http://jira.jboss.com/jira/browse/JBCACHE-1183?page=all ]
Manik Surtani updated JBCACHE-1183:
-----------------------------------
Fix Version/s: 1.4.X
(was: 1.4.1.SP8)
Acquired WL lock could be not released after async transaction
rollback
-----------------------------------------------------------------------
Key: JBCACHE-1183
URL: http://jira.jboss.com/jira/browse/JBCACHE-1183
Project: JBoss Cache
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.4.1.SP4, 2.0.0.GA
Environment: WindowsXP, jdk150_06
Reporter: Jacek Halat
Assigned To: Manik Surtani
Fix For: 1.4.X
Attachments: AsyncRollbackTxLockTest.java
In some cases on weblogic (and other servers where transaction manager with async
transaction rollback after timeout is used) acquired WL can be not released. Only way to
release lock is stop/start cche again.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6040
days inactive
6130
days old
9 comments
2 participants
participants (2)
-
Jacek Halat (JIRA) -
Manik Surtani (JIRA)