Uploaded image for project: 'Spring XD'
  1. Spring XD
  2. XD-2323

Filejdbc jobs status shows "STARTED" even when job is complete

    Details

    • Type: Bug
    • Status: Done
    • Priority: Major
    • Resolution: Complete
    • Affects Version/s: 1.1 M1
    • Fix Version/s: 1.1 M1
    • Component/s: Batch
    • Labels:
      None
    • Story Points:
      3
    • Rank (Obsolete):
      45962
    • Sprint:
      Sprint 38

      Description

      SHA: 67473dc71332c0727516b6f3fd11a55561b2472e
      Deployment: 1 Admin, 2 Containers
      JobStore: HSQLDB
      OS: Mac OSX & Ubuntu
      Reproducible: Yes
      Job: job create foo --definition "filejdbc --resources=file:filejdbctest/filejdbctest.out --names=data --tableName=filejdbctest --initializeDatabase=true "--deploy

      When using Rabbit as a transport with more than one container and launching the job above. The Job execution stays as "STARTED" status, even though the job is actually finished. We expect it to reach a state of "COMPLETED". Using Redis as a transport the job execution status does reach "COMPLETED".

      The execution step list shows:
      Id Step Name Job Exec ID Start Time End Time Status
      – ----------------------- ----------- ----------------------- ----------------------- ---------
      8 step1-master 4 2014-11-06 15:28:29,820 STARTED
      9 step1-master:partition0 4 2014-11-06 15:28:29,854 2014-11-06 15:28:29,890 COMPLETED

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                grussell Gary Russell
                Reporter:
                grenfro Glenn Renfro
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: