APAR status
Closed as program error.
Error description
The problem is that startserver write msg ADMU3000I to stdout in a different format than it writes the message to the logfile (with this language). WASService is expecting the message to appear like it appears in the startserver.log: ADMU3000I: Der Server nodeagent ist für e-business bereit. Die Prozess-ID ist 27680. but it is written as: ADMU3000I: Der Server nodeagent ist f?r e-business bereit. Die Prozess-ID ist 27680. . WASService needs to modify code to allow for this. With the current code, the 3000 in the message number is detected as the pid and failure occurs attempting to connect to the process since the pid is 27680, not 3000
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: IBM WebSphere Application Server windows * * service users * **************************************************************** * PROBLEM DESCRIPTION: Failures starting and stopping * * WebSphere on Windows with WebSphere * * service enabled. * **************************************************************** * RECOMMENDATION: Disable the service or apply this fix if * * applicable to environment. * **************************************************************** When started from the Windows services, the server will start but the service indicated it failed to start. The server will fail to start from the command line or start menu when the service is enabled. Stop commands will fail. Disable the service and start the service using the command line (startserver or startnode). If message ADM3000I is displayed on multiple lines or contains multiple characters after the process identifier, this fix is required to correct the service.
Problem conclusion
With some languages, startserver prints msg ADMU3000I to the console on multiple lines but logs the message with a single line. The WebSphere service parses this message to obtain the server process identifier. The service requires the process identifier to communicate with the server and obtain an accurate status for the server. The service incorrectly pulls the message number (3000) as the process identifier. It fails to attach to the process with the incorrect process identifier. The WebSphere service expected the message to appear in the same format on the console and the log file. WebSphere service code was modified to extract the pid from multiple lines and from any position within the message. The fix for this APAR is targeted for inclusion in fix pack 9.0.5.7. This fix does not apply to other release levels of WebSphere. For more information, see 'Recommended Updates for WebSphere Application Server': https://www.ibm.com/support/pages/node/715553
Temporary fix
Disable the service and use command line tools to start and stop WebSphere (such as startServer, stopServer, startNode, stopNode, etc).
Comments
APAR Information
APAR number
PH32837
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
900
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2020-12-18
Closed date
2021-01-05
Last modified date
2021-02-12
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R900 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
02 November 2021