Derby
  1. Derby
  2. DERBY-2814

Specifying derby.* properties used in default policy file in derby.properties does not work

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 10.3.1.4
    • Fix Version/s: 10.3.1.4
    • Component/s: Network Server
    • Labels:
      None
    • Bug behavior facts:
      Regression, Security

      Description

      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.

      1. script-2.sh
        2 kB
        Dag H. Wanvik
      2. script.sh
        2 kB
        Dag H. Wanvik

        Issue Links

          Activity

          Hide
          Myrna van Lunteren added a comment -

          As this is fixed by 2811, assigning same person.

          Show
          Myrna van Lunteren added a comment - As this is fixed by 2811, assigning same person.
          Hide
          Daniel John Debrunner added a comment -

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

          Show
          Daniel John Debrunner added a comment - 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."
          Hide
          Dag H. Wanvik added a comment -

          Ran manual tests verifying that the patch for DERBY-2811 fixes this. Closing.

          Show
          Dag H. Wanvik added a comment - Ran manual tests verifying that the patch for DERBY-2811 fixes this. Closing.
          Hide
          Rick Hillegas added a comment -

          I think that this is addressed by the patch for DERBY-2811.

          Show
          Rick Hillegas added a comment - I think that this is addressed by the patch for DERBY-2811 .
          Hide
          Rick Hillegas added a comment -

          Hi Dag, I think that the patch attached to DERBY-2811 addresses this issue also. Could you test-drive it? Thanks!

          Show
          Rick Hillegas added a comment - Hi Dag, I think that the patch attached to DERBY-2811 addresses this issue also. Could you test-drive it? Thanks!

            People

            • Assignee:
              Rick Hillegas
              Reporter:
              Dag H. Wanvik
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development