Changing the location of the startServer and stopServer logs
 Technote (FAQ)
 
Problem
Changing the LOG_ROOT variable from the IBM® WebSphere® Application Server Administrator Console does not change the location of the startServer.log or stopServer.log files.
 
Cause
Changing the LOG_ROOT variable from the Administrative Console does not change the location of the startServer.log or stopServer.log files, because the startServer and stopServer commands do not read any Java™ Virtual Machine (JVM) parameters.
 
Solution
This is working as designed. You cannot change the location of the startServer.log and stopServer.log files from the Administrative Console, or in any XML files, because the startServer.log is generated by the startServer command and there is no JVM loaded by it. Also the startServer and stopServer commands do not read any JVM parameters.

To change the location of these logs, specify the -logfile parameter and provide the location where the logs need to be written when the script is run.

For example:
For UNIX® platforms:

startServer.sh  server1 -logfile C:\logs\start.log

For Microsoft® Windows®:

startServer.bat server1 -logifle C:\logs\start.log
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers WebSphere Application Server - Express AIX, HP-UX, Linux, Solaris, Windows 6.0, 5.1, 5.0
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > System Management/Repository
Operating system(s): Windows
Software version: 6.0
Software edition:
Reference #: 1251879
IBM Group: Software Group
Modified date: Mar 30, 2007