[
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-2.diff
Thanks to Kathey. DERBY-4715-2.diff patch will boot and communicate there is
not sufficient permission to derby.log for derby.jar. If there is no permission
for print out java.runtime.version or java.fullversion, there will only print
java vendor information to derby.log
Suites.all test is passed. It is running derbyall test suite. Please review the
patch
> 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-4715-2.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.
