Uploaded image for project: 'OpenMRS Core'
  1. OpenMRS Core
  2. TRUNK-1637

Clarify what the startup error "Waiting for changelog lock...." means

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Non-Essential
    • Resolution: Fixed
    • Affects Version/s: OpenMRS 1.5.0, OpenMRS 1.5.1, OpenMRS 1.5.2, OpenMRS 1.5.3, OpenMRS 1.6.0, OpenMRS 1.6.1
    • Fix Version/s: OpenMRS 1.9.0, 1.9 Beta Sprint
    • Component/s: None
    • Labels:
    • Complexity:
      Medium

      Description

      Liquibase locks the database when updating. If openmrs or tomcat crashes while doing that, the lock remains. We need to either add a way to clean that up on crash, or at the very least provide a helpful message to users so they know how to fix it.

        Attachments

        1. capt.avi
          4.85 MB
          Taras Chorny
        2. crash_moment.png
          164 kB
          Taras Chorny
        3. run_app_after_crash.png
          127 kB
          Taras Chorny
        4. TRUNK-1637.patch
          23 kB
          Taras Chorny
        5. TRUNK-1637-root.patch
          23 kB
          Taras Chorny
        6. TRUNK-1637-WITH-2023-complex-NEW.patch
          42 kB
          Taras Chorny
        7. user1_clean_up_crash_on_browser1.png
          71 kB
          Taras Chorny
        8. user1_review_progress.png
          111 kB
          Taras Chorny
        9. user1_run_on_browser_2_(another_update).png
          136 kB
          Taras Chorny
        10. user2_logged_after_u1_run_updates.png
          98 kB
          Taras Chorny
        11. user2_review_progress_that_started_by_user_1.png
          138 kB
          Taras Chorny

          Activity

            People

            Assignee:
            cta Taras Chorny
            Reporter:
            bwolfe Ben Wolfe
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: