db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Commented: (DERBY-3618) Perform thread dump with ASSERTS with jdk 1.5 or higher
Date Wed, 30 Apr 2008 16:54:55 GMT

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

Kathey Marsden commented on DERBY-3618:

A couple of things to consider when working on this issue ...
1) This will require more permissons in the testing policy file for derby.jar. It would be
nice if they could be added just for sane builds but I don't think that is possible.

The two permissions that will be needed to dump the thread stack traces are:
permission java.lang.RuntimePermission "getStackTrace";
permission java.lang.RuntimePermission "modifyThreadGroup";

The change should be as such that if these permissions are not present it will just skip the
thread dump.

2) Testing might be tricky, since we don't really have JUnit unit testing for internal methods.
Maybe it will be easy enough to add if the methods are public. Also the output goes to derby.log
which is hard to check. We may just have to settle for manual testing.

> Perform thread dump with ASSERTS with jdk 1.5 or higher
> -------------------------------------------------------
>                 Key: DERBY-3618
>                 URL: https://issues.apache.org/jira/browse/DERBY-3618
>             Project: Derby
>          Issue Type: Improvement
>          Components: Services
>    Affects Versions:
>            Reporter: Kathey Marsden
>            Assignee: Erlend Birkenes
>            Priority: Minor
> It would be good to have a stack traces for all threads dump to the derby.log when an
assertion occurs with JVM's that support it.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message