IBM Support

PI90503: CANNOT START LOGGING IN TPV

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • The customer's environment has an Administrative Agent profile t
    manages two stand-alone servers, under the same node xxxxx. When
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server.                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: The Tivoli Performance Viewer (TPV)     *
    *                      logging can not be started, if multiple *
    *                      servers are managed by an               *
    *                      Administrative                          *
    *                      Agent.                                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If the customer's environment has an Administrative Agent
    profile
    that manages two stand-alone servers, under the same node and
    with
    each server started, when the TPV start logging is pressed in
    the
    Administrative Console for any server, the following error
    message
    is shown:
    "An error occured during the attempt to start logging."
    When the TPV logging is started, the query for the TPVMBean will
    return more than one result when multiple running servers are
    managed by the Administrative Agent. The current implementation
    expects only one MBean reference to be returned. Hence, causing
    the
    start logging error to be shown in the Administrative Console.
    

Problem conclusion

  • The code was modified to allow the TPV start logging to work for
    all running servers managed by an Administrative Agent.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 8.0.0.15, 8.5.5.14, and 9.0.0.7.  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

    PI90503

  • Reported component name

    WEBSPHERE APP S

  • Reported component ID

    5724J0800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2017-11-22

  • Closed date

    2018-01-09

  • Last modified date

    2018-01-09

  • 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



Document information

More support for: WebSphere Application Server
General

Software version: 850

Reference #: PI90503

Modified date: 09 January 2018


Translate this page: