Uploaded image for project: 'Derby'
  1. Derby
  2. DERBY-2978 Replication: Add slave replication mode
  3. DERBY-3184

Replication: Connection attempts to a database in slave mode must fail

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 10.4.1.3
    • 10.4.1.3
    • Services
    • None

    Description

      When a database 'X' is booted in slave mode, the call to Monitor.startPersistentService("X",...) will not complete because the call gets stuck in LogToFile#recover. This is intentional.

      For as long as startPersistentService is blocked, however, other threads that try to connect to 'X' (effectively calling Monitor.findService("X", ...)) will also hang. This is unacceptable, and needs to raise an error.

      Attachments

        1. derby-3184-1.diff
          16 kB
          Jorgen Loland
        2. derby-3184-1.stat
          1 kB
          Jorgen Loland
        3. derby-3184-bugfix-1a.stat
          0.5 kB
          Jorgen Loland
        4. derby-3184-bugfix-1a.diff
          9 kB
          Jorgen Loland
        5. derby-3184-2a.stat
          0.3 kB
          Jorgen Loland
        6. derby-3184-2a.diff
          15 kB
          Jorgen Loland
        7. derby-3184-2b.diff
          18 kB
          Jorgen Loland
        8. derby-3184-2b.stat
          0.4 kB
          Jorgen Loland
        9. derby-3184-2c.diff
          18 kB
          Jorgen Loland
        10. derby-3184-3a.diff
          13 kB
          Jorgen Loland
        11. derby-3184-3a.stat
          0.6 kB
          Jorgen Loland
        12. derby-3184-3b.diff
          12 kB
          Jorgen Loland

        Issue Links

          Activity

            People

              jorgenlo Jorgen Loland
              jorgenlo Jorgen Loland
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: