Hi there,

My team's currently using Hibernate to build a huge application for one of our client, but we're facing a strange problem that I thought I would expose here just in case someone already came up with the same problem and a solution.

It's a web application in which some actions are tracked in the database. An entity has been created to store the modifications made on some others objects. If a user is doing one of these observed actions in the application, new entities are created and saved in the database. These entities contain properties such as who modified, when and what has been modified. We're not looking for a better way of managing this tracking operation.

- if the application is deployed within Tomcat, everything works perfectly
- if the application is deployed within Weblogic 10, it works randomly (usually only once) then stops. This means that the tracking entities are still and always saved in the database, but the page that should actually display them do never show the new ones (like I'm having a read problem). Up until now, the only way I found to have them displayed is to close the browser, start a new one and request the tracking page again.

This has first made me think about a caching problem. But having read the whole caching documentation, I'm not pretty sure any more. Anyway, I explicitly disabled the L2 cache (even if it's not really needed).

Has anyone ever experienced such a problem before ? Could that come from Weblogic (the only difference is the running environment) ?

Thanks for your time and help.

J