Session timeout of cms is too low causing users to be logged out when cms actions take a long time to process

A while ago I set the session timeout of the cms to one minute. This was done in order to prevent the sessions of clients that lose their connection or browse away from the cms to cause OOMs by accumulating events. At that time I verified that one blocking request on the server did not prevent the browser from sending a concurrent pinger request to keep the session alive. However, it seems that although there is no problem on the client side to send a pinger request in that scenario, on the server side that pinger request is blocked until the previous request finishes. This is due to the fact that the cms and console applications are single page applications and wicket synchronises requests for the same page. After the browser has sent the first pinger request after the blocking request, it does not send it again until that pinger request has returned. In conclusion: requests longer than one minute will regularly cause the user to be logged out as a consequence of a timed out session.