[
https://issues.apache.org/jira/browse/DERBY-4715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12890614#action_12890614
]
Knut Anders Hatlen commented on DERBY-4715:
-------------------------------------------
Thanks Lily.
After the last patch, the message looks like this:
Booting Derby version The Apache Software Foundation - Apache Derby - 10.7.0.0
alpha - (1): instance a816c00e-0129-f436-4fd9-00000348e710
on database directory /tmp/db
Loaded from file:/code/derby/trunk0/classes/
java.vendor=Sun Microsystems Inc.
java.runtime.version=1.6.0_21-b06 with class loader
sun.misc.launcher$appclassloa...@17182c1
I think it would be better if the "with class loader" part came straight after
"on database directory (...)" and not on the java.runtime.version line.
Would it make sense to add an extra parameter for jvmVersion? It feels a bit
strange to have jvmVersion as a part of the JarClassPath parameter. Or perhaps
it's cleaner to move jvmVersion out of that message altogether, and instead add
a call to "logMsg(jvmVersion);" after having printed the boot message?
> 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.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.
