Init funcs="pcheck_uri_clean_fixed_init"shlib="C:/Sun/webserver7/lib/custom.dll"
fn="load-modules"NativeThread="no"
TheNativeThread agaects all functions in the funcs list,so if you have more than one
functionin a library, but only some of them use native threads, use separate Init lines.If you set
NativeThreadto yes, the thread maps directly to an OS thread.
Forinformation on the load-modules function,see “load-modules” in Sun Java System Web
Server7.0 Update 1 Administrator’sC onguration FileReference.
ProcessModes
Youcan run Sun Java System Web Server in one of the following modes:
■“Single-ProcessMode” on page 44
■“Multi-ProcessMode” on page 44
Note– Multi-process mode is deprecated for Java technology-enabled servers. Most applications
arenow multi-threaded, and multi-process mode is usually not needed. However,
multi-processmode can signicantly improve overall server throughput for NSAPI
applicationsthat do not implement ne-grained locking.

Single-ProcessMode

Inthe single-process mode, the server receives requests from web clients to a single process.
Insidethe single server process, acceptor threads are running that are waiting for new requests
toarrive. When a request arrives, an acceptor thread accepts the connection and puts the
requestinto the connection queue. A request processing thread picks up the request from the
connectionqueue and handles the request.
Becausethe server is multi-threaded, all NSAPI extensions written to the server must be
thread-safe.This means that if the NSAPI extension uses a global resource, like a shared
referenceto a le or global variable, then the use of that resource must be synchronized so that
onlyone thread accesses it at a time. All plug-ins provided with the Web Server are thread-safe
andthread-aware, providing good scalability and concurrency. However, your legacy
applicationsmight be single-threaded. When the server runs the application, it can only execute
oneat a time. This leads to server performance problems when put under load. Unfortunately,
inthe single-process design, there is no real workaround.

Multi-ProcessMode

Youcan congure the server to handle requests using multiple processes with multiple threads
ineach process. This exibility provides optimal performance for sites using threads, and also
providesbackward compatibility to sites running legacy applications that are not ready to run
ina threaded environment. Because applications on Windows generally already take advantage
ofmulti-thread considerations, this feature applies to UNIX and Linux platforms.
UnderstandingThreads,Processes, and Connections
SunJavaSystem Web Server 7.0 Update 1 Performance Tuning,Sizing, and Scaling Guide •44