[
https://issues.apache.org/jira/browse/DERBY-6680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14106602#comment-14106602
]
Knut Anders Hatlen commented on DERBY-6680:
-------------------------------------------
Thanks, Dag!
There's also a call to LocalizedResource's constructor in processCommands(),
where codeset is always null. I think the patch changes that call from using
derby.ui.encoding (if it's set) to always using the default codeset of the JVM.
We might want to read the property there as well to keep the current behaviour.
> 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-2.diff, 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)
