> I'm connecting to the database fine and executing stored procedures
> via CallableStatements. They complete without any difficulty, but
> for some reason aren't committing to the database. Looking at the
> tables from a second database tool shows no activity, yet I can edit
> the data from my Java connection as long as I don't restart my
> application.
>
> I've tried running setAutoCommit(true) explicitly when the
> connection is first created to no avail. Inside the debugger (I use
> Eclipse for Java) I've turned off autoCommit after pausing the
> application through breakpoints, run the procedure, committed, and
> then turned autoCommit on again, and it works fine after that until
> I restart the application.

Do I understand you right, that you results of procedure execution are
not committed? Can you prepare a test case, where you open a
connection via DriverManager, execute code, commit (if auto-commit is
off), close the connection, open new connection, read data and assert
that your changes were not committed? I would be really surprised if
this can happen, but if it does, this is quite serious bug.

Best regards,
Roman Rokytskyy