Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> Controlling transactions when JDBC connection closed?
We're reusing a set of Java classes from an "old" application in a new application. The old application used a PC database; the new one is using Oracle. It appears that the PC database implicitly rolled back transactions if a connection to the database was closed. However, with Oracle, is appears that when we close a JDBC connection, the current transaction is implicitly committed.
I understand that these classes *should* be explicitly controlling their transactions, and committing or rolling back before closing the connection to the database, and we will have to fix these classes to do so. However, I would also like to know if it's possible to change this behaviour of Oracle of implicitly committing upon close. Is there a JDBC configuration file or something like that? This is Oracle 8.1.7, in a JRUN environment, if that's any help. (As you can tell, this Java stuff is not my forte...)
Thanx for any advice.
-ak
This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses.
www.mimesweeper.com
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051 San Diego, California -- Public Internet access / Mailing Liststo: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). Received on Sun Aug 26 2001 - 21:18:48 CDT
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
![]() |
![]() |