Bug 63405 - Tomcat EXCEPTION_ACCESS_VIOLATION - Problematic frame tcnative-1.dll+0x802e
Summary: Tomcat EXCEPTION_ACCESS_VIOLATION - Problematic frame tcnative-1.dll...
Status: NEW
Alias: None
Product: Tomcat Native
Classification: Unclassified
Component: Library (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
Depends on:
Reported: 2019-05-06 04:55 UTC by kd
Modified: 2019-07-18 03:51 UTC (History)
0 users

Tomcat crash error file (110.60 KB, text/plain)
2019-05-06 04:55 UTC, kd

Note You need to log in before you can comment on or make changes to this bug.
Description kd 2019-05-06 04:55:04 UTC
Created attachment 36571 [details]
Tomcat crash error file


During application performance testing on Tomcat, Tomcat crashed multiple times with EXCEPTION_ACCESS_VIOLATION error as follows. PFA error file generated after crash.

# A fatal error has been detected by the Java Runtime Environment:
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000018000802e, pid=97772, tid=0x000000000000c740
# JRE version: OpenJDK Runtime Environment (8.0_192-b01) (build 1.8.0_192-b01)
# Java VM: OpenJDK 64-Bit Server VM (25.192-b01 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# C  [tcnative-1.dll+0x802e]
# Core dump written. Default location: D:\nice_systems\RTServer\Tomcat\hs_err_pid97772.mdmp
# If you would like to submit a bug report, please visit:
#   http://www.azulsystems.com/support/
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
Comment 1 Mark Thomas 2019-06-20 13:42:48 UTC
Could you please provide your connector configuration and a description of the requests being sent at the time. It is particularly helpful to know what type(s) of requests were being used (WebSocket, Comet, sendfile, static files, servlets, etc.)

Without a test case we can use to reproduce this, we need to narrow down the volume of code we need to manually inspect to try and figure out what the root cause is.
Comment 2 kd 2019-07-17 09:53:59 UTC

<?xml version='1.0' encoding='utf-8'?>
<Server port="8005" shutdown="SHUTDOWN">
  <Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" />
  <Listener className="org.apache.catalina.core.JasperListener" />
  <Listener className="org.apache.catalina.core.JreMemoryLeakPreventionListener" />
  <Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener" />
  <Listener className="org.apache.catalina.core.ThreadLocalLeakPreventionListener" />

    <Resource name="UserDatabase" auth="Container"
              description="User database that can be updated and saved"
              pathname="conf/tomcat-users.xml" />
  <Service name="Catalina">
  <Connector port="7077" protocol="HTTP/1.1"
               maxThreads="1000" connectionTimeout="20000"
               server="Web" />
	<Connector port="7078" protocol="org.apache.coyote.http11.Http11AprProtocol"
               maxThreads="1000" connectionTimeout="20000" scheme="https" secure="true"
               server="Web" />
    <Engine name="Catalina" defaultHost="localhost">
      <Realm className="org.apache.catalina.realm.LockOutRealm">
        <Realm className="org.apache.catalina.realm.UserDatabaseRealm"
      <Host name="localhost"  appBase="webapps"
            unpackWARs="true" autoDeploy="true">

REST API were invoked at the time of crash.
We also use Websocket for client server communication.
Please let me know if you need more details.