Clones Should be Configured With Their Own Unique stdout and stderr Files
 Technote (FAQ)
 
Problem
When configuring a server group in a WebSphere Application Server V4.0 environment, it is important that each clone in the server group have its own unique stdout and stderr files.
 
Solution
Scenario: A server group with two clones on the same node, each clone using the same servlet.

For the same servlet request, the response time differs for each clone because the same stdout file is set for both clones.

The application generates debug and error messages to standard output. During start up, the first clone locks the stdout file while writing to disk. The second clone starts and cannot write to disk because the file is locked by the first clone.

Solution : Configure each clone with its own unique stdout and stderr files. This will allow for standard output and standard error to be logged to the respective files simultaneously.

 
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Workload Management (WLM)
Operating system(s): HP-UX
Software version: 4.0
Software edition:
Reference #: 1145513
IBM Group: Software Group
Modified date: Nov 17, 2003