IBM Support

IT32046: GATEWAY PEERING MIGHT BECOME STUCK IN PENDING STATE

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DataPower's Gateway Peering set-up might become stuck in a
    pending state indefinitely if the path from the unix domain
    socket (UDS) (used by the monitor/sentinel process) exceeded
    the max value on linux platform (which is 108 characters).
    

Local fix

  • You can attempt to shorten the names of the Gateway Peering
    Objects and/or Gateway Service to reduce the total path length
    under that character limit.
    

Problem summary

  • API Connect Gateway Service might get stuck in the pending state
    due to the length of internal path for the monitor/sentinel
    process is too long.
    

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    IT32046

  • Reported component name

    DATAPOWER

  • Reported component ID

    DP1234567

  • Reported release

    18X

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2020-03-02

  • Closed date

    2020-05-04

  • Last modified date

    2020-05-06

  • 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

[{"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":"18X"}]

Document Information

Modified date:
28 September 2021