This week's book giveaways are in the Refactoring and Agile forums. We're giving away four copies each of Re-engineering Legacy Software and Docker in Action and have the authors on-line! See this thread and this one for details.
problem: Users will be working on their app retrieving records and then updating them. However, occasionally, they get a record that had nothing to do with their search. It is as if the record was cached from another user's search and different users are then getting that instead of the one they requested. A new session does not change the outcome. Once they get the problem it stays and they can no longer be productive. Coming back to the app after a couple hours seems to work.
The model layer is SB calling EB and the SB has container managed transaction set. The app server is OracleAS. Is there a setting on the server that auto caches? Is this set in the descriptor?