[JBoss JIRA] Created: (JBAS-7238) jdbc2 pm: ejbStore and db synchronization ordering
by Alexey Loubyansky (JIRA)
jdbc2 pm: ejbStore and db synchronization ordering
--------------------------------------------------
Key: JBAS-7238
URL: https://jira.jboss.org/jira/browse/JBAS-7238
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: CMP service
Affects Versions: JBossAS-5.1.0.GA, JBossAS-4.2.3.GA
Reporter: Alexey Loubyansky
Assignee: Alexey Loubyansky
Fix For: JBossAS-5.2.0.Beta1
In "cmp2.x jdbc2 pm" persistence manager there is a probability that the database synchronization will occur before the invocations of ejbStore resulting in the lose of changes done as part of the ejbStore. This happens because ejbStore invocations and db synchronization are triggered from different javax.transaction.Synchronization instances.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 9 months
[JBoss JIRA] Created: (JBAS-7313) jdbc2 pm: table view collisions between beans from different jars in the same tx
by Alexey Loubyansky (JIRA)
jdbc2 pm: table view collisions between beans from different jars in the same tx
--------------------------------------------------------------------------------
Key: JBAS-7313
URL: https://jira.jboss.org/jira/browse/JBAS-7313
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: CMP service
Affects Versions: JBossAS-5.1.0.GA, JBossAS-4.2.3.GA
Reporter: Alexey Loubyansky
Assignee: Alexey Loubyansky
Fix For: JBossAS-5.2.0.GA
This bug was introduced by JBAS-7238. The problem is "views" object, which is created one per EJB JAR for every transaction, is stored in GlobalTxSynchronization under the same key for all the EJBs no matter from which JAR they are. This results in collisions in case EJBs from different JARs are involved in the same transaction, i.e. views from for one JAR might overwrite the views from another JAR.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
16 years, 9 months