You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (Created) (JIRA)" <ji...@apache.org> on 2012/01/28 01:39:35 UTC

[jira] [Created] (DERBY-5590) Document optional modifyThreadGroup permssion in java 2 security permissions

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
            Reporter: Kathey Marsden


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

        

[jira] [Updated] (DERBY-5590) Document optional modifyThreadGroup permssion in java 2 security permissions

Posted by "Kathey Marsden (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kathey Marsden updated DERBY-5590:
----------------------------------

    Affects Version/s: 10.9.0.0
    
> 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: 10.9.0.0
>            Reporter: Kathey Marsden
>
> 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

        

[jira] [Commented] (DERBY-5590) Document optional modifyThreadGroup permssion in java 2 security permissions

Posted by "Rick Hillegas (JIRA)" <ji...@apache.org>.
    [ 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: 10.9.0.0
>            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

        

[jira] [Updated] (DERBY-5590) Document optional modifyThreadGroup permssion in java 2 security permissions

Posted by "Kim Haase (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kim Haase updated DERBY-5590:
-----------------------------

    Attachment: DERBY-5590.zip
                DERBY-5590.stat
                DERBY-5590.diff

Kathy, thank you for explaining this issue so clearly. I'm attaching DERBY-5590.diff, DERBY-5590.stat, and DERBY-5590.zip, with changes to the two files you mentioned:

M       src/devguide/cdevbabejgjd.dita
M       src/ref/rrefproperextdiagsevlevel.dita

Please let me know whether further changes are needed.
                
> 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: 10.9.0.0
>            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

        

[jira] [Assigned] (DERBY-5590) Document optional modifyThreadGroup permssion in java 2 security permissions

Posted by "Kim Haase (Assigned) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kim Haase reassigned DERBY-5590:
--------------------------------

    Assignee: Kim Haase
    
> 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: 10.9.0.0
>            Reporter: Kathey Marsden
>            Assignee: Kim Haase
>
> 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

        

[jira] [Closed] (DERBY-5590) Document optional modifyThreadGroup permssion in java 2 security permissions

Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kim Haase closed DERBY-5590.
----------------------------


Changes have appeared in Latest Alpha Manuals.
                
> 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: 10.9.1.0
>            Reporter: Kathey Marsden
>            Assignee: Kim Haase
>             Fix For: 10.9.1.0
>
>         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

        

[jira] [Updated] (DERBY-5590) Document optional modifyThreadGroup permssion in java 2 security permissions

Posted by "Kim Haase (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kim Haase updated DERBY-5590:
-----------------------------

    Issue & fix info: Patch Available
    
> 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: 10.9.0.0
>            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

        

[jira] [Resolved] (DERBY-5590) Document optional modifyThreadGroup permssion in java 2 security permissions

Posted by "Kim Haase (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/DERBY-5590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kim Haase resolved DERBY-5590.
------------------------------

          Resolution: Fixed
       Fix Version/s: 10.9.0.0
    Issue & fix info:   (was: Patch Available)

Thanks very much, Rick.

Committed patch DERBY-5590.diff to documentation trunk at revision 1341573. 
                
> 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: 10.9.0.0
>            Reporter: Kathey Marsden
>            Assignee: Kim Haase
>             Fix For: 10.9.0.0
>
>         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