[JBoss JIRA] (AS7-4976) Missing transaction isolation with EJB2.1 EntityBeans with pessimistic locking
10:35 a.m.
Klaus Benary created AS7-4976:
---------------------------------
Summary: Missing transaction isolation with EJB2.1 EntityBeans with
pessimistic locking
Key: AS7-4976
URL: https://issues.jboss.org/browse/AS7-4976
Project: Application Server 7
Issue Type: Bug
Components: EJB
Affects Versions: 7.1.1.Final
Environment: Windows 7 Pro SP1 (64bit); JDK 1.6.0_31 (64bit); Oracle Database 11g
Release 11.1.0.6.0 - 64bit Production; AS71.1Final / AS71.2 latest build
Reporter: Klaus Benary
Assignee: jaikiran pai
On pessimistically locked EntityBeans, a transaction B can see the result of transaction A
even if thransaction A threw an exception and thus did not commit.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:39 a.m.
[
https://issues.jboss.org/browse/AS7-4976?page=com.atlassian.jira.plugin.s...
]
Klaus Benary updated AS7-4976:
------------------------------
Attachment: JCTest.zip
Reproducer eclipse project added
Missing transaction isolation with EJB2.1 EntityBeans with
pessimistic locking
------------------------------------------------------------------------------
Key: AS7-4976
URL: https://issues.jboss.org/browse/AS7-4976
Project: Application Server 7
Issue Type: Bug
Components: EJB
Affects Versions: 7.1.1.Final
Environment: Windows 7 Pro SP1 (64bit); JDK 1.6.0_31 (64bit); Oracle Database 11g
Release 11.1.0.6.0 - 64bit Production; AS71.1Final / AS71.2 latest build
Reporter: Klaus Benary
Assignee: jaikiran pai
Labels: entitybean, transactionisolation
Attachments: JCTest.zip
On pessimistically locked EntityBeans, a transaction B can see the result of transaction
A even if thransaction A threw an exception and thus did not commit.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:39 p.m.
[
https://issues.jboss.org/browse/AS7-4976?page=com.atlassian.jira.plugin.s...
]
Stuart Douglas resolved AS7-4976.
---------------------------------
Fix Version/s: 7.1.3.Final (EAP)
7.2.0.Alpha1
Resolution: Done
Missing transaction isolation with EJB2.1 EntityBeans with
pessimistic locking
------------------------------------------------------------------------------
Key: AS7-4976
URL: https://issues.jboss.org/browse/AS7-4976
Project: Application Server 7
Issue Type: Bug
Components: EJB
Affects Versions: 7.1.1.Final
Environment: Windows 7 Pro SP1 (64bit); JDK 1.6.0_31 (64bit); Oracle Database 11g
Release 11.1.0.6.0 - 64bit Production; AS71.1Final / AS71.2 latest build
Reporter: Klaus Benary
Assignee: Stuart Douglas
Labels: entitybean, transactionisolation
Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1
Attachments: JCTest-maven.zip, JCTest.zip
On pessimistically locked EntityBeans, a transaction B can see the result of transaction
A even if thransaction A threw an exception and thus did not commit.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:17 a.m.
[
https://issues.jboss.org/browse/AS7-4976?page=com.atlassian.jira.plugin.s...
]
Lennart Petersson commented on AS7-4976:
----------------------------------------
Hi!
Have what I think is a similar testcase where an entity bean is updated by first delete
the bean and then recreate it, all within the same transaction. And we got the very same
exception:
11:09:49,103 ERROR [org.jboss.as.ejb3] (http-/127.0.0.1:8080-1) JBAS014138: Exception
releasing entity: java.lang.IllegalStateException: JBAS014172: Instance
[org.jboss.as.cmp.component.CmpEntityBeanComponentInstance@a353ed] not found in cache
at
org.jboss.as.ejb3.component.entity.entitycache.ReferenceCountingEntityCache.release(ReferenceCountingEntityCache.java:85)
[jboss-as-ejb3-7.2.0.Alpha1-SNAPSHOT.jar:7.2.0.Alpha1-SNAPSHOT]
I hoped for this issue to be solved in 7.2.0.Alpha1 but not at least in the snapshot i
checked out yesterday. Still getting this exception.
regards,
Lennart
Redpill Linpro
Missing transaction isolation with EJB2.1 EntityBeans with
pessimistic locking
------------------------------------------------------------------------------
Key: AS7-4976
URL: https://issues.jboss.org/browse/AS7-4976
Project: Application Server 7
Issue Type: Bug
Components: EJB
Affects Versions: 7.1.1.Final
Environment: Windows 7 Pro SP1 (64bit); JDK 1.6.0_31 (64bit); Oracle Database 11g
Release 11.1.0.6.0 - 64bit Production; AS71.1Final / AS71.2 latest build
Reporter: Klaus Benary
Assignee: Stuart Douglas
Labels: entitybean, transactionisolation
Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1
Attachments: JCTest-maven.zip, JCTest.zip
On pessimistically locked EntityBeans, a transaction B can see the result of transaction
A even if thransaction A threw an exception and thus did not commit.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:44 a.m.
[
https://issues.jboss.org/browse/AS7-4976?page=com.atlassian.jira.plugin.s...
]
Lennart Petersson commented on AS7-4976:
----------------------------------------
Looking into
org.jboss.as.ejb3.component.entity.entitycache.ReferenceCountingEntityCache.release I see
following:
public synchronized void release(final EntityBeanComponentInstance instance, boolean
success) {
if (instance.isDiscarded()) {
return;
}
if (instance.getPrimaryKey() == null) return; // TODO: Should this be an
Exception
final CacheEntry cacheEntry = cache.get(instance.getPrimaryKey());
if (cacheEntry == null) {
------> THIS IS WHERE EXCEPTION IS THROWN
throw EjbLogger.EJB3_LOGGER.entityBeanInstanceNotFoundInCache(instance);
}
if (cacheEntry.replacedInstance != null) {
------> THIS SOUNDS LIKE THE PROBLEMATIC SITUATION BUT WE NEVER ARRIVES HERE DUE TO
NULL CACHEENTRY
//this can happen if an entity is removed and a new entity with the same PK is
added in a transactions
if (instance == cacheEntry.replacedInstance) {
if (success) {
cacheEntry.instance = cacheEntry.replacedInstance;
} else if (cacheEntry.instance.isDiscarded()) {
//if the TX was a failure, and the previous instance has been
discarded
//we just remove the entry and return
cache.remove(instance.getPrimaryKey());
return;
}
cacheEntry.replacedInstance = null;
}
}
...
...
This might be interesting, or not...
regards,
/L
Missing transaction isolation with EJB2.1 EntityBeans with
pessimistic locking
------------------------------------------------------------------------------
Key: AS7-4976
URL: https://issues.jboss.org/browse/AS7-4976
Project: Application Server 7
Issue Type: Bug
Components: EJB
Affects Versions: 7.1.1.Final
Environment: Windows 7 Pro SP1 (64bit); JDK 1.6.0_31 (64bit); Oracle Database 11g
Release 11.1.0.6.0 - 64bit Production; AS71.1Final / AS71.2 latest build
Reporter: Klaus Benary
Assignee: Stuart Douglas
Labels: entitybean, transactionisolation
Fix For: 7.1.3.Final (EAP), 7.2.0.Alpha1
Attachments: JCTest-maven.zip, JCTest.zip
On pessimistically locked EntityBeans, a transaction B can see the result of transaction
A even if thransaction A threw an exception and thus did not commit.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5051
days inactive
5067
days old
6 comments
4 participants
participants (4)
-
jaikiran pai (JIRA) -
Klaus Benary (JIRA)
-
Lennart Petersson (JIRA)
-
Stuart Douglas (JIRA)