To turn autocommit off, call Connection.setAutoCommit(false); Here's some docs: http://download.oracle.com/javase/1.4.2/docs/api/java/sql/Connection.html
If you don't turn autocommit off, you will indeed discover that the automatic commit process can close various cursors and result sets at awkward times: http://db.apache.org/derby/docs/10.6/devguide/cdevconcepts29416.html You can gain a better understanding of the behavior of your application by learning to read the derby.log logfile, and by learning to use the various Derby trace flags, such as derby.language.logStatementText. If you can post more details about the specifics of your situation, the community will be able to give you more detailed suggestions. thanks, bryan
