APAR status
Closed as program error.
Error description
When an SLM policy that monitors backend latency is called from another rule (for example, in a user-defined API Connect policy), then thresholds based on backend latency do not properly account for that latency and some requests are allowed that would otherwise trigger the threshold.
Local fix
Problem summary
SLM rule inside user-defined policy wrapped by an error rule does not properly account for backend response latency.
Problem conclusion
Fix is available in 7.6.0.13 and 2018.4.1.4 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
IT28240
Reported component name
DATAPOWER
Reported component ID
DP1234567
Reported release
760
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-02-27
Closed date
2019-03-22
Last modified date
2019-03-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
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS9H2Y","label":"IBM DataPower Gateway"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"760","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
11 February 2022