In this case the user was no longer signed into the backend but still had a browser tab open with the backend javascript still running. Every 5 seconds, 401 error is logged because the javascript call fails every time with the same error.
Fix suggested by Santo:
The ideal situation would be that after the first call that get the 401 status code, the JavaScript would stop making endless attempts.
Issue surfaced in support forum: https://groups.google.com/forum/#!topic/dotcms/W_xnd8tbqps
In this case the user was no longer signed into the backend but still had a browser tab open with the backend javascript still running. Every 5 seconds, 401 error is logged because the javascript call fails every time with the same error.
Fix suggested by Santo: The ideal situation would be that after the first call that get the 401 status code, the JavaScript would stop making endless attempts.
/dotcms324/dotserver/tomcat-8.0.18/webapps/ROOT/html/common/nav_sub_inc.jsp From: window.setInterval(function(){ checkNotifications(); }, 5000); TO: notificationsTimer = setInterval(function(){ checkNotifications(); }, 5000);
/dotcms324/dotserver/tomcat-8.0.18/webapps/ROOT/html/common/notifications_inc.jsp From: error : function(error) { console.log(error); } TO: error : function(error) { console.log(error); clearInterval(notificationsTimer); }
Solved, thanks!