Hello,
A thread from a day or two ago mentioned a NPE in SecureNioChannel
when the connector is configured with Http11NioProtocol. OP mentioned
using Http11Nio2Protocol resolves the issue. I am also seeing this
exception and it is resolved by switching to the Nio2 protocol
implementation.
Is this a reasonable workaround until TC 8.5.6? Are there
dis/advantages to using Nio2 instead of Nio?
Thanks,
Colin
Ubuntu 12.04.5 LTS (GNU/Linux 3.0.0-32-virtual x86_64)
java version "1.8.0_101"
Tomcat 8.5.5
14-Sep-2016 17:26:44.052 SEVERE [https-jsse-nio-443-exec-9]
org.apache.coyote.AbstractProtocol$ConnectionHandler.process Error
reading request, ignored
java.lang.NullPointerException
at
org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.getSslSupport(NioEndpoint.java:1329)
at
org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:792)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1410)
at
org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
at java.lang.Thread.run(Thread.java:745)
<Connector port="8443" protocol="org.apache.coyote.http11.Http11NioProtocol"
maxThreads="150" SSLEnabled="true" scheme="https" secure="true" >
<SSLHostConfig>
<Certificate certificateKeystoreFile="my_keystore"
certificateKeystorePassword="my_password" />
</SSLHostConfig>
</Connector>
(Sorry I wasn't subscribed to the list so I can't reply to the original thread.)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
