On Mar 4, 2014 2:49 AM, "Dmitry Batiyevskiy" <dmitry.batiyevs...@ardas.dp.ua> wrote: > > Howard, > My connector config is the following (i've already posted that): > > <Connector port="8443" maxHttpHeaderSize="8192" > maxThreads="15000" > enableLookups="false" disableUploadTimeout="true" > acceptCount="100" scheme="https" secure="true" > SSLEnabled="true" > compression="off" > SSLCertificateFile="/opt/tomcat/mycompany.com.crt" > SSLCertificateKeyFile="/opt/tomcat/mycompany.com.key" /> >
Okay, thanks. > Also -Dhttps.protocols=TLSv1 option is passed to java machine > > The reason for me to use apr connector is https performance, isn't NIO much > slower in that? > Chris recommended NIO. I'll let him answer your question. > Regards, > > Dmitry Batiyevskiy > > Ardas Group Inc. > > www.ardas.dp.ua > > > 2014-03-04 2:04 GMT+02:00 Howard W. Smith, Jr. <smithh032...@gmail.com>: > > > On Mon, Mar 3, 2014 at 11:22 AM, Christopher Schultz < > > ch...@christopherschultz.net> wrote: > > > > > Dmitry, > > > > > > On 3/3/14, 6:06 AM, Dmitry Batiyevskiy wrote: > > > > Can you advice how we can find the problem in app/environment like > > > > this? What are possible ways to debug this? > > > > > > Honestly, I'd try switching to the NIO connector and resume your > > > testing. If all is well, it may point to a bug in the APR connector > > > and/or tcnative itself. If you are having similar problems with the > > > pure-Java connectors, then the problem is likely something you are > > > doing in your application that is causing an invalid state. You'll > > > probably get better information from the Java stack trace than from an > > > assertion-failure. > > > > > > Give that a try and let us know how things go. > > > > > > +1 Chris > > > > I have found much /continued/ success using NIO connector across tomcat and > > atmosphere versions. > >
