IBM Support

PJ44074: SOLUTION DEPLOYMENT STATUS CHECK IN ADMIN CLIENT CAN ENCOUNTER LOCK CONTENTION ERRORS (FNRPE2131090018E) IN TARGET OBJECT STORE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The Solution Deployment Status check that continuously "pings"
    the Target Object Store during solution deployment to check the
    current status of the deployment so that it can be displayed in
    the Case Manager Administration Client UI can sometimes
    encounter lock contention errors (FNRPE2131090018E) while large
    Workflow maps are being transferred, etc., as part of the
    solution deployment process itself.  As a result of this issue,
    the UI in the Case Manager Administration Client will indicate
    that the solution deployment itself has failed even when it has
    in fact succeeded - as seen in the Detail and Error Deployment
    Log files produced.
    

Local fix

  • Unlike Case Manager Administration Client, the Case Manager
    Configuration Tool does not "ping" the Target Object Store
    during solution deployment to check the current status of the
    deployment.  So using the Case Manager Configuration Tool to
    deploy the solution (using the "Deploy Solution" step from a
    "Production Profile" - even in a "Development" environment) is a
    viable workaround.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Case Manager Administration Client users encountering        *
    * Workflow lock contention errors during solution deployment   *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * To fix this problem, apply 5.2.1.4-ICM-FP004 or later        *
    * releases.                                                    *
    ****************************************************************
    

Problem conclusion

  • Fixed in 5.2.1.4-ICM-FP004 and higher.  The fix for this problem
    is provided in and resolved by IBM Case Manager
    5.2.1.4-ICM-FP004 or later releases.
    
    With this fix, Case Manager Administration Client users are much
    less likely to encounter Workflow lock contention errors during
    solution deployment because the code that pings and displays the
    current deployment status during the deployment will now use
    cached connection information.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PJ44074

  • Reported component name

    CASE MGR ADM CL

  • Reported component ID

    5725A1506

  • Reported release

    521

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-04-04

  • Closed date

    2016-05-03

  • Last modified date

    2016-05-03

  • 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

    CASE MGR ADM CL

  • Fixed component ID

    5725A1506

Applicable component levels

  • R520 PSN

       UP

  • R521 PSY

       UP

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSCTJ4","label":"IBM Case Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"521"}]

Document Information

Modified date:
04 January 2021