Problem Statement
| Info |
|---|
| If while While creating a snapshot of a project with several issues, if the process is interrupted and then when an attempt to take another snapshot is made, the following below error is thrown thrown: |
Error Message
| Code Block | ||
|---|---|---|
| ||
Job with name 'com.botronsofttest.jira.rollout.snapshot' has already been scheduled. (This message is an example) |
Log Entries
| Code Block | ||
|---|---|---|
| ||
ERROR user1user1234 445x98019x1xxxxxxxxx 116nnw6xxxxxxxxxxx 10.2510.861.811,10.800.801.82,10.530.491.803 /rest/configuration-manager/1.0/snapshots/progress/4 [c.b.j.r.impl.rest.AbstractResource] com.botronsofttest.jira.rollout.jobs.JobAlreadyScheduledException: Job with name 'com.botronsofttest.jira.rollout.snapshot' has already been scheduled java.util.concurrent.ExecutionException: com.botronsofttest.jira.rollout.jobs.JobAlreadyScheduledException: Job with name 'com.botronsofttest.jira.rollout.snapshot' has already been scheduled |
Environment
| Application | Jira | Version | App Version | Database Type |
|---|
Cause
...
| Host | Datacenter |
|---|
Cause
CMJ allows for only one snapshot
...
to be created at a time. This means that before you attempt another one, you
...
should wait for the
...
current one to complete.
Solution
To
...
create a new snapshot:
- When an operation is running in the background, wait for the previously started operation to
...
- be completed. You can monitor this in the CMJ's Audit
...
- log for a message that suggests
...
- the snapshot
...
- is created. Please refer to Audit Logging for more details.
To stop the process of snapshot creation:
- Rarely can the operation get stuck because of
...
- an unexpected issue with the platform
...
- . To stop the process anyway, the solution is to restart JIRA and create a new snapshot
...
- .