IBM Support

PM22200: IMPROVE LOGGING IN STARTSERVER.LOG IN THE CASE WHERE OS IMPOSES MAX FILESIZE LIMIT PREVENTING ALLOCATION OF NATIVE_STDOUT.LOG

Fixes are available

6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
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
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • A server failed to start because the native_stdout.log file
    could not be written because it exceeded the Operating System
    maximum file size limitation of 2GB. However, the cause of
    this problem was not evident in the debug (-trace option used)
    StartServer.log file; error messages logged:
    ...
    [8/25/10 22:15:33:062 PDT] 0000000a WsServerLaunc E   ADMU3007E:
    Exception com.ibm.ws.process.exception.ProcessOpException:
    com.ibm.ws.process.exception.ProcessOpException: Error creating
    new process.
    at
    com.ibm.ws.process.UnixProcessImpl.create(UnixProcessImpl.java:1
    37)
    at com.ibm.ws.process.ProcessFactory.create(Unknown Source)
    ...
    Defect for improvement of the logging and serviceability to
    identify cause of problem and corrective action.
    

Local fix

  • Remove the 2 GIG native_stdout.log file, Server creates a new
    native_stdout.log file and server successfully starts
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server V6.1 and V7.0                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: The native layer for WebSphere          *
    *                      Application Server process management   *
    *                      does not provide sufficient logging     *
    *                      and serviceability.                     *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The WebSphere Application Server process management
    capabilities do not provide sufficient error and
    serviceability messages to aid in root problem determination.
    

Problem conclusion

  • This change does not directly affect function, but improves
    the logging and serviceability of the native code layer for the
    WebSphere Application Server process management capabilities.
    These changes will provide better messages as to what the root
    problem is when there is an error starting a process via the
    process management capabilities.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 6.1.0.37 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 number

    PM22200

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    60S

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-09-09

  • Closed date

    2010-11-22

  • Last modified date

    2010-11-22

  • 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

    WEBSPHERE APP S

  • Fixed component ID

    5724J0800

Applicable component levels

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61Z PSY

       UP

  • R700 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 6.0

Reference #: PM22200

Modified date: 22 November 2010