db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lily Wei (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4715) Write jvm information and path of derby.jar to derby.log
Date Wed, 21 Jul 2010 15:49:49 GMT

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

Lily Wei updated DERBY-4715:

    Attachment: DERBY-4715-7.diff

Thank Knut for reviewing the patch.

"with class loader" comes straight after "on database directory (...)" now.
And, logMsg(jvmVersion) is after printed the boot message

I did not take out the space for "Booting ..." message. Should I go ahead and take it out?

I am running tests now.

This is the message on my screen, please review it:
2010-07-21 15:45:10.935 GMT:
 Booting Derby version The Apache Software Foundation - Apache Derby - al
pha - (965674M): instance a816c00e-0129-f5ae-0a4d-000000c1b4f8
on database directory C:\derby\trunk\testtmp\test2  with class loader sun.misc.Lau
Loaded from file:/C:/derby/trunk/jars/sane/derby.jar
java.vendor=Sun Microsystems Inc.
Database Class Loader started - derby.database.classpath=''

2010-07-21 15:45:14.145 GMT:
Shutting down instance a816c00e-0129-f5ae-0a4d-000000c1b4f8 with class loader sun.

> Write jvm information and path of derby.jar to derby.log
> --------------------------------------------------------
>                 Key: DERBY-4715
>                 URL: https://issues.apache.org/jira/browse/DERBY-4715
>             Project: Derby
>          Issue Type: Bug
>          Components: Miscellaneous
>    Affects Versions:
>            Reporter: Lily Wei
>            Assignee: Lily Wei
>            Priority: Minor
>             Fix For:
>         Attachments: DERBY-4715-1.diff, DERBY-4715-2.diff, DERBY-4715-3.diff, DERBY-4715-4.diff,
DERBY-4715-5.diff, DERBY-4715-6.diff, DERBY-4715-7.diff, derby.log
> The bug is part of DERBY-1272. In production environment, derby.jar can be located different
than the derbyclient.jar It can be easier if we have jvm version information and path of derby.jar
are in the derby.log

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message