...

• Cleanup Tickets

• Tickets to be selected for a discussion in meetings

2024-02-14

• MooBench memory leak: Based on analysis of heap dumps, it seems like the RotatingLogFilePoolHandler caused the problem: https://github.com/kieker-monitoring/kieker/blob/371a9095a1bc212dbd422afdf831197bd50794cf/monitoring/src/kieker/monitoring/writer/filesystem/RotatingLogFilePoolHandler.java#L85 (We have ~5000 files in the ArrayList)

  • First solution: increase kieker.monitoring.writer.filesystem.FileWriter maxLogSize, maxEntriesInFile and decrease maxLogFiles for MooBench

  • Long-term solution: Change default parameters in Kieker (currently, we have only 25 000 entries in one file, resulting in files of ~1.5 MB): https://github.com/kieker-monitoring/kieker/blob/371a9095a1bc212dbd422afdf831197bd50794cf/monitoring/src-resources/META-INF/kieker.monitoring.default.properties#L338

• Overall architecture: Have one monitoring module with submodules monitoring-core and one module for each agent: monitoring-aspectj, monitoring-disl, monitoring-javassist, monitoring-bytebuddy

  • Each agent should be provided as individual jar

  • Only the required classes should be contained (no analysis classes)

• Java 11 PR problem: Was caused by a deprecated test → Removed and try again

• DiSL PR problem: Was caused by missing Kieker license header for DiSL → Changed and try again

2024-01-24

• MooBench

  • Is https://github.com/kieker-monitoring/moobench/tree/main/continuous-integration still relevant (or is this replaced by the Jenkinsfile)?

  • Would it make sense to migrate https://maui.se.informatik.uni-kiel.de/repo/moobench/ to github?

...