PQ76261: Service has incorrect status when the log
root is changed
Downloadable files
Abstract
When trying to start the windows service for WebSphere
Application Server, the service goes to the "started" state and then the
"stopped" state.
Download Description
USERS AFFECTED:
WebSphere Application Server users that have modified the Log Root from
its default location.
PROBLEM DESCRIPTION:
The Windows service goes to the "started" state briefly before going to
the "stopped" state while the server starts successfully. The Windows
service cannot find the application servers pid file to verify that the
server started successfully. Since the status is incorrect, the server can
not be stopped via the windows services.
PROBLEM CONCLUSION:
The code was modified to allow a user to specify the new log location in a
parameter when installing the service. After applying the fix the user
should run "wasservice.exe -add <service name> -serverName
<server name> -logRoot <path to the server's log directory>
TEMPORARY FIX:
The fix that was sent to the customer allows for the service to take a Log
Root parameter.
Prerequisites
Please download the UpdateInstaller tool to install this Fix.