Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Message-ID: <14215061.179451278098269657.JavaMail.jira@thor>
Date: Fri, 2 Jul 2010 15:17:49 -0400 (EDT)
From: "Kathey Marsden (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Subject: [jira] Commented: (DERBY-4715) Wrie jvm information and path of
 derby.jar to derby.log
In-Reply-To: <11111040.60211277480930634.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/DERBY-4715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12884786#action_12884786 ] 

Kathey Marsden commented on DERBY-4715:
---------------------------------------

Hi Lily,

Could you make sure something reasonable happens if there is no permission in the policy file for reading the system properties, getting the source location etc.   We should still boot and communicate that there is not sufficient permission to report the information  but not in an alarming way.
 

> 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.