Timer do not restart after app server restart

XMLWordPrintable

    • Type: Bug Report
    • Resolution: Won't Fix
    • Priority: L3 - Default
    • None
    • Affects Version/s: 7.9.0
    • Component/s: None
    • None
    • Environment:
      Camunda on Docker and PostgreSQL. Base OS is CentOS.

      Also possible to replicate on standalone Camunda-Tomcat with PostgresSQL.

      If I start the attached BPMN file (e.g. using the REST API), I have one process instance generating log messages with the current time in milliseconds. These messages occur roughly once a minute. This is expected.

      If I shut down Camunda (e.g. docker-compose stop) and restart Camunda (e.g. docker-compose up), the process instance is still visible in Camunda Cockpit, but the timer does not continue to fire.

      Is this intended?

      Thanks

            Assignee:
            Unassigned
            Reporter:
            Albert Lai
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: