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 "Lily Wei (JIRA)" <ji...@apache.org> on 2010/07/02 06:48:49 UTC
[jira] Updated: (DERBY-4715) Wrie jvm information and path of
derby.jar to derby.log
[ 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-1.diff
derby.log
Write java vendor, java runtime version and java fullversion, the path of derby.jar to derby.log. Please review regarding:
1. Does the output looks okay?
2. Whether this will create too long of output for derby.log in general.
Here is a sample of how derby.log looks now:
2010-07-01 21:38:01.173 GMT:
Booting Derby version The Apache Software Foundation - Apache Derby - 10.7.0.0 al
pha - (959745M): instance a816c00e-0129-8ff1-e2bd-000000132a78
on database directory sun.misc.Launcher$AppClassLoader@69ba69ba with class loader
C:\derby\trunk\testtmp\test
Loaded from C:\derby\trunk\jars\sane\derby.jar
java.vendor=IBM Corporation java.runtime.version=pwi32dev-20090707 (SR10 ) J2RE 1.
5.0 IBM J9 2.3 Windows Vista x86-32 j9vmwi3223-20090707 (JIT enabled)
J9VM - 20090706_38445_lHdSMr
JIT - 20090623_1334_r8
GC - 200906_09java.fullversion=J2RE 1.5.0 IBM J9 2.3 Windows Vista x86-32 j9vmwi
3223-20090707 (JIT enabled)
J9VM - 20090706_38445_lHdSMr
JIT - 20090623_1334_r8
GC - 200906_09
^M
Database Class Loader started - derby.database.classpath=''^M
> Wrie 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.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.