On 11/04/17 13:35, Johan Compagner wrote: > Thread: http-443-72, state: RUNNABLE, total cpu time: 5583984.375ms, total > user time: 5451312.5ms > java.net.SocketInputStream.socketRead0(Native Method) > java.net.SocketInputStream.socketRead(Unknown Source) > java.net.SocketInputStream.read(Unknown Source) > java.net.SocketInputStream.read(Unknown Source) > sun.security.ssl.InputRecord.readFully(Unknown Source) > sun.security.ssl.InputRecord.read(Unknown Source) > sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source) > sun.security.ssl.SSLSocketImpl.readDataRecord(Unknown Source) > sun.security.ssl.AppInputStream.read(Unknown Source) > > org.apache.coyote.http11.InternalInputBuffer.fill(InternalInputBuffer.java:733) > > org.apache.coyote.http11.InternalInputBuffer.parseRequestLine(InternalInputBuffer.java:364) > org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:814) > > org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:620) > org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489) > java.lang.Thread.run(Unknown Source) > > it seems that there is an incomming request right?
That is the normal waiting state for keep-alive connections with the HTTP BIO connector. Mark > That is not really a thread just in a a waiting state? > that should be something like this: > > Thread: http-443-70, state: WAITING, total cpu time: 7274093.75ms, total > user time: 7110015.625ms > java.lang.Object.wait(Native Method) > java.lang.Object.wait(Unknown Source) > org.apache.tomcat.util.net.JIoEndpoint$Worker.await(JIoEndpoint.java:458) > org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:484) > java.lang.Thread.run(Unknown Source) > > > or could the above be a keep alive thing? so the browser keeps the > connection alive for a while to reuse? > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
