IBM Support

PH43733: DISTRIBUTEDMAP.REMOVE() RESULTS IN NPE WHEN REPLICATION CONFIGURATION IS INCORRECT

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

  • If a cache instance is enable for replication but doesn't
    specify an existing replication domain, an NPE may occur when
    removing entries from the cache.
    

Local fix

  • Possible workaround:
    
    clusterCaching 	You can specify one of the following values:
       true (default)
       false
    
    	Set this property to false if you want each cluster member to
    maintain its own caches. When this property is set to false and
    you are operating in a cluster, session affinity is required for
    proper operation. When this property is set to false, the
    default for useStateCookies changes to false.
    
    https://www.ibm.com/docs/en/was/8.5.5?topic=cocrp-openid-connec
    t-relying-party-custom-properties-1
    First, try the following unqualified (ie, no provider_(id)
    prefix) OIDC TAI property:
    
    clusterCaching=false
    
    
    That will initialize DC as a local cache so both the
    insert/remove paths should recognize the state.
    
    
    If that does not work, remove the property, then create the
    DynaCacheCluster replication domain:
       In the admin console, navigate to Environment -> Replication
    domains
       For the Name, enter DynaCacheCluster
    
       For number of replicas, select Entire domain
       Click OK
       Save
       Restart the server
    
    For reference:  https://www.ibm.com/docs/en/was/9.0.5?topic=set
    tings-data-replication-domain
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server                                      *
    *                  using dynacache with replication enabled.   *
    ****************************************************************
    * PROBLEM DESCRIPTION: A NullPointerException may occur in     *
    *                      DRSNotificationService.isDRSReady()     *
    *                      when                                    *
    *                      invalidating or removing a cached       *
    *                      object.                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    A valid replication domain name must be specified when
    replication is enabled for a cache instance.  A
    NullPointerException in DRSNotificationService.isDRSReady() may
    occur when the cache instance is initialized with replication
    enabled but a replication domain name is not specified.
    

Problem conclusion

  • Dynacache will disable replication for a cache instance if the
    replication name is not specified when the cache instance is
    initialized.  This will prevent the NullPointerException but the
    configuration is still invalid.  If replication is required then
    the replication domain name must be specified in the cache
    instance configuration.  If replication is not required then
    replication should not be enabled.
    
    The fix for this APAR is targeted for inclusion in fix packs
    9.0.5.12 and 8.5.5.22 For more information, see 'Recommended
    Updates for WebSphere Application Server':
    https://www.ibm.com/support/pages/node/715553
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH43733

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-01-28

  • Closed date

    2022-04-15

  • Last modified date

    2022-04-15

  • 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

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"9.0"}]

Document Information

Modified date:
16 April 2022