IT44803: FIX THE RATELIMIT TOKEN FROM LAST INTERVAL TO CONSUME THE LAST REMAINING INSTEAD OF REJECTING.

APAR status

• Closed as program error.

Error description

• Customers using a ratelimit 1 second interval with cache only
  off might observe from the analytics data for a transaction
  shows as rejected, but lists a full count of available API calls
  in the ratelimit.
  
  
  It was determined the rejection was from previous interval
  when enforce the ratelimit.
  
  
  To address this issue, the Gateway will remember the last
  remaining from last interval and reject the transactions from
  the interval before the last interval but provide the log to
  indicate it's from the interval other than previous.
  
  For example:
  
  "transaction_id":"73664269"
  "rate_limit":{"rate-limit":{"unit":"second","shared":"true","co
  unt":"10","interval":"1","period":"1","reject":"true","limit":"
  10"}}
  Ratelimit start time when the transaction occurs:
  1697557249055805 (Tue Oct 17 2023 15:40:49 GMT+0000)
  Ratelimit start time when the ratelimit is enforced:
  1697557250055805 (Tue Oct 17 2023 15:40:50 GMT+0000)
  

Local fix

Problem summary

• Customers using a ratelimit 1 second interval with cache only
  off might observe from the analytics data for a transaction
  shows as rejected, but lists a full count of available API calls
  in the ratelimit.
  

Problem conclusion

• Fix is available in 10.0.1.17, 10.5.0.9 and 10.5.3.0
  
  
  For a list of the latest fix packs available, please see:
  https://www.ibm.com/support/pages/node/83105
  

Temporary fix

Comments

APAR Information

• 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