Troubleshooting with JMX Console

Several classes within the JMX Console display useful information for troubleshooting, particularly if you have clustered application or mediation servers. Here are the classes:

service=ClusterPrimaryDesignator -- Valuable to see if all hosts are connected to the cluster, and several other application server properties. Attributes like currentView show the active application servers. This class provides additional information about the cluster that can help with diagnosing initial configuration problems.

service=JMSMBEAN -- Supplies JMS information.

service=LoadedRuleExecMBEAN --This MBean provides Async execution of rules on this server. It can display loaded rule information, among other things.

Service=MedServerTrackerMBean -- Select java.lang.String.listAgentContents(). Part of the results return the mediation server partitions, listing the mediation servers included in that partition.

You can see active settings and possibly modify them by using the JMX console from a browser (see also JMX Console):

http://serverIP:8089/jmx-console

The default user/password is admin/dorado. Set a filter to oware:* for a more concise view of the relevant settings

Some settings require that a service is stopped and restarted for the setting to take effect. Only changes made to server/conf files on disk will take effect after a restart.

• See NotificationProcessingMBean for event processing settings

• See OWSysLogMBean for syslog listener queue and archive settings

Here are some examples of exposed service settings for Event Management:

<!--

| NotificationProcessingMBean

-->

<mbean code="com.dorado.assure.mediation.NotificationProcessingMBean"

name="oware:service=NotificationProcessingMBean">

<attribute name="TransportBatchSize">2000</attribute> <!--# events-->

<attribute name="TransportBatchInterval">500</attribute> <!--#

milliseconds-->

<attribute name="ServerRetryInterval">5</attribute> <!--# seconds-->

<attribute name="ServerRefreshInterval">30</attribute> <!--# seconds-->

<attribute name="SuppressUnknownSource">false</attribute>

<attribute name="SuppressInformational">false</attribute>

Setting SuppressUnknownSource to true rejects all event from unknown sources -- without historical event records. Setting SuppressInformational to true rejects all events that do not produce an alarm, correlation or automation (not necessarily just events of informational severity). Basically it suppresses events that are only inserted in history.

<attribute name="QueueBatchSize">1000</attribute> <!--# entries-->

<attribute name="QueueFileBufferSize">131072</attribute> <!--# bytes-->

<attribute name="QueueFileName">@OWARE_USER_ROOT@/owareapps/eventmgmt/temp/event_spool.

dat</attribute>

<attribute name="QueueMaxFileSize">20971520</attribute> <!--# bytes-->

<attribute name="QueueMaxSize">100000</attribute> <!--# entries-->

<depends>oware:service=HAServiceController</depends>

</mbean>

 

<!--

| SNMPListenerMBean

-->

<mbean code="com.dorado.assure.mediation.SNMPListenerMBean"

name="oware:service=EMSNMPListenerMBean">

<attribute name="V3AuthRefreshInterval">60</attribute> <!--# seconds-->

<depends>oware:service=NotificationProcessingMBean</depends>

</mbean>

 

<!--

| SysLogMBean

-->

<mbean code="com.dorado.assure.mediation.OWSysLogMBean"

name="oware:service=EMSysLogMBean">

<attribute name="SpoolZipLevel">1</attribute>

<attribute name="SpoolReset">true</attribute>

<attribute name="QueueLimit">50000</attribute>

<attribute name="QueueFetchPref">5000</attribute>

<attribute name="MaxQueueReadSize">50000</attribute>

<attribute name="SpoolFileName">syslog_spool.dat</attribute>

<attribute name="SpoolPath">@OWARE_USER_ROOT@/owareapps/eventmgmt/temp</attribute>

<attribute name="SpoolSize">5242880</attribute>

<attribute name="ArchiveMaxLength">52428800</attribute>

<attribute name="ArchiveEnabled">false</attribute>

<attribute name="ArchivePath">@OWARE_USER_ROOT@/owareapps/eventmgmt/archive</attribute>

<attribute name="ArchiveZip">true</attribute>

<depends>oware:service=NotificationProcessingMBean</depends>

</mbean>