IBM Support

JR62285: AD HOC GROUP MONITOR DOESN'T VALIDATE GROUPS WHEN ENABLED

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.

Direct link to fix

 

APAR status

  • Closed as program error.

Error description

  • When the enable-ad-hoc-group-monitoring configuration setting is
    set to the "true", monitoring of ad hoc groups is enabled.
    However, the function doesn't correctly compute the composition
    of an ad hoc group that contains nested groups, resulting in
    incorrect corruption detect and insufficient repairs.
    
    You might see log messages like the following messages even
    though the membership of an ad hoc group was not modified:
    
    [3/22/20 22:35:47:855 PDT] 000001c8 TemporaryGrou I
    com.lombardisoftware.server.ejb.security.TemporaryGroupsCore
    checkRequestedVersusUsersInDB ad-hoc group monitoring:
    CWLLG1103I: Mismatch detected for ad-hoc group: UserGroup.1552,
    name: OItXgXFWapkZF+lJ3Z2mmvKyHir9BGsEzRCk2WXEBEY= (1552). 0
    users are missing and 2 users are unexpectedly in DB.
    [3/22/20 22:35:47:856 PDT] 000001c8 TemporaryGrou I
    com.lombardisoftware.server.ejb.security.TemporaryGroupsCore
    checkRequestedVersusUsersInDB ad-hoc group monitoring:
    CWLLG1105I: User unexpectedly in DB: 1, name: celladmin
    [3/22/20 22:35:47:856 PDT] 000001c8 TemporaryGrou I
    com.lombardisoftware.server.ejb.security.TemporaryGroupsCore
    checkRequestedVersusUsersInDB ad-hoc group monitoring:
    CWLLG1105I: User unexpectedly in DB: 9, name: deadmin
    [3/22/20 22:35:47:859 PDT] 000001c8 TemporaryGrou I
    com.lombardisoftware.server.ejb.security.TemporaryGroupsCore
    createTemporaryGroup ad-hoc group monitoring: CWLLG1102I: Ad-hoc
    group UserGroup.1552 was repaired to contain the desired set of
    users (duplicates will be contained only once):
    

Local fix

Problem summary

  • This issue occurs because groups in the ad hoc group are not
    considered when the membership of the ad hoc group is compared
    with the current membership in the database.
    

Problem conclusion

  • A fix is available or will be available that considers groups in
    the ad hoc group when the membership of the ad hoc group is
    compared with the current membership in the database.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR62285

  • Reported component name

    BUS AUTO WORKFL

  • Reported component ID

    5737H4100

  • Reported release

    I00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-04-29

  • Closed date

    2020-05-19

  • Last modified date

    2020-05-19

  • 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

    BUS AUTO WORKFL

  • Fixed component ID

    5737H4100

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS8JB4","label":"IBM Business Automation Workflow"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"18.0.0.0","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
22 June 2020