JDBC 4.1 adds new features to the Connection interface:
- Aborting connections - The abort(Executor) method aborts
a running connection. Outstanding transactional work is rolled back, and the
physical connection to the database is destroyed. When running under a Java
SecurityManager, this method can be called only if
SQLPermission("callAbort") has been granted both to the
Derby JDBC driver (in
derby.jar and derbyclient.jar) and to the
application code that calls Connection.abort(). For security reasons,
permission to execute this method should not be granted lightly. Do not grant
this permission to application code unless you are certain that only superusers
can invoke the code. For more information, see "Granting permissions to
Derby" in the
Java DB Developer's Guide.