You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 25, 2024. It is now read-only.
I'm running 2 batch application with different set of Jobs using the same Mongo-DB collections. The Trigger key & group names are different for these application Jobs. The issue is that application - A is trying to acquire the trigger lock from application - B and trying to execute the JOB from application - B which doesn't know about the application B Job detail.
Please advise. I don't want to create new set of collections for each batch applications.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm running 2 batch application with different set of Jobs using the same Mongo-DB collections. The Trigger key & group names are different for these application Jobs. The issue is that application - A is trying to acquire the trigger lock from application - B and trying to execute the JOB from application - B which doesn't know about the application B Job detail.
Please advise. I don't want to create new set of collections for each batch applications.
The text was updated successfully, but these errors were encountered: