This section will describe some common locking problems and their solution.
220.127.116.11. Locking Behavior Not Working
Many JBoss users observe that locking does not seem to be working and see concurrent access to their beans, and thus dirty reads. Here are some common reasons for this:
If you have custom
container-configurations, make sure you have updated these configurations.
Make absolutely sure that you have implemented
hashCode correctly from custom/complex primary key classes.
Make absolutely sure that your custom/complex primary key classes serialize correctly. One common mistake is assuming that member variable initializations will be executed when a primary key is unmarshaled.