db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5590) Document optional modifyThreadGroup permssion in java 2 security permissions
Date Tue, 22 May 2012 16:02:44 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281061#comment-13281061

Rick Hillegas commented on DERBY-5590:

Hi Kim,

Thanks for the patch. These changes look straightforward and correct to me. +1.
> Document optional modifyThreadGroup permssion in java 2 security permissions
> ----------------------------------------------------------------------------
>                 Key: DERBY-5590
>                 URL: https://issues.apache.org/jira/browse/DERBY-5590
>             Project: Derby
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions:
>            Reporter: Kathey Marsden
>            Assignee: Kim Haase
>         Attachments: DERBY-5590.diff, DERBY-5590.stat, DERBY-5590.zip
> With DERBY3618 and  DERBY-4856 if modifyThreadGroup privileges are available, DERBY will
produce a thread dump in the derby.log upon asserts or session level SQLExceptions
> The two permissions that will be needed to dump the thread stack traces are:
> permission java.lang.RuntimePermission "getStackTrace";
> permission java.lang.RuntimePermission "modifyThreadGroup";
> These should be mentioned in the optional permissions at:
> http://db.apache.org/derby/docs/10.8/devguide/cdevbabejgjd.html
> These optional permissions will allow extended diagnostics, specifically  the stack traces
of all threads to be dumped to derby.log on severe errors and when derby.stream.error.extendedDiagSeverityLevel
 is set.
> It would be good to mention them here too:
> http://db.apache.org/derby/docs/10.8/ref/rrefproperextdiagsevlevel.html

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message