Show Table of Contents
21.4.8. Troubleshooting
This section will describe some common locking problems and their solution.
21.4.8.1. 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
equalsandhashCodecorrectly 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 unmarshalled.
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.