IBM Support

IT39947: API CONNECT GATEWAY PEERING OBJECTS CAN HAVE OPERATIONAL STATE 'UP' EVEN WHEN 2 OBJECTS HAVE CONFLICTING PORTS

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 gateway peering object is using a host alias for the local
    address the port conflict will not be noticed.
    

Local fix

  • Make sure the port are distinct.
    

Problem summary

  • Peering keeps restarting while serveror monitor ports are
    conflicted.
    

Problem conclusion

  • Fix is available in 2018.4.1.20, 10.0.1.7 and 10.5.0.0.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT39947

  • Reported component name

    DATAPOWER

  • Reported component ID

    DP1234567

  • Reported release

    A0X

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-03-03

  • Closed date

    2022-04-21

  • Last modified date

    2022-04-21

  • 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

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS9H2Y","label":"IBM DataPower Gateways"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A0X"}]

Document Information

Modified date:
22 April 2022