[
https://issues.apache.org/jira/browse/DERBY-4588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamta A. Satoor updated DERBY-4588:
-----------------------------------
Fix Version/s: 10.5.3.1
> Provide a diagnostic property that will print a stack trace on successful
> boot to help diagnose dual boot issues after the DERBY-700 fix
> ----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-4588
> URL: https://issues.apache.org/jira/browse/DERBY-4588
> Project: Derby
> Issue Type: Improvement
> Components: Services
> Affects Versions: 10.1.3.1, 10.2.2.0, 10.3.3.0, 10.5.3.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Fix For: 10.5.3.1
>
> Attachments: DERBY-4588_quickfix_diff.txt
>
>
> Now that DERBY-700 has been fixed, some users upgrading to the 1.6 JVM are
> seeing an error on dual boot where they did not before (which is of course is
> a very good thing). They do however at that time need to diagnose where the
> dual boot is coming from which is sometimes harder than one might think with
> a complex system and legacy code. It would be helpful to have a property
> that they could set which would print a stack trace on any boot attempt, even
> if successful, to help diagnose the application error, maybe:
> derby.stream.error.logBootTrace=true
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
