timeout page continue do comet request and log a lot message
Activity
Heng Sin Low June 3, 2020 at 7:59 AM
hi @Carlos Ruiz , that’s not sufficient for @Orlando Curieles use case - many users with short session timeout configuration. this need changes to allow the client side to know that the session has timeout and stop sending more request to the server.
Hiep Lq June 3, 2020 at 7:53 AM
ever you reduce log your server still get busy with that kind of process (like DOS attack)
but it's ok because not much user leave timeout screen on same time
Carlos Ruiz June 3, 2020 at 7:48 AM
I did the test - opened a session and left it open, after the session reaches the timeout (and the user leave it unattended) every second a ZkAtmosphereHandler.warn is written in the log.
So, in 30 minutes 1800 lines were written to the log with that message - as @Orlando Curieles said - multiply that by 100 users and you'll have an overflood log.
@Hiep Lq / @Heng Sin Low -> maybe the solution for 7.1 is simply to decrease the log level to info instead of warning?
Hiep Lq June 2, 2020 at 6:55 PM
note: it's fixed for master branch only, release 7.1 still has (need to update zk to resolved it)
but for me it's ok because i use master branch
Carlos Ruiz May 19, 2020 at 7:50 PM
As per the comment, this is already fixed
Details
Assignee
Heng Sin LowHeng Sin LowReporter
Hiep LqHiep LqPriority
Major
Details
Details
Assignee
Reporter
Priority
Major
1. reduce timeout to 2 minute (for fast re-do)
2. login to any client
3. wait for over 2 minute
4. this time browse sent comet request each 10s and server will log a lot message
17:41:30.054-----------> ZkAtmosphereHandler.warn: Could not find session: /webui/zkau/comet;jsessionid=setssionID.node0 [37]
i guess it relate https://idempiere.atlassian.net/browse/IDEMPIERE-4154#icft=IDEMPIERE-4154 or https://idempiere.atlassian.net/browse/IDEMPIERE-4206#icft=IDEMPIERE-4206
@Heng Sin Low any suggest?