If you can see by debugging (or easier by using the P6Spy jdbc tracer) that ojb executes the correct insert or update, then the problem can not be cause dby cache / gc interaction.
The only explanation i have for such a behaviour is that a database commit is not done after executing your statement.
Why could this happen? JBOSS is a fullfledged J2EE container with JTA transaction manager and Tomcat isn't.
SO under commit you must use explicit commits.
Please check your OJB.properties settings that define the transactional behaviour.
cheeers, Thomas
Sukesh Garg wrote:
My application accesses OJB via the JBOSS startup daemons and TOMCAT.
The database gets updated correctly when the operation is performed via
the JBOSS daemon.
However, if the operation is performed via tomcat, the db does not get
updated. There are no errors reported.
If I enable the debugger and put a breakpoint, then the db gets updated properly. It seems as if the application is too fast for the cache to update the database and garbage collection kicks in and cleans the update object.
I am using ObjectCacheDefaultImpl. I tried explicitly marking the object dirty but no success.
Would really appreciate any help.
thx, Sukesh
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
