?
avatar brianteeman
brianteeman
7 Jun 2017

Spotted by @coolcat-creations at jab17 and confirmed now by me

After some time working on testing j4 which might include closing and reopening the browser and/or having a session timeout and being forced to llog back in the count of the number of admins just keeps increasing

See below for the screenshots of a few hours using both J3 and J4 - the count only goes up in 4

(personally I am convinced there is some bug in 4 as i am being logged out much more often than i was in 3 but @wilsonge said there was no issue)
screenshotr16-56-15
screenshotr16-56-23

avatar brianteeman brianteeman - open - 7 Jun 2017
avatar joomla-cms-bot joomla-cms-bot - change - 7 Jun 2017
Labels Added: ?
avatar joomla-cms-bot joomla-cms-bot - labeled - 7 Jun 2017
avatar mbabker
mbabker - comment - 7 Jun 2017

There's probably something to dig into, I've noticed some quirks as well but hadn't thought twice about it.

avatar franz-wohlkoenig franz-wohlkoenig - change - 7 Jun 2017
Status New Discussion
avatar franz-wohlkoenig franz-wohlkoenig - change - 7 Jun 2017
Category Authentication
avatar wilsonge
wilsonge - comment - 7 Jun 2017

Just to add I'm not saying for sure there is not a bug in 4 - just with limited testing I couldn't easily reproduce one. I'm busy tonight but can look into it thursday night all being well.

avatar brianteeman
brianteeman - comment - 8 Jun 2017

coming back to the test site in the morning I see that the count has not reset and its still increasing

avatar mbabker
mbabker - comment - 8 Jun 2017

https://github.com/joomla/joomla-cms/blob/4.0-dev/libraries/src/CMS/Application/CMSApplication.php#L173

In 3.x we are arbitrarily running garbage collection on the session database table because we log the extra metadata as well, whereas the 4.0 code right now won't do it in favor of allowing PHP's session extension to handle garbage collection (which is how all the other handlers have to work, we don't have code arbitrarily flushing expired session data on the filesystem path or in Memcached). My guess is all of us who are seeing this type of behavior aren't getting the PHP cleanup to happen very often (some of it is explained in https://secure.php.net/manual/en/session.configuration.php#ini.session.gc-probability and linked references).

avatar brianteeman brianteeman - change - 14 Jun 2017
Status Discussion Closed
Closed_Date 0000-00-00 00:00:00 2017-06-14 19:53:55
Closed_By brianteeman
avatar brianteeman brianteeman - close - 14 Jun 2017
avatar brianteeman brianteeman - change - 19 Jun 2017
Status Closed New
Closed_Date 2017-06-14 19:53:55
Closed_By brianteeman
avatar brianteeman brianteeman - reopen - 19 Jun 2017
avatar franz-wohlkoenig franz-wohlkoenig - change - 19 Jun 2017
Status New Discussion
avatar brianteeman
brianteeman - comment - 20 Aug 2017

I am going to close this at this time as I see there have been updates to session

avatar brianteeman brianteeman - change - 20 Aug 2017
Status Discussion Closed
Closed_Date 0000-00-00 00:00:00 2017-08-20 10:38:57
Closed_By brianteeman
avatar brianteeman brianteeman - close - 20 Aug 2017

Add a Comment

Login with GitHub to post a comment