More information if an EJBException is thrown due to an concurrent modify if
OptimisticBeanLock active
------------------------------------------------------------------------------------------------------
Key: JBAS-4266
URL:
http://jira.jboss.com/jira/browse/JBAS-4266
Project: JBoss Application Server
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: CMP service
Reporter: Wolf-Dieter Fink
Assigned To: Alexey Loubyansky
in case of a concurrent modify if optimistic lock is active the EJBException is not very
helpful.
See org.jboss.ejb.plugins.cmp.jdbc2.schema.EntityTable.java:1761 (4.0.4.GA)
In this case there is a check rows != 1, so only one row is affected.
catch the Exception outside and fill in better information in a future relaease.
This will give a better feeling and increase the speed of analysing.
It looks like the same for IPT container:
JDBCAbstractCreateCommand.java and JDBCStoreEntityCommand.java
--
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