I did threaddump right after first connection timeout:
"dw-35-acceptor-0@112c3f5b-application@7d755813{HTTP/1.1}{0.0.0.0:80}" -
Thread t@35
java.lang.Thread.State: RUNNABLE
at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)
at
sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:422)
at
sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:250)
- locked <65c2ec4d> (a java.lang.Object)
at
org.eclipse.jetty.server.ServerConnector.accept(ServerConnector.java:377)
at
org.eclipse.jetty.server.AbstractConnector$Acceptor.run(AbstractConnector.java:500)
at
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
at
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
at java.lang.Thread.run(Thread.java:745)
Locked ownable synchronizers:
- None
"dw-34-acceptor-1@7c35910e-application@7d755813{HTTP/1.1}{0.0.0.0:80}" -
Thread t@34
java.lang.Thread.State: BLOCKED
at
sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:233)
- waiting to lock <65c2ec4d> (a java.lang.Object) owned by
"dw-35-acceptor-0@112c3f5b-application@7d755813{HTTP/1.1}{0.0.0.0:80}" t@35
at
org.eclipse.jetty.server.ServerConnector.accept(ServerConnector.java:377)
at
org.eclipse.jetty.server.AbstractConnector$Acceptor.run(AbstractConnector.java:500)
at
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
at
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
at java.lang.Thread.run(Thread.java:745)
Locked ownable synchronizers:
- None
On Thursday, June 9, 2016 at 10:19:05 AM UTC+2, Thomas wrote:
>
> Hello,
>
> while load testing of my server with jmeter(100 threads, ramp-up period 0)
> I'll get 1% failures with connections timeouts. I set 20000 millis for
> connection 60000 millis for response. More than enough to process a simple
> request. It looks like, if all threads are busy then dropwizard stops
> accepting new connections.
>
> However, all servlets use async context and all processing is done in
> non-blocking manner. So large number of connections could be accepted by
> the server. I'm still debugging to be sure that no blocking calls happen in
> application code. But my question is, what is recommended config for async,
> non-blocking servlets? Shall I explicitly enable non-blocking mode?
>
> I'm using dropwizard 0.9.2 with the following config
>
> server:
> gzip:
> bufferSize: 8KiB
> minThreads: 32
> applicationConnectors:
> - type: http
> port: 80
> acceptorThreads: 2
> selectorThreads: 4
> outputBufferSize: 8KiB
>
> Thanks for your help!
>
>
--
You received this message because you are subscribed to the Google Groups
"dropwizard-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
