+1 On Jan 13, 2011, at 3:20 PM, Rick Hillegas (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/DERBY-4869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12981458#action_12981458 > ] > > Rick Hillegas commented on DERBY-4869: > -------------------------------------- > > JDBC 4.1 adds a new method to Connecton: abort(Executor). This method > attempts to terminate the Connection and release its resources. If a > SecurityManager is in place, the new method expects that SQLPermission( > "callAbort" ) ) will have been granted to the abort() method. I believe that > the motivation for this permission is to prevent an ordinary user of a pooled > connection from accidentally destroying the underlying physical connection to > the database, since that is one of the consequences of calling abort(). Only > privileged code would be allowed to intervene and abort runaway connections. > > I think that we should document how to grant this permission, probably in the > JDBC section of the Reference Guide. > > I also think that our default and template security policies should not grant > this permission to any of the Derby code domains. My sense right now is that > the permission should be granted to an outer application code domain only > accessed by superusers. > > Other or concurring opinions? > > Thanks, > -Rick > > >> Implement JDBC 4.1, the api increment introduced by Java 7 >> ---------------------------------------------------------- >> >> Key: DERBY-4869 >> URL: https://issues.apache.org/jira/browse/DERBY-4869 >> Project: Derby >> Issue Type: Improvement >> Components: JDBC >> Reporter: Rick Hillegas >> Attachments: derby-4869-01-ac-rs-getObject.diff, >> derby-4869-01-ad-rs-getObject.diff, derby-4869-02-aa-cs-ps-addBatch.diff, >> derby-4869-02-ab-cs-ps-addBatch.diff, >> derby-4869-03-aa-rs-getObject-errorCleanup.diff, >> derby-4869-04-aa-rs-getObject-simplification.diff, >> derby-4869-05-aa-rs-getObject-exception.diff, >> derby-4869-06-aa-cs-getObject.diff, derby-4869-06-ab-cs-getObject.diff, >> derby-4869-07-aa-timedisplacement.diff, derby-4869-08-ac-nullHandling.diff, >> derby-4869-exp-01-aa-noTryCatch.diff, disable-tests.diff, >> JDBC_4.1_Changes.html, timezone.diff >> >> >> This is a master issue logged to track our work implementing JDBC 4.1, the >> changes to the java.sql and javax.sql packages introduced by Java 7. > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. >
Lance Andersen| Principal Member of Technical Staff | +1.781.442.2037 Oracle Java Engineering 1 Network Drive Burlington, MA 01803 [email protected] Oracle is committed to developing practices and products that help protect the environment
