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 "Kristian Waagan (JIRA)" <ji...@apache.org> on 2010/07/13 15:02:59 UTC
[jira] Updated: (DERBY-4598) Print class loader used to boot and
shutdown derby in derby.log
[ https://issues.apache.org/jira/browse/DERBY-4598?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kristian Waagan updated DERBY-4598:
-----------------------------------
Issue & fix info: (was: [Patch Available])
Cleared patch available flag.
Is the work on this issue completed?
> Print class loader used to boot and shutdown derby in derby.log
> ----------------------------------------------------------------
>
> Key: DERBY-4598
> URL: https://issues.apache.org/jira/browse/DERBY-4598
> Project: Derby
> Issue Type: Bug
> Components: Services
> Affects Versions: 10.5.3.0
> Reporter: Kathey Marsden
> Assignee: Kathey Marsden
> Priority: Minor
> Fix For: 10.3.3.1, 10.4.2.1, 10.5.3.1
>
> Attachments: DERBY-4598_withmasters_10.5_diff.txt, DERBY-4598_withmasters_diff.txt
>
>
> It would be good to print the class loader used to boot and shutdown derby. When using class loaders, it is important to use the same class loader when shutting down or it doesn't really shutdown at all. Doing this will make it easier to diagnose such problems. I think it is ok to just leave it as the normal behavior as it does not add too much bulk to the log.
> 2010-03-25 20:57:57.781 GMT:
> Booting Derby version The Apache Software Foundation - Apache Derby - 10.6.0.0 alpha - (927552M): instance a816c00e-012
> 7-971d-fe59-000000107bb8
> on database directory C:\kmarsden\repro\DERBY-4588\wombat with class loader sun.misc.Launcher$AppClassLoader@42ed42ed
> Database Class Loader started - derby.database.classpath=''
> 2010-03-25 20:58:10.109 GMT:
> Shutting down instance a816c00e-0127-971d-fe59-000000107bb8 with class loader sun.misc.Launcher$AppClassLoader@42ed42ed
> ----------------------------------------------------------------
> Note it is important to set derby.infolog.append=true or the different class loaders will clobber the log.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.