Uploaded image for project: 'Red Hat Process Automation Manager'
  1. Red Hat Process Automation Manager
  2. RHPAM-1521

Syncing job executor with database stopped after temporary database unavailability

    XMLWordPrintable

Details

    • Bug
    • Status: Verified (View Workflow)
    • Major
    • Resolution: Done
    • 7.0.2.GA
    • 7.1.0.GA
    • jBPM Core
    • None
    • CR2
    • Hide

      1. enable auto reconnect for jBPM data source on JBoss server eg. background-validation
      2. configure job executor to do synchronization with a database org.kie.executor.interval > 0
      3. start kie-server
      4. wait until job executor starts to sync with database - log entries "Load of jobs from storage started/finished" appear
      5. shutdown database - an exception should be written into log
      6. startup database
      7. job executor doesn't work - log entries "Load of jobs from storage started/finished" don't appear

      Show
      1. enable auto reconnect for jBPM data source on JBoss server eg. background-validation 2. configure job executor to do synchronization with a database org.kie.executor.interval > 0 3. start kie-server 4. wait until job executor starts to sync with database - log entries "Load of jobs from storage started/finished" appear 5. shutdown database - an exception should be written into log 6. startup database 7. job executor doesn't work - log entries "Load of jobs from storage started/finished" don't appear
    • 2018 Week 36-38

    Description

      I tested my system how it behaves when a database is temporarily unavailable. My JBoss EAP data sources are configured to auto-reconnect. As I expected processes that were running at the time of database breakdown ended with errors. After a few seconds when the database was back available I could run new processes with success but I noticed that job executor stopped to sync with the database. I have property org.kie.executor.interval set to 10 to sync job executor between nodes. After a short research, I found out that LoadAndScheduleRequestsTask doesn’t handle exceptions so when an exception is thrown ScheduledThreadPoolExecutor by design stops executing periodic tasks.

      Attachments

        Issue Links

          Activity

            People

              swiderski.maciej Maciej Swiderski (Inactive)
              dariusz.uzar Dariusz Uzar (Inactive)
              Marian Macik Marian Macik
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: