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 (JIRA)" <ji...@apache.org> on 2010/03/17 18:02:27 UTC
[jira] Created: (DERBY-4588) Provide a diagnostic property that
will print a stack trace on successful boot to help diagnose dual boot
issues after the DERBY-700 fix
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.5.3.0, 10.3.3.0, 10.2.2.0, 10.1.3.1
Reporter: Kathey Marsden
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.
[jira] Updated: (DERBY-4588) Provide a diagnostic property that
will print a stack trace on successful boot to help diagnose dual boot
issues after the DERBY-700 fix
Posted by "Mamta A. Satoor (JIRA)" <ji...@apache.org>.
[ 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.4.2.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.4.2.1, 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.
[jira] Updated: (DERBY-4588) Provide a diagnostic property that
will print a stack trace on successful boot to help diagnose dual boot
issues after the DERBY-700 fix
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-4588:
----------------------------------
Comment: was deleted
(was: Here is a patch for this issue. It prints the class loader on boot of Derby, on shutdown of Derby and on boot error XJ040.
I think it would also be useful to add on boot database and shutdown of database, but those are not part of this patch. I have not run tests.
)
> 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
>
> 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.
[jira] Updated: (DERBY-4588) Provide a diagnostic property that
will print a stack trace on successful boot to help diagnose dual boot
issues after the DERBY-700 fix
Posted by "Mamta A. Satoor (JIRA)" <ji...@apache.org>.
[ 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.3.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.3.3.1, 10.4.2.1, 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.
[jira] Updated: (DERBY-4588) Provide a diagnostic property that
will print a stack trace on successful boot to help diagnose dual boot
issues after the DERBY-700 fix
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-4588:
----------------------------------
Attachment: (was: DERBY-4598_diff.txt)
> 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
>
> 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.
[jira] Assigned: (DERBY-4588) Provide a diagnostic property that
will print a stack trace on successful boot to help diagnose dual boot
issues after the DERBY-700 fix
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden reassigned DERBY-4588:
-------------------------------------
Assignee: Kathey Marsden
> 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
>
> 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.
[jira] Resolved: (DERBY-4588) Provide a diagnostic property that
will print a stack trace on successful boot to help diagnose dual boot
issues after the DERBY-700 fix
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden resolved DERBY-4588.
-----------------------------------
Resolution: Fixed
Resolving this issue. I will open up a separate doc issue and link it.
> 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.3.3.1, 10.4.2.1, 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.
[jira] Updated: (DERBY-4588) Provide a diagnostic property that
will print a stack trace on successful boot to help diagnose dual boot
issues after the DERBY-700 fix
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-4588:
----------------------------------
Attachment: DERBY-4598_diff.txt
Here is a patch for this issue. It prints the class loader on boot of Derby, on shutdown of Derby and on boot error XJ040.
I think it would also be useful to add on boot database and shutdown of database, but those are not part of this patch. I have not run tests.
> 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
> Attachments: DERBY-4598_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.
[jira] Updated: (DERBY-4588) Provide a diagnostic property that
will print a stack trace on successful boot to help diagnose dual boot
issues after the DERBY-700 fix
Posted by "Mamta A. Satoor (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (DERBY-4588) Provide a diagnostic property that
will print a stack trace on successful boot to help diagnose dual boot
issues after the DERBY-700 fix
Posted by "Kathey Marsden (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DERBY-4588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kathey Marsden updated DERBY-4588:
----------------------------------
Attachment: DERBY-4588_quickfix_diff.txt
Attached is a quick fix for this issue. I verified it basically works but have not run tests. A couple of things to note.
1) The "boot trace" and "shutdown trace" messages are not localized. I don't think derby.log entries need to be or do they?
2)I thought it would also be nice to print a stack trace on shutdown, so added that too, but left the property name at derby.stream.error.logBootTrace.
I have not run tests and will be out for a week, so if someone wants to pick this up, run tests, and get it committed that would be great.
Kathey
> 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
> 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.