Java Management Extension (JMX) Interface
The JMX interface allows System Administrators to use a simple
Web interface to the various Java Management Extension management beans in the
system.
Titania Delivery provides three Management Beans, or MBeans.
- ContentEngineInspector
- This bean can be used to inspect the current status of the Content Engine, if it is
included in the Web tier. (If using a standalone Content Engine, this bean appears
on the
Content Engine's embedded Web console, and will not have any data here.)
- ActiveEvents
- The JSON presentation of the events work currently being done.
- ActiveNotifications
- The notifications being dealt with at the current time.
- EventCount
- The total number of events handled since the system started up.
- EventsByType
- A JSON object containing the number of events of each type handled by Content Engine since it started up.
- NotificationCount
- The total number of notifications handled by the system since it started up.
- NotificationsByType
- A JSON object containing the number of notifications of each type handled by the system since it started up.
- PortalRenderingInspector
- Displays information about the active XSLT transformations currently being processed
by
the system for Portal display. This can be used to track down potential "hanging"
XSLT
stylesheets that can cause the system to lock up.
- ActiveRenders
- The currently-running renderings.
- RenderCount
- The number of XSLT renderings that have been performed since system start-up.
- QueueInspector
- Displays information about the contents of the work queue.
- ClaimedEventsByClaimant
- Displays the events claimed by each Content Engine thread.
- EventProcessors
- The list of IDs of all Content Engine worker threads.
- QueueSize
- The number of events currently on the work queue.
- QueueSizeByType
- A JSON object dscribing the number of events of each type currently in the queue.
- clearQueue()
- This action will clear the contents of the work queue.
Warning: Use this with extreme caution. It effectively cancels all scheduled future processing.
There are additional management bean categories available through this interface. The following are management beans that may be of particular interest to Titania Delivery administrators:
- java.lang
- Contains management beans for the JVM itself. Of these, the Memory bean has an action called gc() that can be used to cause the JVM to initiate garbage collection.
- net.sf.ehcache
- This category contains beans that can be used to monitor the status of the various in-memory caches used by Titania Delivery.