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 19:29:51 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-8.diff

Thanks, Knut. 
I attach patch DERBY-4715-8.diff with the same changes as last one and take out the space
for "Boot...."
This is what it looks like now. Please review it:
----------------------------------------------------------------
2010-07-21 18:43:02.968 GMT:
Booting Derby version The Apache Software Foundation - Apache Derby - 10.7.0.0 alp
stance a816c00e-0129-f650-e20c-000000c1b4f8
on database directory C:\derby\trunk\testtmp\test  with class loader sun.misc.Laun
r@11b86e7
Loaded from file:/C:/derby/trunk/jars/sane/derby.jar
java.vendor=Sun Microsystems Inc.
java.runtime.version=1.6.0_20-b02
Database Class Loader started - derby.database.classpath=''

2010-07-21 18:43:06.484 GMT:
Shutting down instance a816c00e-0129-f650-e20c-000000c1b4f8 with class loader sun.
lassLoader@11b86e7
----------------------------------------------------------------
The tests are still running. 

> 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: 10.6.1.0
>            Reporter: Lily Wei
>            Assignee: Lily Wei
>            Priority: Minor
>             Fix For: 10.7.0.0
>
>         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-4715-8.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.


Mime
View raw message