Bug 778963 (SOA-1393)

Summary: Document how to cleanup JMXDATA table
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: Aaron Pestel <ammppp>
Component: Documentation, JBossESB, Monitoring and Management, JONAssignee: nwallace <nwallace>
Status: CLOSED WONTFIX QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 4.3 GA   
Target Milestone: ---   
Target Release: FUTURE   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1393
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
SOA-P 4.3
Last Closed: 2011-11-01 20:14:54 UTC Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Aaron Pestel 2009-07-02 03:37:22 UTC 
project_key: SOA

We have good documentation about the monitoring and management ESB console here:  http://www.redhat.com/docs/en-US/JBoss_SOA_Platform/4.3.CP01/html-single/Administration_Guide/index.html#monit_and_manage_console

However, one thing we don't document is how to cleanup the JMXDATA table.  This table can grow very large when nothing is even happening on the ESB since the ESB management console is constantly polling for metrics.

Requesting that we document how users can keep this table to a reasonable size.