ETL jobs not running on schedule
Accepted answer
Hello,
under: https://<host>:9443/ccm/admin#action=com.ibm.team.repository.admin.configureAdvanced
you will find the properties:
The time interval in seconds between runs of this task. Please do not change).
under: https://<host>:9443/ccm/admin#action=com.ibm.team.repository.admin.configureAdvanced
you will find the properties:
The time interval in seconds between runs of this task. Please do not change).
Comments
Piotr,
Data Collection Jobs Enabled is set to true; Task Delay is set to 86400.
IsSnapshotEnabled set to true for all jobs.
Is there anything else I should check?
I would like to increase the verbosity of ETL logs (set it temporarily to TRACE or DEBUG) in order to guess why the CCM jobs don't run on schedule.
Which properties should I set in log4j.properties?
One other answer
Hello Luca,
as far as I know the data collection job execution is driven by JTS, as the jobs need to be executed in a specific sequence; so only JTS has the schedule setting.
From the description it sounds like a communication issue between JTS and CCM at the time the ETL is scheduled to start; might be worth having a look at the application logs for both.
Best Regards,
Francesco Chiossi
as far as I know the data collection job execution is driven by JTS, as the jobs need to be executed in a specific sequence; so only JTS has the schedule setting.
From the description it sounds like a communication issue between JTS and CCM at the time the ETL is scheduled to start; might be worth having a look at the application logs for both.
Best Regards,
Francesco Chiossi