Information Servlet /resin-status
Resin 3.0

Features
Installation
Configuration
Web Applications
IOC/AOP
Resources
JSP
Servlets and Filters
Portlets
Databases
Admin (JMX)
CMP
EJB
Amber
EJB 3.0
Security
XML and XSLT
XTP
JMS
Performance
Protocols
Third-party
Troubleshooting/FAQ

Servlet
JMX Consoles
Instrumenting
Tutorials
Cookbook
Admin (JMX)
Admin (JMX)
JMX Consoles

Resin provides a primitive status servlet /resin-status. It's disabled by default to avoid any security issues.

  1. Configure the /resin-status servlet
  2. Interpreting the proxy cache hit ratio

Configure the /resin-status servlet

resin.conf /resin-status configuration
<resin xmlns="http://caucho.com/ns/resin"
       xmlns:resin="http://caucho.com/ns/resin/core">

...

<web-app-default>

      <servlet-mapping servlet-class='com.caucho.servlets.ResinStatusServlet'>
        <url-pattern>/resin-status</url-pattern>
        <init enable="read"/>
      </servlet-mapping>

      <security-constraint>
        <web-resource-collection url-pattern="/resin-status/*"/>
        <ip-constraint>
          <allow>127.0.0.1/32</allow>
        </ip-constraint>
      </security-constraint>

</web-app-default>

...

Interpreting the proxy cache hit ratio

The proxy cache is Resin's internal proxy cache (in Resin Pro). The hit ratio marks what percentage of requests are served out of the cache, i.e. quickly, and which percentage are taking the full time.

The proxy cache hit ratio is useful for seeing if you can improve your application's performance with better caching. For example, if you had a news site like www.cnn.com, you should have a high hit rate to make sure you're not overtaxing the database.

If you have a low value, you might want to look at your heavily used pages to see if you can cache more.


Admin (JMX)
Admin (JMX)
JMX Consoles
Copyright © 1998-2005 Caucho Technology, Inc. All rights reserved.
Resin® is a registered trademark, and HardCoretm and Quercustm are trademarks of Caucho Technology, Inc.