You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Christoph Empl <Ch...@mgm-tp.com.INVALID> on 2022/09/29 09:56:50 UTC
Tomcat unresponsive
Hello,
i’m facing a problem that my tomcat seems to become unresponsive if it’s under a certain load.
Most threads in threaddumps look like this:
"https-jsse-nio-21030-exec-133" #13306 daemon prio=5 os_prio=0 cpu=17099.37ms elapsed=897.51s tid=0x00007f6270063b00 nid=0x1e5c38 in Object.wait() [0x00007f6109df4000]
java.lang.Thread.State: TIMED_WAITING (on object monitor)
at java.lang.Object.wait(java.base@17.0.3/Native Method)
- waiting on <no object reference available><monitor://%3cno%20object%20reference%20available%3e>
at org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.fillReadBuffer(NioEndpoint.java:1325)
- locked <0x000000050f48a720><monitor://%3c0x000000050f48a720%3e> (a java.util.concurrent.Semaphore)
at org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.read(NioEndpoint.java:1226)
at org.apache.coyote.http11.Http11InputBuffer.fill(Http11InputBuffer.java:805)
at org.apache.coyote.http11.Http11InputBuffer.access$400(Http11InputBuffer.java:42)
at org.apache.coyote.http11.Http11InputBuffer$SocketInputBuffer.doRead(Http11InputBuffer.java:1185)
at org.apache.coyote.http11.filters.IdentityInputFilter.end(IdentityInputFilter.java:151)
at org.apache.coyote.http11.Http11InputBuffer.endRequest(Http11InputBuffer.java:655)
at org.apache.coyote.http11.Http11Processor.endRequest(Http11Processor.java:1192)
at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:439)
at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:890)
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1743)
at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
- locked <0x000000050f48a730><monitor://%3c0x000000050f48a730%3e> (a org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper)
at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(java.base@17.0.3/Thread.java:833)
I’m suspecting a slow network. Does anybody have another idea?
Thanks, Christoph
Re: Tomcat unresponsive
Posted by Christoph Empl <Ch...@mgm-tp.com.INVALID>.
Sorry... Tomcat Version 9.0.63.
Am 29.09.22, 12:06 schrieb "Jason Wee" <pe...@gmail.com>:
could be waiting for i/o or some others... what tomcat version ?
On Thu, Sep 29, 2022 at 5:57 PM Christoph Empl
<Ch...@mgm-tp.com.invalid> wrote:
>
> Hello,
>
> i’m facing a problem that my tomcat seems to become unresponsive if it’s under a certain load.
>
> Most threads in threaddumps look like this:
>
>
> "https-jsse-nio-21030-exec-133" #13306 daemon prio=5 os_prio=0 cpu=17099.37ms elapsed=897.51s tid=0x00007f6270063b00 nid=0x1e5c38 in Object.wait() [0x00007f6109df4000]
>
> java.lang.Thread.State: TIMED_WAITING (on object monitor)
>
> at java.lang.Object.wait(java.base@17.0.3/Native Method)
>
> - waiting on <no object reference available><monitor://%3cno%20object%20reference%20available%3e>
>
> at org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.fillReadBuffer(NioEndpoint.java:1325)
>
> - locked <0x000000050f48a720><monitor://%3c0x000000050f48a720%3e> (a java.util.concurrent.Semaphore)
>
> at org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.read(NioEndpoint.java:1226)
>
> at org.apache.coyote.http11.Http11InputBuffer.fill(Http11InputBuffer.java:805)
>
> at org.apache.coyote.http11.Http11InputBuffer.access$400(Http11InputBuffer.java:42)
>
> at org.apache.coyote.http11.Http11InputBuffer$SocketInputBuffer.doRead(Http11InputBuffer.java:1185)
>
> at org.apache.coyote.http11.filters.IdentityInputFilter.end(IdentityInputFilter.java:151)
>
> at org.apache.coyote.http11.Http11InputBuffer.endRequest(Http11InputBuffer.java:655)
>
> at org.apache.coyote.http11.Http11Processor.endRequest(Http11Processor.java:1192)
>
> at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:439)
>
> at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
>
> at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:890)
>
> at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1743)
>
> at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
>
> - locked <0x000000050f48a730><monitor://%3c0x000000050f48a730%3e> (a org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper)
>
> at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
>
> at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
>
> at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>
> at java.lang.Thread.run(java.base@17.0.3/Thread.java:833)
>
>
> I’m suspecting a slow network. Does anybody have another idea?
>
>
> Thanks, Christoph
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat unresponsive
Posted by Jason Wee <pe...@gmail.com>.
could be waiting for i/o or some others... what tomcat version ?
On Thu, Sep 29, 2022 at 5:57 PM Christoph Empl
<Ch...@mgm-tp.com.invalid> wrote:
>
> Hello,
>
> i’m facing a problem that my tomcat seems to become unresponsive if it’s under a certain load.
>
> Most threads in threaddumps look like this:
>
>
> "https-jsse-nio-21030-exec-133" #13306 daemon prio=5 os_prio=0 cpu=17099.37ms elapsed=897.51s tid=0x00007f6270063b00 nid=0x1e5c38 in Object.wait() [0x00007f6109df4000]
>
> java.lang.Thread.State: TIMED_WAITING (on object monitor)
>
> at java.lang.Object.wait(java.base@17.0.3/Native Method)
>
> - waiting on <no object reference available><monitor://%3cno%20object%20reference%20available%3e>
>
> at org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.fillReadBuffer(NioEndpoint.java:1325)
>
> - locked <0x000000050f48a720><monitor://%3c0x000000050f48a720%3e> (a java.util.concurrent.Semaphore)
>
> at org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.read(NioEndpoint.java:1226)
>
> at org.apache.coyote.http11.Http11InputBuffer.fill(Http11InputBuffer.java:805)
>
> at org.apache.coyote.http11.Http11InputBuffer.access$400(Http11InputBuffer.java:42)
>
> at org.apache.coyote.http11.Http11InputBuffer$SocketInputBuffer.doRead(Http11InputBuffer.java:1185)
>
> at org.apache.coyote.http11.filters.IdentityInputFilter.end(IdentityInputFilter.java:151)
>
> at org.apache.coyote.http11.Http11InputBuffer.endRequest(Http11InputBuffer.java:655)
>
> at org.apache.coyote.http11.Http11Processor.endRequest(Http11Processor.java:1192)
>
> at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:439)
>
> at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
>
> at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:890)
>
> at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1743)
>
> at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
>
> - locked <0x000000050f48a730><monitor://%3c0x000000050f48a730%3e> (a org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper)
>
> at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
>
> at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
>
> at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>
> at java.lang.Thread.run(java.base@17.0.3/Thread.java:833)
>
>
> I’m suspecting a slow network. Does anybody have another idea?
>
>
> Thanks, Christoph
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Tomcat unresponsive
Posted by Suvendu Sekhar Mondal <su...@gmail.com>.
Hello Christoph,
On Thu, Sep 29, 2022, 3:27 PM Christoph Empl
<Ch...@mgm-tp.com.invalid> wrote:
> Hello,
>
> i’m facing a problem that my tomcat seems to become unresponsive if it’s
> under a certain load.
>
Can you please elaborate the situation a bit? What happens after that, is
it crashing or becomes sluggish? Does it recovers ever or you have to
restart it?
If you can recreate it at your will, can you please share load profile,
connector's configuration and some thread dumps? You may need to upload
dumps somewhere else and share the link. I will suggest to use jstack to
get simple thread dumps few seconds(say 5) apart.
> Most threads in threaddumps look like this:
>
>
> "https-jsse-nio-21030-exec-133" #13306 daemon prio=5 os_prio=0
> cpu=17099.37ms elapsed=897.51s tid=0x00007f6270063b00 nid=0x1e5c38 in
> Object.wait() [0x00007f6109df4000]
>
> java.lang.Thread.State: TIMED_WAITING (on object monitor)
>
> at java.lang.Object.wait(java.base@17.0.3/Native Method)
>
> - waiting on <no object reference
> available><monitor://%3cno%20object%20reference%20available%3e>
>
> at org.apache.tomcat.util.net
> .NioEndpoint$NioSocketWrapper.fillReadBuffer(NioEndpoint.java:1325)
>
> - locked <0x000000050f48a720><monitor://%3c0x000000050f48a720%3e>
> (a java.util.concurrent.Semaphore)
>
> at org.apache.tomcat.util.net
> .NioEndpoint$NioSocketWrapper.read(NioEndpoint.java:1226)
>
> at
> org.apache.coyote.http11.Http11InputBuffer.fill(Http11InputBuffer.java:805)
>
> at
> org.apache.coyote.http11.Http11InputBuffer.access$400(Http11InputBuffer.java:42)
>
> at
> org.apache.coyote.http11.Http11InputBuffer$SocketInputBuffer.doRead(Http11InputBuffer.java:1185)
>
> at
> org.apache.coyote.http11.filters.IdentityInputFilter.end(IdentityInputFilter.java:151)
>
> at
> org.apache.coyote.http11.Http11InputBuffer.endRequest(Http11InputBuffer.java:655)
>
> at
> org.apache.coyote.http11.Http11Processor.endRequest(Http11Processor.java:1192)
>
> at
> org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:439)
>
> at
> org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
>
> at
> org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:890)
>
> at org.apache.tomcat.util.net
> .NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1743)
>
> at org.apache.tomcat.util.net
> .SocketProcessorBase.run(SocketProcessorBase.java:49)
>
> - locked <0x000000050f48a730><monitor://%3c0x000000050f48a730%3e>
> (a org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper)
>
> at
> org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
>
> at
> org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
>
> at
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
>
> at java.lang.Thread.run(java.base@17.0.3/Thread.java:833)
>
>
> I’m suspecting a slow network. Does anybody have another idea?
>
>
> Thanks, Christoph
>