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 Mon, 09 Aug 2010 15:45:20 GMT

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

Lily Wei updated DERBY-4715:
----------------------------

    Fix Version/s: 10.5.3.1
                   10.6.1.1

Add fix version.

> 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.5.3.1, 10.6.1.1, 10.7.0.0
>
>         Attachments: DERBY-4715-1.diff, DERBY-4715-10.5_967304.diff, DERBY-4715-10.6_967304.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