[
https://issues.apache.org/jira/browse/DERBY-6680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14105461#comment-14105461
]
Knut Anders Hatlen commented on DERBY-6680:
-------------------------------------------
It looks to me as if LocalizedResource needs read permission on the derby.ui.*
properties only if its constructor is called with null for encoding or locale.
We could make NetworkServerControlImpl read those properties itself (using
PropertyUtil.getSystemProperty(), like it does when it reads other system
properties) and pass non-null values to the constructor. That might help avoid
this problem.
> 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: 10.11.1.1
> Reporter: Rick Hillegas
> Assignee: Dag H. Wanvik
> Fix For: 10.11.1.2, 10.12.0.0
>
> Attachments: derby-6680.diff, derby-6680b.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
(v6.2#6252)
