Following André suggestion I replaced the connector protocols, both for HTTP and AJP ports, to force NIO.2. Now Tomcat is working for seven hours without any problem.
My findings until now are: 1. It is not a Tomcat related problem, WildFly 10 has the same behavior. The WildFly high CPU threads also calls sun.nio.ch.WindowsSelectorImpl$SubSelector.poll0(Native Method). 2. When switching from NIO to NIO.2 the problem goes away. 3. It seems clearly a Java 8 for Windows problem that happens in several versions. I tested 1.8.0_66, 1.8.0_71 and 1.8.0_77. 4. Perhaps the problem is related to Windows 2008 R2 or VMWare ESXi. On a Windows 10 machine it works like a charm. 5. I cannot imagine what triggered the problem, no change in WIndows or ESX was made. The only thing that changed was that some new applications were installed when the problem started to show, but after that I removed all the applications. In the case of WildFly no application was never started. I'll try to fill a bug in the Oracle site if there is not any other suggestion. Thanks again to all. Josep 2016-04-13 17:06 GMT+02:00 Josep M Beleta <bel...@carver-as.com>: > I'll try it. Thanks a lot. > > 2016-04-13 15:24 GMT+02:00 André Warnier (tomcat) <a...@ice-sa.com>: > >> On 13.04.2016 13:55, Josep M Beleta wrote: >> >>> > >Could I find a workaround? >>>> >>> >> Maybe for the meantime, you could try another Connector protocol ? >> http://tomcat.apache.org/tomcat-8.5-doc/config/http.html#Common_Attributes >> -> protocol >> >> Note: I am not an expert, and not sure that in this particular case it >> would help. >> But it is very quickly done, and it may provide some additional insight >> into the issue. >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> >> >
