Dear Thomas,
Thanks for your response.
The DB does get updated by the JBOSS daemon.
However, when the OJB implementation is accessed directly by tomcat
running in the same JBOSS instance, it does not update the database.
You are right that the corresponding sql update does not happen(no
corre
Hi Sukesh,
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
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
