We are experiencing the same problem with the "db.commit()" call on mysql version 3.23.48 for -freebsd 5.0 (i386) with basically the same transaction code. We keep thinking that we must be missing something in our setup of the database connections or the usage of transactions in the Castor API. We have no problem doing a create or an OQL query, but as soon as we attempt an update IN THE SAME PROGRAM, we are hanging. Interestingly enough when you run the three transactions: create, select, and update (didn't get to implement delete because update didn't work) in separate, sequential runs of the program everything works perfectly. Another weirdness is that if (when running all transactions in the same program run) the create fails because the entity is already in the database, the update is posted to the database, but still hangs.
Does anybody have any words of wisdom or working code that they wouldn't mind sharing? In particular, can anybody show us working examples of initializing a db and performing multiple transactions on it. We are getting a PoolMan (verison 2.0.4) via JNDI which wraps the mysql connection thru mm.mysql drivers.
Cheers,
Tim Ruppert && Ben Cox
------------------------------------------------------------------------------------------------------------
Hi,what can cause a "db.commit()" call that it hangs ?
here is the regarding part of my code:
db.begin()
...
// some reading queries
...
db.commit() // this method never return's or gives an exception
db.close()the database i'm using is an oracle (8.1.7.).
thanks for any hints,
frank
