Bug 778963 (SOA-1393) - Document how to cleanup JMXDATA table
Summary: Document how to cleanup JMXDATA table
Keywords:
Status: CLOSED WONTFIX
Alias: SOA-1393
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: Documentation, JBossESB, Monitoring and Management, JON
Version: 4.3 GA
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: FUTURE
Assignee: nwallace
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-07-02 03:37 UTC by Aaron Pestel
Modified: 2011-11-01 20:14 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
SOA-P 4.3
Last Closed: 2011-11-01 20:14:54 UTC
Type: Feature Request

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-1393 0 None None None Never

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.
Note You need to log in before you can comment on or make changes to this bug.