PM32369: WASSERVICE IS UNABLE TO READ THE PID WHEN MICROSOFT WINDOWS SERVICE IS STARTED

6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server

APAR status

• Closed as program error.

Error description

• This is the failing scenario:
  1. Microsoft Windows Service is create to start Deployment
  Manager
  2. Start the Service
  3. The Deployment Manager starts but the Service fails
  4. With WASService trace enabled, the WASServiceTrace.log
  shows:
  getPidForServerFromStdout: Checking stdout for pid:
  C:\WAS70\appserver\profiles\dmgr01\logs\dmgrService.log
  ...
  getPidForServerFromStdout: Could not get pid from stdout.
  

Local fix

• There is no work around but the Deployment Manager is starting
   -
  KEYWORDS: dmgr startup start
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  IBM WebSphere Application Server V6.1 and   *
  *                  V7.0 Microsoft Windows services users       *
  ****************************************************************
  * PROBLEM DESCRIPTION: The wasservice.exe may not indicate     *
  *                      successful start                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Wasservice.exe is used to interface with Microsoft Windows
  Services and the IBM WebSphere Application Server. It may not
  indicate that the application server has started if it can not
  obtain process information from the application nor the
  standard output files.
  

Problem conclusion

• There was a problem extracting the process id information from
  the standard output generated from the application server. The
  code was modified to ensure the pid is successfully obtained.
  
  The fix for this APAR is currently targeted for inclusion in
  fix packs 6.1.0.39 and 7.0.0.17.  Please refer to the
  Recommended Updates page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

• 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

• R61W PSY

     UP

• R700 PSY

     UP