Many Thanks Mark for the super quick response. More details inline.

On Fri, Mar 29, 2019 at 1:21 PM Mark Thomas <ma...@apache.org> wrote:

> On 29/03/2019 01:40, Inder wrote:
>
> <snip/>
>
> > INFO: Server version:
> > INFO: Server built:          unknown
> > INFO: Server number:         8.5.x
>
> That doesn't look like a standard Tomcat build. What version of Tomcat
> is this / is this based on?
>
> Its 8.5.20

> > INFO: Loaded APR based Apache Tomcat Native library [1.2.14] using APR
> > version [1.4.8].
>
> Those are quite old. There is a fix that may be relevant to APR poll
> behaviour in APR 1.6.4.
>
> OK... will consider upgrading or moving to NIO Connector. Do you see any
issue or comparable dis-advantage of using NIO connector?


> > INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters
> > [false], random [true].
> > INFO: APR/OpenSSL configuration: useAprConnector [true], useOpenSSL
> [true]
> > INFO: OpenSSL successfully initialized [OpenSSL 1.0.2k-fips  26 Jan 2017]
>
>
> > Mar 15, 2019 7:59:35 AM org.apache.coyote.AbstractProtocol init
> > INFO: Initializing ProtocolHandler ["http-apr-8081"]
> > Mar 15, 2019 7:59:35 AM org.apache.coyote.AbstractProtocol init
> > INFO: Initializing ProtocolHandler
> > ["https-openssl-apr-0:0:0:0:0:0:0:0-8443"]
>
> What is the connector configuration here?
>
  <Listener className="org.apache.catalina.core.AprLifecycleListener"
useAprConnector="true" SSLEngine="on" />

    <Connector
           protocol="HTTP/1.1"
           port="8443" maxThreads="200" address="::"
           scheme="https" secure="true" SSLEnabled="true"
           SSLCertificateFile="/usr/Systems/APACHE/conf/ssl.crt/server.crt"

 SSLCertificateKeyFile="/usr/Systems/APACHE/conf/ssl.key/server.key"
           SSLVerifyClient="none" clientAuth="false" SSLProtocol="TLSv1"
           SSLCipherSuite="ALL:!ADH:!RC4:+HIGH:+MEDIUM:!LOW:!SSLv2:!EXPORT"
           URIEncoding="UTF-8" />


>
> > After some troubleshooting, we found that when this happens, Java worker
> > threads are idle and waiting for tasks, while sockets are in ESTABLISHED
> > and CLOSE_WAIT state. All the TCP sockets at the OS level indicate they
> > have bytes in the TCP buffer that is not been read by the application.
> > so looks like something went wrong, and the APR connector library is no
> > more reading from the socket, or some issue between java socket Acceptor
> > call and APR library.
>
> What is the CPU utilisation like at this point?
>
Didn't take much note of that. Will check the next time issue happens.

>
> > Has anyone encountered any problem like this or have any suggestion on
> what
> > should be checked that may help to isolate the problem.
>
> Possibly:
> https://tomcat.markmail.org/thread/4wdcgluibejormye

Thanks... Looks like I hit into the same issue. I think if I change the
Connector configuration to use NIO, I should not hit into this issue.
Any idea what causes the issue above? Is that some race condition scenario?

>
>
> > "https-openssl-apr-0:0:0:0:0:0:0:0-8443-Poller" #404 daemon prio=5
> > os_prio=0 tid=0x00007fe938168320 nid=0x2991 runnable [0x00007fe661063000]
> >    java.lang.Thread.State: RUNNABLE
> >         at
> > org.apache.tomcat.util.net.AprEndpoint$Poller.run(AprEndpoint.java:1642)
> >         at java.lang.Thread.run(Thread.java:748)
>
> This is consistent with the problem described above.
>
> It looks like a Tomcat upgrade to at least 8.5.30 should address this. I
> recommend the latest 8.5.x
>
> OK... Will consider the upgrade. Many Thanks again for the quick inputs
and pointers.


> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Reply via email to