Re: empty ResultSet after connection commit
Date: October 17, 2011 10:11AM
As I know, all the queries after the transaction commit should not be executed until the commit ended either successfully or rolled back, and in my test i didn't get any errors from the commit work.
Also I am not sure if its possible to reach a deadlock with a single connection & single DB, since the 5 connections are doing the same sequence of transactions & queries but each on its own database (the databases are identical). the idea is that we are trying to do he stress testing with running the 5 connection at the same time.
As I mentioned before the irregular behavior happened to one or 2 connections and the others continue working.
Moreover, if I made my test to run a single connection & DB, it ends correctly with no errors.. I think it may be related to the huge number of transactions that I am doing!!
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.