Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-5481

Job execution threads keep executing exclusive follow-up jobs although the job executor has been shut down

    XMLWordPrintable

Details

    • Bug Report
    • Resolution: Fixed
    • L3 - Default
    • 7.5.0, 7.5.0-alpha3
    • None
    • engine
    • None

    Description

      Trying to shut down JobExecutor does not work well when new timer tasks are created within the next job executor job check. Basically new jobs are added to currentProcessorJobQueue in ExecuteJobsRunnable.run(), so shutdown does not happen.

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          1. catalina.2016-02-22.log
            1.53 MB
            Thomas Skjolberg
          3. jobexecutor.war
            4.22 MB
            Thomas Skjolberg
          4. recurring.bpmn
            3 kB
            Thomas Skjolberg
          5. recurring.png
            6 kB
            Thomas Skjolberg

          Issue Links

            is related to

            Bug Report - A problem which impairs or prevents the functions of the product. CAM-5506 Job execution continues even though the corresponding process application is undeployed

            • L3 - Default - Minor issue or issue with existing workaround, feature requests and questions
            • Open

            Bug Report - A problem which impairs or prevents the functions of the product. CAM-5505 Shutting down Tomcat (+ BPM platform), the job execution thread pool is not gracefully shut down

            • L3 - Default - Minor issue or issue with existing workaround, feature requests and questions
            • Closed
            links to

            Web Link https://github.com/camunda/camunda-bpm-platform/issues/2076

            Activity

              People

                thorben.lindhauer Thorben Lindhauer
                skjolber Thomas Skjolberg
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Salesforce