NonStop Servlets for JavaServer Pages (5.0) System Administrator's Guide

Overview and Architecture

NonStop Servlets for JavaServer Pages (NSJSP) System Administrator’s Guide—525644-002

1-19

Enhanced NSJSPCoyoteConnector

The NSJSP connector component NSJSPCoyoteConnector has been enhanced so

the connector is managed using JMX MBeans.

Session Clustering (not supported)

NSJSP 5.0 does not support session clustering. Instead, the current session routing

mechanism continues to be used in NSJSP 5.0.

Session clustering was not implemented because Tomcat 5.0 uses private backend

TCP sessions to support in memory session replication among servers in the same

cluster. Each session update triggers the server to send the session update to the

other servers in the cluster. If the number of servers increases, the backend session

traffic may cause performance degradation.

Invoker Servlet Availability

By default, the invoker servlet is no longer available in all web applications. However,

you can enable the invoker servlet by editing the

/usr/tandem/webserver/conf/web.xml and uncommenting the "/servlet/*"

servlet-mapping definition.

Using the invoker servlet in a production environment is not recommended. You can

achieve the same functionality and be more secure by adding and mapping your

servlets individually using the <servlet> and <servlet-mapping> elements in

your web application's deployment descriptor web.xml.

For more information, see the servlets-examples web applications deployment

descriptor (web.xml).