Features - Resin and Resin Professional

Resin is provided in two versions, Resin Professional and Resin Open Source. Resin Professional adds features and enhancements commonly needed in a production environment. Resin Open Source is suitable for hobbyists, developers, and low traffic websites that do not need the performance and reliability enhancements of Resin Professional.

Reliability features

Resin Professional provides a number of reliability features, including automatic server restart, detection and restart of locked or stalled servers, and monitoring of JVM memory usage for applications with memory leaks.

Resin configuration: <ping>
Resin configuration: <min-free-memory>

Clustering

Clustering provides the ability for multiple servers to appear as one server to clients. Clustering provides enhanced reliability and allows sites to scale up as server demand increases,

Clustering is supported with the standalone web server, Apache, and IIS.

Resin documentation: Reliability and Load Balancing

Persistent and Distributed sessions

Persistent sessions guarantee that a server can restore the contents of the HttpSession object when it is restarted. Distributed sessions provide the ability for multiple servers in a cluster to share the values stored in the HttpSession.

Resin documentation: Persistent and Distributed Sessions

Performance enhancing native code

Resin Professional includes a native code libary on both Windows and Unix platforms. Native code is used to provide significant performance benefits in areas like socket connections, keepalive connections, and file system access.

OpenSSL

Resin Professional uses native code to link to the OpenSSL libraries, a much better and more efficient SSL solution than the Java facilities provided by JSSE.

Resin documentation: OpenSSL

HTTP proxy caching

Resin Professional provides a memory and disk based caching system for increased performance benefits. Server caching can speed dynamic pages to near-static speeds. Small but frequently accessed resources such as images and css files are cached in memory and served directly to the client, avoiding even a read from the disk.

Many pages require expensive operations like database queries but change infrequently. Resin can cache the results and serve them like static pages. Resin's caching will work for any servlet, including JSP and XTP pages.

Resin documentation: Caching
Resin configuration: <cache>

Gzip filter

Bandwidth costs are significant for many websites. The GzipFilter enables automatic compression of responses for browsers that support it. Use of the GzipFilter reduces bandwidth usage and may provide significant cost savings.

Resin documentation: GzipFilter

Web Server

Standalone

Resin documentation: Standalone web server Unix and Windows

Hypertext Transfer Protocol (HTTP)

Secure Socket Layter (SSL) 3.0

Resin documentation

Apache 1.3 and 2.0 integration

IIS 5 and IIS 6 integration

Resin documentation: Resin with IIS

Operating Systems

Resin and Resin-EE are tested and supported on the following operating systems:

Linux
Solaris
Windows
Mac OS X

Resin is known to work on the following operating systems:

AIX
HP-UX
Free-BSD

Resin is used on these operating systems, however there may or may not be difficulties with Apache integration, and the JNI code that Resin uses to increase performance may not be available.

Databases

Resin provides a robust connection pool for any JDBC 1, JDBC 2, or JDBC 3 database driver.

Java Servlet 2.4

Java Server Pages (JSP) 2.0

Java Server Pages Standard Template Library (JSTL) 1.01

Portlet 1.0

Status: BETA

XSLT 1.0

XPath 1.0

JAXP 1.2

Java Connector Architecture (JCA) 1.5

Java Management Extensions (JMX) 1.2