A fix is available
APAR status
Closed as program error.
Error description
"Quota Enforcement Concurrent Transactions Metrics" shows incorrect values when using more than one key (in the ratelimit.concurrentCreate(key) call.
Local fix
Workaround is to have two chained mpgw services and each of them uses only one concurrent policy.
Problem summary
A DataPower user who uses Quota Enforcement ratelimit module might see the APIs for concurrent transactions work for one key per transaction only.
Problem conclusion
Fix is available in 2018.4.1.11 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
IT31854
Reported component name
DATAPOWER
Reported component ID
DP1234567
Reported release
770
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2020-02-13
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
[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS9H2Y","label":"IBM DataPower Gateway"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"770","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
17 June 2020