Problem Statement
If while creating a snapshot of a project with several issues, if the process is interrupted and then when attempt to take another snapshot the following error is thrown
Error Message
Job with name 'com.botronsoft.jira.rollout.snapshot' has already been scheduled.
Log Entries
ERROR user1 445x98019x1 116nnw6 10.251.86.81,10.80.80.8,10.53.49.80 /rest/configuration-manager/1.0/snapshots/progress/4 [c.b.j.r.impl.rest.AbstractResource] com.botronsoft.jira.rollout.jobs.JobAlreadyScheduledException: Job with name 'com.botronsoft.jira.rollout.snapshot' has already been scheduled java.util.concurrent.ExecutionException: com.botronsoft.jira.rollout.jobs.JobAlreadyScheduledException: Job with name 'com.botronsoft.jira.rollout.snapshot' has already been scheduled
Environment
| Application | Jira |
|---|---|
| Version | Server |
Cause
CMJ allows only one snapshot creation operation at a time. This means that before you attempt another one, you must wait for the currently running one to complete.
Solution
- To kill an ongoing process of snapshot creation, below are the two options.
- As the operation is still running in the background, wait for the previously started operation to complete. You can monitor CMJ's Audit Log for a message that suggests that the snapshot is created.
- Rarely, the operation can get stuck because of a platform issue. In this case, the solution is to restart JIRA and create a new snapshot