[
https://issues.apache.org/jira/browse/DERBY-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel John Debrunner resolved DERBY-2814.
------------------------------------------
Resolution: Fixed
Fix Version/s: 10.3.0.0
Derby Info: [Regression] (was: [Existing Application Impact])
DERBY-2811 was fixed in 10.3.0.0 so this was too.
Also this was a regression, not existing application impact according to this
definition:
"Existing Application impact.An existing application can be impacted by
the *solution* to this issue."
> Specifying derby.* properties used in default policy file in derby.properties
> does not work
> -------------------------------------------------------------------------------------------
>
> Key: DERBY-2814
> URL: https://issues.apache.org/jira/browse/DERBY-2814
> Project: Derby
> Issue Type: Bug
> Components: Network Server, Security
> Affects Versions: 10.3.0.0
> Reporter: Dag H. Wanvik
> Fix For: 10.3.0.0
>
> Attachments: script-2.sh, script.sh
>
>
> When specifying properties referenced by the default policy file, for
> example derby.drda.host, in derby.properties instead of on the
> commandline (via the -h option or -D option to the VM), it seems the
> properties are not heeded, see repro scripts (script.sh and
> script-2.sh). This made the server come up not accepting connections
> from the host I had specified in the *.host property.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
