Re: [Architecture] Old access token cleanup when token generating, renewing and revoking.

2018-07-29 Thread Nalaka Senarathna
hi all, >> *@Nalaka,* >> Have we done a load test to verify whether this feature does not affect >> to the functionalities when there is a high load in a high concurrency >> situation? >> If so appreciate if you can share that details as well. >> > > Yes, we did. @Nalaka Senarathna please

Re: [Architecture] Old access token cleanup when token generating, renewing and revoking.

2018-07-28 Thread Nuwan Dias
On Tue, Jul 24, 2018 at 3:17 PM Ishara Cooray wrote: > Our objective is to run this clean up process without anyone having to > configure anything. Even today we have instructions and scripts to clean up > the tables. But in practice, nobody even notices this and never does these > kind of stuff

Re: [Architecture] Old access token cleanup when token generating, renewing and revoking.

2018-07-24 Thread Ishara Cooray
Our objective is to run this clean up process without anyone having to configure anything. Even today we have instructions and scripts to clean up the tables. But in practice, nobody even notices this and never does these kind of stuff until they hit an issue and consult us through support. So if

Re: [Architecture] Old access token cleanup when token generating, renewing and revoking.

2018-07-19 Thread Harshan Liyanage
Hi Nuwan, Thanks for your detailed clarifications. Both explanations are perfectly valid. Regards, Harshan Liyanage Mobile: *+94765672894* Email: hars...@wso2.com Blog: http://harshanliyanage.blogspot.com/ Medium: https://medium.com/@harshan.dll *WSO2, Inc.:** wso2.com *

Re: [Architecture] Old access token cleanup when token generating, renewing and revoking.

2018-07-19 Thread Nuwan Dias
On Wed, Jul 18, 2018 at 9:09 PM Harshan Liyanage wrote: > Hi all, > > @Nuwan: That's why I suggested having a configurable cron expression so > that users can configure the task to run on an optimal schedule instead of > blocking vital functionalities. Also in that way, we could do a batch >