IBM Support

PH06211: SPORADIC EPISODES OF VIEW_SERVER NOT RESPONDING MESSAGES ON SOLARIS 11.3

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

  • Sporadically during normal build or testing activities using IBM
    Rational ClearCase the dynamic view client with report
    repeatedly "view_server not responding" / "view_server ok"
    messages. This slows down the work as it generates many RPC
    retries.
    
    An example of the errors seen is:
    View server for <SERVER>:<VIEW STORAGE PATH> not responding
    still trying (st=5 er=145)
    View server for <SERVER>:<VIEW STORAGE PATH> ok
    
    WORKAROUND:
    None.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users of ClearCase dynamic views on Solaris 11.              *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * ClearCase users on Oracle Solaris systems sporadically       *
    * experience extremely slow performance of actions in a        *
    * particular dynamic view, accompanied by a series of error    *
    * messages of the form: "View server for <view storage path>   *
    * not responding still trying (st=5 err=145)".                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • Sporadic slow performance of a dynamic view on Oracle Solaris
    occurs when there is a conflict between kernel services using
    the same UDP port for RPCs.  The port assignment is managed by
    the Solaris kernel, but ClearCase has implemented a workaround
    for this problem in versions 8.0.1.21 and 9.0.1.7.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH06211

  • Reported component name

    CLEARCASE WIN

  • Reported component ID

    5724G2900

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-12-06

  • Closed date

    2019-06-20

  • Last modified date

    2019-06-20

  • 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

    CLEARCASE WIN

  • Fixed component ID

    5724G2900

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSSH27","label":"Rational ClearCase"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"900","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
20 June 2019