@Internal public class DefaultSchedulerRunDetailsManager extends Object implements SchedulerRunDetailsManager
SchedulerRunDetailsManager
interface.
It mostly delegates the work to the InternalRunDetailsDao
object.ALL_JOBS_TTL_MILLIS, UNSUCCESSFUL_JOBS_TTL_MILLIS
Constructor and Description |
---|
DefaultSchedulerRunDetailsManager(InternalRunDetailsDao internalRunDetailsDao,
com.atlassian.scheduler.SchedulerService schedulerService) |
Modifier and Type | Method and Description |
---|---|
com.atlassian.scheduler.status.RunDetails |
addRunDetails(com.atlassian.scheduler.config.JobId jobId,
Date startedAt,
com.atlassian.scheduler.status.RunOutcome runOutcome,
String message)
Delegates the task to the underlying Scheduler Service since the ConfluenceSchedulerService bean is not accessible from the add-on
|
long |
count(com.atlassian.scheduler.config.JobId jobId,
long timeToLiveThreshold,
com.atlassian.scheduler.status.RunOutcome runOutcome)
Count the job's run details that are stored before a time-to-live threshold in milliseconds
|
org.apache.commons.lang3.tuple.Pair<Integer,Integer> |
purgeOldRunDetails()
This method purges the old run details, i.e.
|
public DefaultSchedulerRunDetailsManager(InternalRunDetailsDao internalRunDetailsDao, com.atlassian.scheduler.SchedulerService schedulerService)
public org.apache.commons.lang3.tuple.Pair<Integer,Integer> purgeOldRunDetails()
SchedulerRunDetailsManager
or DefaultSchedulerRunDetailsManager#UNSUCCESSFUL_JOBS_TTL_MILLIS
This prevents the table space from growing without bounds, and it is unlikely that you really
care about the results of a scheduled job that hasn't run in that long, anyway.purgeOldRunDetails
in interface SchedulerRunDetailsManager
public long count(com.atlassian.scheduler.config.JobId jobId, long timeToLiveThreshold, com.atlassian.scheduler.status.RunOutcome runOutcome)
SchedulerRunDetailsManager
count
in interface SchedulerRunDetailsManager
timeToLiveThreshold
- the TTL thresholdrunOutcome
- the run outcome that should be matchedpublic com.atlassian.scheduler.status.RunDetails addRunDetails(com.atlassian.scheduler.config.JobId jobId, Date startedAt, com.atlassian.scheduler.status.RunOutcome runOutcome, @Nullable String message)
SchedulerRunDetailsManager
addRunDetails
in interface SchedulerRunDetailsManager
jobId
- the Job IDstartedAt
- when the job is startedrunOutcome
- the run outcomemessage
- the messageCopyright © 2003–2017 Atlassian. All rights reserved.