db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6680) Other jar files may need to be granted permission to read derby.ui.* properties
Date Mon, 18 Aug 2014 20:57:18 GMT

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

Myrna van Lunteren commented on DERBY-6680:

I admit, I always use the same classpath for all setups myself also.

And you're right about sysinfo/derbytools.jar use, and extra warnings are good, so +1 to your

Thanks for picking this up.

> Other jar files may need to be granted permission to read derby.ui.* properties
> -------------------------------------------------------------------------------
>                 Key: DERBY-6680
>                 URL: https://issues.apache.org/jira/browse/DERBY-6680
>             Project: Derby
>          Issue Type: Bug
>    Affects Versions:
>            Reporter: Rick Hillegas
>            Assignee: Dag H. Wanvik
>         Attachments: derby-6680.diff
> The following properties may be read by LocalizedResource, a class which is included
in derby.jar, derbynet.jar, derbyclient.jar, and derbytools.jar:
> {noformat}
> derby.ui.codeset
> derby.ui.locale
> {noformat}
> A user has tripped across this problem in production. With the user's language settings,
the network server fails to come up because the server policy file does not grant the server
permission to read these properties. See http://apache-database.10148.n7.nabble.com/Hellow-I-have-some-problem-in-customize-security-policy-with-derby-modified-3-td141002.html
> We should adjust server.policy and template.policy accordingly.

This message was sent by Atlassian JIRA

View raw message