[jboss-jira] [JBoss JIRA] (AS7-4976) Missing transaction isolation with EJB2.1 EntityBeans with pessimistic locking

Wed Jun 27 05:17:12 EDT 2012

    [ https://issues.jboss.org/browse/AS7-4976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12703498#comment-12703498 ] 

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 at 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