Describe the bug
Upgrade openAM/openDJ pods. After some time, agents configured on application pods start to flood openAM with create token requests.
Only way to stop this seems to restart application pod.
This problem seems not to affect those pods that are restarted after openAM/openDJ upgrade.
In activity.csv log hundreds of lines like the following related to the agent of the offending pod without any attempt of DELETE:
In openDJ situation reflects the log above (snippet is taken from another syste in a moment where other application were acting the same on activity.csv) - some of the offending pod were already been restarted:
A workaround that seems to work is to restart all application pods after openAM/openDJ upgrade.
To Reproduce
Steps to reproduce the behavior:
Upgrade openAM/openDJ pods
Access an application whose pod has not been restarted after openAM/openDJ. Its agent will start (sometimes after a few hours of usage) to flood openAM with CREATE-SESSION requests.
Openam pod becomes unhealty showing "no healty upstreams". Liveness check on pod fails
Expected behavior
We expect that agents renews session properly without flooding openam without the need of application pod restart
Desktop (please complete the following information):
this seems unrelated to browser/system used
Additional context
dockers running on kubernetes environment in a single namespace
Describe the bug Upgrade openAM/openDJ pods. After some time, agents configured on application pods start to flood openAM with create token requests. Only way to stop this seems to restart application pod. This problem seems not to affect those pods that are restarted after openAM/openDJ upgrade.
In activity.csv log hundreds of lines like the following related to the agent of the offending pod without any attempt of DELETE:
In openDJ situation reflects the log above (snippet is taken from another syste in a moment where other application were acting the same on activity.csv) - some of the offending pod were already been restarted:
A workaround that seems to work is to restart all application pods after openAM/openDJ upgrade.
To Reproduce Steps to reproduce the behavior:
Expected behavior We expect that agents renews session properly without flooding openam without the need of application pod restart
Desktop (please complete the following information):
Additional context