Bakshinder Singh created SLING-5069:
---------------------------------------
Summary: Huge delta reported between sling request log and the
SlingMainServlet
Key: SLING-5069
URL: https://issues.apache.org/jira/browse/SLING-5069
Project: Sling
Issue Type: Bug
Components: Engine
Environment: Windows 2012
Reporter: Bakshinder Singh
Intermittently during load we see a huge delta between the time reported when
the request was received in request log and the thread name which is setup in
SlingMainServlet service method:
// set the thread name according to the request
String threadName = setThreadName(request);
I am not sure what is holding the thread or any syncronization issues before
request reaches the SlingMainServlet.
Ex:
Request.log: The request is received at 08:59:07
28/Sep/2015:08:59:07 -0400 [e6bd04c5-733b-49f6-a188-2abad60ded2a] GET
/content/audit/us/en/member/research/study/15/2016-audit-plan-hot-spots.html?referrerTitle=Home%20-%20Member%20-%20CEB%20Audit%20Leadership%20Council&utm_campaign=ADR-amkaur-2015.09.28-GLOBAL-M-B-Daily-NL-Team-70134000001PwnpAAC&utm_medium=email&utm_source=Eloqua
HTTP/1.1 [email protected] 200 text/html; charset=utf-8 13416ms
Other log files:
The thread name longtime is 1443445160351: 08:59:20 . There is a 13sec delta
28.09.2015 08:59:20.850 *DEBUG* [10.111.2.67 [1443445160351] GET
/content/audit/us/en/member/research/study/15/2016-audit-plan-hot-spots.html
HTTP/1.1]
com.ceb.webcq.services.integrations.sbws.session.impl.CebLoggingInInterceptor
org.perf4j.TimingLogger e6bd04c5-733b-49f6-a188-2abad60ded2a
start[1443445160694] time[156] tag[IUserProfileWebService:GetNotifications]
This happens several times may be around one in 1000 request or so.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
