db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erlend Birkenes (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-3618) Perform thread dump with ASSERTS with jdk 1.5 or higher
Date Sat, 19 Jul 2008 02:51:33 GMT

     [ https://issues.apache.org/jira/browse/DERBY-3618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Erlend Birkenes updated DERBY-3618:

    Attachment: DERBY-3618_6.diff

Version 6.

- Fixed it so ASSERT message always prints, as it indeed was meant to, but I had missed it.
- Added permissions to derby_tests.policy to derby.jar and derbyclient.jar to have permissions
to dump threads.
- Removed setIO prom the policies. That was leftovers from the first test.
- Given permissions to derby.jar and derbyclient.jar instead of all in the test policy. That
worked fine. Thanks for the tip :)

-Unfortunately the exception stack trace has to come after the thread dump when we do it this
way, as the message can only be set in the constructor, the super constructor has to be called
first, and non-static methods can't be called in it so we can't get to the stack trace until
after the superconstructor. I tried everything to get it into the message, but I don't think
it can be done.

> 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
>         Attachments: DERBY-3618_1.diff, DERBY-3618_2.diff, DERBY-3618_3.diff, DERBY-3618_4.diff,
DERBY-3618_5.diff, DERBY-3618_6.diff
> 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