Resin 2.x server

Resin 2.x server

Log Track Supported: Yes
Config Track Supported: Yes
Custom Properties Supported: None
Supported Control Actions: start,stop,restart
Supported Metrics:

Configuration help:

Configure Resin 2.x for Monitoring

To enable monitoring of Resin servers and services the Resin server must be instrumented using a filter to collect metrics and a webapp to deliver the metric data into HQ. The web application, filter and any additional jars are packaged in the HQ agent directory under product_connectors/servlet. All commands below should be issued from this directory.

    cp libs/hq-filter.jar ${installpath}/lib
    cp libs/mx4j-jmx.jar ${installpath}/lib
    cp -R hyperic-hq ${installpath}/webapps
  

The final step for monitoring requires a change to the environment to place mx4j-jmx.jar in the front of Resin's classpath. Resin 2.x uses and older version of JMX that is incompatible with HQ. To fix this set the environment variable CLASSPATH to include the mx4j-jmx.jar

     export CLASSPATH=${installpath}/lib/mx4j-jmx.jar
  

Then start the Resin server as normal. This change can be made permanant by setting the CLASSPATH in the users login script or by directly modifying Resin's startup script to set the classpath.

NOTE: If HQ is used to control the Resin server the modification to the CLASSPATH is not necessary.

To enable the filter in a web application for monitoring, add the following filter definition to the application's web.xml.

  <filter>
    <filter-name>JMXFilter</filter-name>
    <filter-class>org.hyperic.hq.product.servlet.filter.JMXFilter</filter-class>
      
    <!-- Uncomment the following line to enable response time logging. 
            The directory you specify as the param can include properties 
            referenced from the System.properties of the vm.

            The ResponseTime log file will by default store the last 1 hour's 
            worth of response time data. This file gets truncated as soon as 
            data is succesfully sent into the server. The file is named uniquely
            for each webapp in the form: yourContextName_HQResponseTime.log

            If this fragment is included in the global web.xml for the container,
            all webapps in it will generate response time data, and have logs 
            following the format described above. You can enable it individually 
            on each webapp as well if you dont want every webapp to generate 
            response time data

         -->
    <!--
    <init-param>
      <param-name>responseTimeLogDir</param-name>
      <param-value>/home/johnmark/software/hyperic-hq-agent-3.1.0/logs</param-value>
    </init-param>
         -->

    <!-- these are optional parameters which you can override to optimize logging -->
    <!--
    <init-param>
      <param-name>bufferSize</param-name>
      <param-value>8k</param-value>
    </init-param>

    <init-param>
      <param-name>bufferTime</param-name>
      <param-value>1h</param-value>
    </init-param>
         -->
  </filter>

  <filter-mapping>
    <filter-name>JMXFilter</filter-name>
    <url-pattern>/*</url-pattern>
  </filter-mapping>

  <listener>
    <listener-class>org.hyperic.hq.product.servlet.filter.JMXSessionListener</listener-class>
    </listener>

  <servlet>
    <servlet-name>JMXWebappMetricServlet</servlet-name>
    <servlet-class>org.hyperic.hq.product.servlet.filter.JMXFilterInitServlet</servlet-class>
    <load-on-startup>1</load-on-startup>
  </servlet>
  

This can be tested by verifying your webapps show up correctly in the JMX Servlet. You may need to modify the hostname in the URL if your jmxUrl is configured relative to the agent host.

General Log and Config Track Properties

• Enable Config Tracking - Check to enable config tracking.
• Configuration Files - Comma delimited list of configuration files to track. Relative files are resolved to ${installpath}.
• Enable Log Tracking - Check to enable log tracking.
• Track event log level - Only track events of level greater than or equal to this level. Order is: [Error, Warn, Info, Debug]
  Mapping:
  • FATAL,ERROR -> Error
  • WARN -> Warn
  • INFO -> Info
  • DEBUG -> Debug
• Log Pattern Match - Include messages that match the given regular expression. The given pattern can be a substring to look for in log messages or a regular expression. See: java.util.regex.Pattern.
• Log Pattern Exclude - Exclude messages that match the given regular expression.
• Log Files - Comma delimited list of log files to track. Relative files are resolved to ${installpath}.