Details
-
Bug
-
Resolution: Can't Do
-
Major
-
None
-
JBoss A-MQ 6.3
-
None
-
Compatibility/Configuration, User Experience
Description
I'm sorry, but I can't report this bug in the right Jira project ENTMQ, because it effects all JBoss A-MQ 6.3.0 versions.
Running JBoss A-MQ 5.11.0.redhat-630187 in a "HA-failover" setup with JDBC store. Below is the TRACE logging [1] from the gc for the kahadb that the scheduler items reside in. There are no references to after dest as mentioned in http://activemq.apache.org/why-do-kahadb-log-files-remain-after-cleanup.html so it's quite hard to determine what's causing the db not to be cleaned up. All my queues are currently empty.
Questions:
- How can I force a cleanup on a kahaDB?
- How can I get more information (either on JMX or the web UI) on what's blocked in scheduler?
- How can I setup a real kahadb setting for the scheduler items?
- Is there a potential bug I'm encountering?
Log attached.
