Thanks for the reply. I am using "org.apache.coyote.http11.Http11AprProtocol" in Tomcat 9.
The NIO connectors worked fine when we tried them, but the native ones seem to start up, but then don’t work. Interestingly, we found out that these connectors do eventually start working! We tried to connect a few hours later and they were working fine. We are now trying to determine exactly how long it takes for them to accept connections in hopes that this will help us figure out what is going on. Having a way to debug this better would be helpful. Mark Claassen Senior Software Engineer Donnell Systems, Inc. 130 South Main Street Leighton Plaza Suite 375 South Bend, IN 46601 E-mail: mailto:mclaas...@ocie.net Voice: (574)232-3784 Fax: (574)232-4014 Disclaimer: The opinions provided herein do not necessarily state or reflect those of Donnell Systems, Inc.(DSI). DSI makes no warranty for and assumes no legal liability or responsibility for the posting. -----Original Message----- From: Roger Brechbühl <rotscher...@gmail.com> Sent: Wednesday, October 31, 2018 5:25 PM To: Tomcat Users List <users@tomcat.apache.org> Subject: Re: Debugging tomcat native connector with which connector do you have problems? nio, nio2 or apr? I ask because we have problems with nio2-openssl when ssl session is reused e.g. when a request is proxied with nginx. kind regards, Roger Mark A. Claassen <mclaas...@ocie.net> schrieb am Mi. 31. Okt. 2018 um 15:32: > Is there a way to debug the native connectors? Specifically, we are > having some problems getting the native openssl connector working on Ubuntu. > Doing an strace on the process shows a lot of FUTEX_WAIT_PRIVATE, but > we don't know why. We were hoping that there was some way to get more > information. > > Thanks, > > Mark Claassen > Senior Software Engineer > > Donnell Systems, Inc. > 130 South Main Street > Leighton Plaza Suite 375 > South Bend, IN 46601 > E-mail: mailto:mclaas...@ocie.net > Voice: (574)232-3784 > Fax: (574)232-4014 > > Disclaimer: > The opinions provided herein do not necessarily state or reflect those > of Donnell Systems, Inc.(DSI). DSI makes no warranty for and assumes > no legal liability or responsibility for the posting. > >
