I did some modification as following:
1: modify jboss.xml, add one container configuration as following:
<container-configurations>
<container-configuration extends="Instance Per Transaction CMP 2.x
EntityBean">
<container-name>Optimistic CMP EntityBean</container-name>
<locking-policy>org.jboss.ejb.plugins.lock.JDBCOptimisticLock</locking-policy>
<commit-option>B</commit-option>
</container-configuration>
</container-configurations>
then shift the special bean to this configuration.
2: configure locking policy for the special bean in jbosscmp-jdbc.xml.
<load-groups>
<load-group>
<load-group-name>wo</load-group-name>
<field-name>statusDicId</field-name>
<field-name>plannedStartDateTime</field-name>
</load-group>
</load-groups>
<optimistic-locking>
<group-name>wo</group-name>
</optimistic-locking>
3: add synchronize in some places which shouldn't be concurrent invoking.
then my system passed the test of loadrunner.
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3862510#3862510
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3862510
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
JBoss-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jboss-user
