I was using the Mongo JobStore with Quartz Scheduler in one of our Spring Boot Maven based project.
With both Simple Jobs or Cron jobs,
On api request details saving to quartz_triggers collection and the trigger state is WAITING. Once the trigger identified as next one to fire it's state should be ACQUIRED, on execution competition state should be COMPLETED, Which is not happening.
With Simple Jobs -> On execution competition, trigger related document is removed from collection.
With Simple Jobs with repetition or Cron Jobs -> Always state is WAITING. There is no fired_triggers collection atleast to track the status of each fire.
Why the trigger state in DB is always WAITING and not updating?
And is the library is ready to be used in enterprise applications or still work going on. Based on your response we can decide to proceed with same library or SQL based JobStore.
I was using the Mongo JobStore with Quartz Scheduler in one of our Spring Boot Maven based project.
With both Simple Jobs or Cron jobs,
On api request details saving to quartz_triggers collection and the trigger state is WAITING. Once the trigger identified as next one to fire it's state should be ACQUIRED, on execution competition state should be COMPLETED, Which is not happening.
With Simple Jobs -> On execution competition, trigger related document is removed from collection.
With Simple Jobs with repetition or Cron Jobs -> Always state is WAITING. There is no fired_triggers collection atleast to track the status of each fire.
Why the trigger state in DB is always WAITING and not updating?
And is the library is ready to be used in enterprise applications or still work going on. Based on your response we can decide to proceed with same library or SQL based JobStore.
Please guide me in this scenario, will be helpful