APAR status
Closed as program error.
Error description
When a configuration change is made in API Manager, API Manager sends the change to the gateway subsystem, where it is initially processed by one gateway. If there are multiple gateways in the subsystem, the processing gateway should propagate the change to the other gateways in the subsystem (via publish/subscribe events sent via gateway peering). Under certain conditions this propagation might not happen for given changes.
Local fix
Problem summary
In a multiple-gateway subsystem, sometimes the configuration change in API Manager is always propagated correctly to all gateways via publish/subscribe events.
Problem conclusion
Fix is available in 2018.4.1.19, 10.0.1.6 and 10.0.4.0 For a list of the latest fix packs available, please see: http://www-01.ibm.com/support/docview.wss?uid=swg21237631
Temporary fix
Comments
APAR Information
APAR number
IT39203
Reported component name
DATAPOWER
Reported component ID
DP1234567
Reported release
18X
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2021-11-24
Closed date
2021-12-07
Last modified date
2022-02-17
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":"18X"}]
Document Information
Modified date:
18 February 2022