db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kim Haase (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4727) Document derby.stream.error.logBootTrace=true diagnostic property
Date Wed, 02 Feb 2011 22:59:29 GMT

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

Kim Haase updated DERBY-4727:

    Issue & fix info: [Patch Available]

> Document derby.stream.error.logBootTrace=true  diagnostic  property
> -------------------------------------------------------------------
>                 Key: DERBY-4727
>                 URL: https://issues.apache.org/jira/browse/DERBY-4727
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions:
>            Reporter: Kathey Marsden
>            Assignee: Kim Haase
>            Priority: Minor
>         Attachments: DERBY-4727.diff, DERBY-4727.stat, DERBY-4727.zip
> With the fix for DERBY-4588, the diagnostic property derby.stream.error.logBootTrace
can be used to diagnose dual boot issues.  Typically when two jvm's or class loaders attempt
to boot derby the error message below will appear:
> ERROR XJ040: Failed to start database 'testdb' with class loader sun.misc.Launch
> er$AppClassLoader@481e481e, see the next exception for details.
> ERROR XSDB6: Another instance of Derby may have already booted the database C:\derby\testdb
> and will show the stack trace and class loader of the failed boot attempt. It is sometimes
also useful to see the stack trace when the first successful boot attempt occured. To see
the stack trace of successful boots and shutdowns, set derby.stream.error.logBootTrace=true
to trace the successful attempt.  If you think that both attempts should be from the same
class loader context, check also the class loader information for boot and shutdown attempts
and make sure they all come from the same class loader context.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message