A fix is available
APAR status
Closed as program error.
Error description
If you have a rate limit interval set to be a multiple of days (and therefore be divisible by 24 hours), you may see that the count of API calls is not correctly reset leading to 429 (Rate Limit exceeded) errors. Another issue noticed is that X-RateLimit-Remaining header in API Header is not showing correct value. For instance if there is a plan with 2000 calls per day and in the analytic you can see how many calls a client has made to that plan (for example 300). Then making an API Call, you will notices in the X-RateLimit-Remaining header, the number is more than 1700.
Local fix
Define Product plans with ratel limit of 22 or 23 hours instead of calls per day or 24 hours.
Problem summary
SLM rate limit policy is not working correctly for daily intervals.
Problem conclusion
Fix is available in 2018.4.1.5 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
IT28426
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-03-12
Closed date
2019-04-26
Last modified date
2019-04-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
R18X 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":"760"}]
Document Information
Modified date:
28 September 2021