IBM Support

IT34706: PEERING ASSEMBLY BURST LIMIT DOES NOT SYNCHRONIZE ALL COUNTERS CORRECTLY

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When peering is enabled the assembly burst limit does not
    properly update statistics for "Remaining Requests"
    

Local fix

Problem summary

  • APIC user may see the value of token consuming and related
    respond headers are not synced among group members when assembly
     burst limit work in peer group.
    

Problem conclusion

  • Fixed in 2018.4.1.15, 10.0.1.1
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT34706

  • Reported component name

    DATAPOWER

  • Reported component ID

    DP1234567

  • Reported release

    A0X

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-11-11

  • Closed date

    2021-01-26

  • Last modified date

    2021-01-26

  • 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

    DATAPOWER

  • Fixed component ID

    DP1234567

Applicable component levels

  • R770 PSY

       UP

  • RA0X PSY

       UP

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS9H2Y","label":"IBM DataPower Gateways"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A0X"}]

Document Information

Modified date:
26 August 2021