Right, but the JMX "JobScheduler" MBean shows no jobs at all (the 'AllJobs' attribute is empty). It also shows NextScheduleTime=1970-01-01 00:59:59.
Turning on tracing, it shows: 2015-10-22 12:33:18,502 | TRACE | heckpoint Worker | JobSchedulerStoreImpl | 105 - org.apache.activemq.activemq-osgi - 5.11.2 | A remove in log 1 has an add still in existance. 2015-10-22 12:33:18,503 | TRACE | heckpoint Worker | JobSchedulerStoreImpl | 105 - org.apache.activemq.activemq-osgi - 5.11.2 | A remove in log 2 has an add still in existance. ..... for lots more log xxx .... The redelivery plugin very very rarely comes into action, so I still don't understand why there's all this data being stored. On 22.10.2015 15:47, Timothy Bish wrote:
On 10/22/2015 04:46 AM, Martin Lichtin wrote:Can you help me understand what is stored in the "scheduler" directory? I see about 14G of db-xxx.log files sitting there. All queues are empty and also the kahadb directory contains just one db-nnn.log file. schedulerSupport is enabled only due to use of the redelivery plugin. I'm pretty puzzled to see two directories ("kahadb" and "scheduler") containing message db files, with the latter one filling up.The scheduler is a KahaDB based store that is used to hold and manage the scheduled messages for the broker. If you are using the broker side redelivery plugin then there could be messages store in the scheduler. You can use the JMX MBean to query what is contained in the scheduler.
