OWS (Oracle Watchlist Screening) Crashes And Restarts Throwing "Klass::external_name()" Error In Thread Dumps (OEDQ)
(Doc ID 2253923.1)
Last updated on FEBRUARY 06, 2019
Applies to:
Oracle Watchlist Screening - Version 11.1.1.7.3 and laterInformation in this document applies to any platform.
Symptoms
Watchlist Screening crashes and the server automatically re-starts. The diagnostic log will show:
#### <[ACTIVE] ExecuteThread: '189' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <[ServletContext@1227514541[app:edq module:/edq path:null spec-version:3.0]] Servlet failed with an IOException.
java.io.IOException: Connection reset by peer
java.io.IOException: Connection reset by peer
A thread dump will show a SIGSEV error:
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f27ac30296b, pid=22782, tid=139694494840576
#
# JRE version: Java(TM) SE Runtime Environment (7.0_76-b13) (build 1.7.0_76-b13)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.76-b04 mixed mode linux-amd64 )
# Problematic frame:
# V [libjvm.so+0x71d96b] Klass::external_name() const+0x1b
#
# SIGSEGV (0xb) at pc=0x00007f27ac30296b, pid=22782, tid=139694494840576
#
# JRE version: Java(TM) SE Runtime Environment (7.0_76-b13) (build 1.7.0_76-b13)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.76-b04 mixed mode linux-amd64 )
# Problematic frame:
# V [libjvm.so+0x71d96b] Klass::external_name() const+0x1b
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |