Why are my kahaDB log files not being removed?

Solution Verified - Updated -

Issue

When using the kahaDB message store you may notice a build up of kahaDB log files which never seem to get removed. This may cause the broker to reach it's store limit and trigger producer flow control if enabled or in other cases it may deplete disk space.

Environment

  • Fuse Message Broker
  • Fuse Message Broker Enterprise
  • Red Hat A-MQ 6.1
  • Red Hat JBoss Fuse 6.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In