[
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_3.diff
Ok, It took me a while, but here is version 3.
I added a jUnit test in
org.apache.derbyTesting.unitTests.junit.AssertFailureTest that tests that the
output produced by AssertFailure is correct in various situations.
i also changed the output a bit since last time so it looks better and is more
useful. It now always prints the AssertFailure stack trace first and then the
thread dump if we can get it, if not it prints the reason why we couldn't. This
still gets printed to derby.log if it is available or to System.out if not or
if verbose is on.
I struggled a bit with the permissions for the test, and I ended up with having
to give the necessary permissions to all (see
org.apache.derbyTesting.unitTests.junit.AssertFailureTest.policy) as this was
the only way I could get it to work in all situations, but I'm sure there is a
better way to do it. Let me know if you know how.
Also added the jUnit test to org.apache.derbyTesting.unitTests.junit._Suite.
Please comment.
> 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: 10.5.0.0
> Reporter: Kathey Marsden
> Assignee: Erlend Birkenes
> Priority: Minor
> Attachments: DERBY-3618_1.diff, DERBY-3618_2.diff, DERBY-3618_3.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.
