This happened in the past and we want to understand why this happened.
Layer7 version = 10.0 CR04
OTK version = 4.3.1 CR02
We are using the default OTK scheduled task
We usually have around 500k tokens in the database when the purge is working properly. Recently, we had a problem with the "OTK Database Maintenance - token" task and upon research we found out that there was more than 32 million tokens in the database. It seems like the purge stop functioning properly around 1 month before we saw the impact.
The scheduled task uses JDBC query assertion to delete records of all expired tokens, there is a bug in the scheduled task where the number of deletes becomes excessive to the point where it's unable to complete in one cycle when this occurs no tokens get deleted causing the table to continuously increase
Release : 10.0
In version OTK 4.5 the schedule task has been modified to purge in blocks/limits instead of ALL at once.
Recommend upgrading to the latest OTK