Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Jetty QueuedThreadPool warnings in logs when running junit tests

See original GitHub issue

WireMock 2.4.1

when runnning junit tests using wiremock, I see some random jetty warnings in the logs :

2017-01-06 17:49:27,788 -  INFO - org.eclipse.jetty.server.ServerConnector : Stopped ServerConnector@3dd1dc90{HTTP/1.1}{0.0.0.0:8080}
2017-01-06 17:49:27,788 -  INFO - o.e.jetty.server.handler.ContextHandler  : Stopped o.e.j.s.ServletContextHandler@320de594{/,null,UNAVAILABLE}
2017-01-06 17:49:27,788 -  INFO - o.e.jetty.server.handler.ContextHandler  : Stopped o.e.j.s.ServletContextHandler@3e7634b9{/__admin,null,UNAVAILABLE}
2017-01-06 17:49:27,789 -  WARN - o.e.jetty.util.thread.QueuedThreadPool   : qtp2116179210{STOPPING,8<=8<=10,i=8,q=7} Couldn't stop Thread[qtp2116179210-22,5,]
2017-01-06 17:49:27,790 -  WARN - o.e.jetty.util.thread.QueuedThreadPool   : qtp2116179210{STOPPING,8<=8<=10,i=2,q=7} Couldn't stop Thread[qtp2116179210-23,5,]
2017-01-06 17:49:27,790 -  WARN - o.e.jetty.util.thread.QueuedThreadPool   : qtp2116179210{STOPPING,8<=8<=10,i=0,q=6} Couldn't stop Thread[qtp2116179210-26,5,]

is this a known issue ? is there a clean way to avoid theses warnings, without setting the log level in logback.xml ?

Issue Analytics

State:
Created 7 years ago
Comments:5

Top GitHub Comments

3reactions

lehcimcommented, Jan 13, 2017

Currently I’m using the following settings in a logback-test.xml which is used only when runnnig tests.

<!-- for wiremock standard jar -->
<logger name="org.eclipse.jetty.util.thread.QueuedThreadPool" level="ERROR" />
<!-- for wiremock standalone shaded jar -->
<logger name="wiremock.org.eclipse.jetty.util.thread.QueuedThreadPool" level="ERROR" />

Of course, there is also a lockback.xml without these settings for production runs.

2reactions

adamtuppercommented, Jan 12, 2017

Hi, I’m getting the same kind of problem where I receive anywhere between approximately 1 - 4 “Couldn’t stop thread” warnings, i.e. [main] QueuedThreadPool WARN qtp1983025922{STOPPING,8<=8<=10,i=0,q=1} Couldn't stop Thread[qtp1983025922-12,5,] Is there any solution to this other than suppressing the warnings? I’m not too keen on doing this.