| [jetty-users] SSLEngineImpl initHandshaker Internal error |
Hi jetty-users,
We are seeing a frightening warning in our log files:
2016-12-21T19:09:10.959Z WARN <> [qtp294008652-57110] o.e.j.util.thread.QueuedThreadPool -
java.lang.IllegalStateException: Internal error
at sun.security.ssl.SSLEngineImpl.initHandshaker(SSLEngineImpl.java:470)
at sun.security.ssl.SSLEngineImpl.readRecord(SSLEngineImpl.java:1007)
at sun.security.ssl.SSLEngineImpl.readNetRecord(SSLEngineImpl.java:907)
at sun.security.ssl.SSLEngineImpl.unwrap(SSLEngineImpl.java:781)
at javax.net.ssl.SSLEngine.unwrap(SSLEngine.java:624)
at org.eclipse.jetty.io.ssl.SslConnection$DecryptedEndPoint.fill(SslConnection.java:525)
at org.eclipse.jetty.server.HttpConnection.fillRequestBuffer(HttpConnection.java:325)
at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:233)
at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)
at org.eclipse.jetty.io.ssl.SslConnection.onFillable(SslConnection.java:202)
at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:273)
at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:95)
at org.eclipse.jetty.io.SelectChannelEndPoint$2.run(SelectChannelEndPoint.java:93)
at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.executeProduceConsume(ExecuteProduceConsume.java:303)
at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.produceConsume(ExecuteProduceConsume.java:148)
at org.eclipse.jetty.util.thread.strategy.ExecuteProduceConsume.run(ExecuteProduceConsume.java:136)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:671)
at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:589)
at java.lang.Thread.run(Thread.java:745)
2016-12-21T19:09:10.960Z WARN <> [qtp294008652-57110] o.e.j.util.thread.QueuedThreadPool - Unexpected thread death: org.eclipse.jetty.util.thread.QueuedThreadPool$2@6792928d in qtp294008652{STARTED,10<=38<=1000,i=11,q=0}
This is happening periodically on many of our servers.
I found a couple of references online, it seems that Netty had a race condition
that caused this once upon a time: https://groups.google.com/forum/#!topic/netty/e-wS0tMjWow
Obviously it's entirely possible (or even likely) that it is one of our clients that is broken,
but I am not sure how to track this down. Trying to pick apart a TLS conversation with Wireshark
doesn't appeal much to me, and this happens way before we get records like request logs.
openjdk version "1.8.0_111"
OpenJDK Runtime Environment (build 1.8.0_111-8u111-b14-3~14.04.1-b14)
OpenJDK 64-Bit Server VM (build 25.111-b14, mixed mode)
Jetty 9.3.11.v20160721
Anybody got any ideas how we might track this down? Any chance it's actually a bug in Jetty?
Thanks in advance,
Steven
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail