Resin deliberately does not include any kind of GUI for
deployment or management. Or philosophy is:
- a single xml configuration file for the server (
- changes to the server configuration file (
resin.conf) are automatically
detected and cause a restart of the server
- changes to the
WEB-INF/web.xml configuration file for a web
application are automatically detected and cause a restart of the web
- new web applications are added either with
changes, or by adding a
.war or subdirectory to a
- new virtual hosts are added either
resin.conf file changes, or by adding a
subdirectory in a
The .rnc files used by Resin for validation are in
See JSP Compilation.
Directory listing is performed by a servlet named `directory'.
The standard resin.conf contains a definition of that servlet:
Directory listing is disabled by removing or commenting out this definition.
We've seen significant performance issues when distributed sessions are
enabled, and are trying to find some clues as to the cause. We've seen as much
as 30% increase in cpu utilization when disttributed sessions are enabled, and
we are using .
has a significant impact on performance.
When using , Resin can't know if an
internal bean value has changed, so the session is serialized with every
request. That's a pretty significant amount of work, depending on how much is
stored in the session.
It is far more efficient to design the session to avoid the need for , so session values are only saved once and
then are read-only.
You can avoid if you call setAttribute()
each time the session state changes. If your web application calls
session.setAttribute("key",value) everytime you change the value object,
then Resin can intercept that call and realize that the session needs to be
written to the distributed store again.
Resin 3.0 is a little more efficient thatn Resin 2.1. Resin 3.0 compares the
crc sum of the serialization; it compares the crc value of the serialization of
current session objects with the objects in the backing store, and if there is
no change the session is not written.
Copyright (c) 1998-2009 Caucho Technology, Inc. All rights reserved.
are registered trademarks of Caucho Technology, Inc.