[
https://issues.jboss.org/browse/ISPN-3055?page=com.atlassian.jira.plugin....
]
Pedro Ruivo commented on ISPN-3055:
-----------------------------------
I've take a look at it and the good new is it has nothing to do with the node restart
:)
If you start firs the Reader and then the Writer and abort a transaction, the bug will be
revealed.
the bug is quite simple. we are not sending the RollbackCommand if the
lockingMode==PESSIMISTIC.
Thanks Deyan!
Unreleased lock after node restart
----------------------------------
Key: ISPN-3055
URL:
https://issues.jboss.org/browse/ISPN-3055
Project: Infinispan
Issue Type: Bug
Affects Versions: 5.2.1.Final
Environment: Debian Squeeze Amd 64, JDK 1.6.0_32
Reporter: Deyan Pandulev
Assignee: Pedro Ruivo
Fix For: 6.0.0.Beta1, 6.0.0.Final
Attachments: SimpleClusterRead.java, SimpleClusterWriter.java,
simple_cluster_node1.xml, simple_cluster_node2.xml
Using dummy transaction manager I was able to produce locks that are not released. The
same behavior can be reproduced with Glassfish AS 3.1.1 using its own TM.
--
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