Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-2035

Setting the database class path takes effect for the current connection but not others until a database reboot.

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Incomplete
    • Affects Version/s: 10.2.1.6
    • Fix Version/s: None
    • Component/s: SQL
    • Labels:
      None

      Description

      After setting the derby.database.classpath as a database property the current connection sees its effects, such as being able to load classes from the jar added into the class path. However a newly opened connection does not see its effect. Shutting down and re-booting the database makes the change visible to all.

      The new test lang.DatabaseClassLoadingTest will have code that shows this bug commented with this bug number.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              djd Daniel John Debrunner
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: