在Windows 10下的Eclipse下启动tomcat时获取EXCEPTION_ACCESS_VIOLATION

时间:2019-03-13 13:05:18

标签: java eclipse oracle

这一直在起作用。当然,我已经进行了更改,但是不知道错误消息指示的方向。

我有一个Java Spring Batch应用程序和一个Web应用程序,用于启动多个批处理作业中的任何一个。我在Eclipse Photon 4.8.0上运行Windows 10,Java 1.8和Tomcat 7.0.59。当我启动服务器时,控制台会通过“在2538毫秒内处理初始化”显示正常的INFO输出,然后

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x000000006d3130a2, pid=18012, tid=20820
#
# JRE version: Java(TM) SE Runtime Environment (8.0_51-b16) (build 1.8.0_51-b16)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.51-b03 mixed mode windows-amd64 compressed oops)
# Problematic frame:
# V  [jvm.dll+0x1430a2]
#
# Failed to write core dump. Minidumps are not enabled by default on client versions of Windows

并列出错误报告文件。在那里,我看到了一个堆栈转储,包括:

j  oracle.jdbc.driver.T2CConnection.t2cSetSessionTimeZone(JLjava/lang/String;)I+0
j  oracle.jdbc.driver.T2CConnection.logon()V+835
j  oracle.jdbc.driver.PhysicalConnection.<init>(Ljava/lang/String;Ljava/util/Properties;Loracle/jdbc/driver/OracleDriverExtension;)V+324
j  oracle.jdbc.driver.T2CConnection.<init>(Ljava/lang/String;Ljava/util/Properties;Loracle/jdbc/driver/OracleDriverExtension;)V+4
j  oracle.jdbc.driver.T2CDriverExtension.getConnection(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection;+34
j  oracle.jdbc.driver.OracleDriver.connect(Ljava/lang/String;Ljava/util/Properties;)Ljava/sql/Connection;+299
j  org.apache.tomcat.jdbc.pool.PooledConnection.connectUsingDriver()V+313
j  org.apache.tomcat.jdbc.pool.PooledConnection.connect()V+91
j  org.apache.tomcat.jdbc.pool.ConnectionPool.createConnection(JLorg/apache/tomcat/jdbc/pool/PooledConnection;Ljava/lang/String;Ljava/lang/String;)Lorg/apache/tomcat/jdbc/pool/PooledConnection;+55
j  org.apache.tomcat.jdbc.pool.ConnectionPool.borrowConnection(ILjava/lang/String;Ljava/lang/String;)Lorg/apache/tomcat/jdbc/pool/PooledConnection;+119
j  org.apache.tomcat.jdbc.pool.ConnectionPool.init(Lorg/apache/tomcat/jdbc/pool/PoolConfiguration;)V+554

我升级了Java的(次要)版本,并将服务器配置为运行该版本,但出现相同的错误。是否有人知道某种兼容性问题或引起这种问题的原因?

0 个答案:

没有答案