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] Closed: (DERBY-4715) Write jvm information and path of derby.jar to derby.log
Date Thu, 05 Aug 2010 14:08:17 GMT

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

Lily Wei closed DERBY-4715.

    Bug behavior facts: [Seen in production]

Thanks, Kristian.

It makes my day to know that Hudson does not find any problems with my backport. I finally
know the build details on Hudson. That is so good to know. 

Myrna also told me about svn merge -c REV tip. I was using that do to this merge. I will close
this JIRA. It is more belong to additional information is needed category.

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

View raw message