Article - CS178198
commonScheduleQueue does not purge JMX performance tables in Windchill PDMLink
Modified: 21-Feb-2025
Applies To
- Windchill PDMLink 10.0 to 13.0
Description
- LogTableCleaner does not clean up JMX database logging tables
- JMX database logging tables are growing steadily
- Preftables export are of huge size
- For example, SAMPLEDMETHODCONTEXTS, CACHESTATISTICS, RAWSERVLETREQUESTSTATS have large number of rows and reaches to 15GB size
- How to verify the schedule to clean up
- How to purge huge size of tables:
MISCLOGEVENTS, SAMPLEDMETHODCONTEXTS, CACHESTATISTICS, RAWMETHODCONTEXTSTATS - Performance Tables exists properly
- Old entries are not purged after the defined maxAgeInDays as described in Article 44623
- No related error messages can be seen in Windchill (Background) Method Server logs
- Expected logging for one JMX database logging table with wt.method.jmx.LogTableCleaner:
INFO [commonScheduleQueue.SchedulingThread] wt.method.jmx.LogTableCleaner wcadmin - Purging data from <DB_table> ... INFO [commonScheduleQueue.SchedulingThread] wt.method.jmx.LogTableCleaner wcadmin - Purged <number> rows older than <timestamp> from <DB_table>
- To activate this logging, add the following line to <Windchill>\codebase\WEB-INF\log4jMethodServer.properties
- log4j.logger.wt.method.jmx.LogTableCleaner=ALL
This is a printer-friendly version of Article 178198 and may be out of date. For the latest version click CS178198