JVM Crashes While Running Index Task For Korean Locale Collection (Doc ID 2181329.1)

Last updated on SEPTEMBER 26, 2016

Applies to:

Oracle Knowledge - Version 8.6 and later
Information in this document applies to any platform.

Symptoms

JVM crashes every time while running Index task on a Korean Locale collection. We are using JAVA 1.7.0_79 and Tomcat 7.0.67.

[660204 Local Workclient-default-taskrun (400)] Indexing document http://support-itb.com/kb/MA1195&actp=search&viewlocale=ko_KR: 366 of 394 from collection ko_KR_im_Manuals completed in 9 milliseconds.
[660205 Local Workclient-default-taskrun (400)] Status: Indexing: 367 of 394. Failed: 0
[660206 Local Workclient-default-taskrun(457)] Event(Code=FORWARD_INDEX_PROCESS_DOCUMENT, id=#23B230I457P400) started at 8/5/16 7:05 PM: Indexing document [id: 367, Fetch URL im:repo/MANUALS/live/146018802ef2505c01238338939a02903#classic_160GB_User_Guide_KH.pdf] in Collection ko_KR_im_Manuals.
[660207 Local Workclient-default-taskrun (457)] Obtained content from collection name ko_KR_im_Manuals document 367
[660208 Local Workclient-default-taskrun (457)] UNKNOWN MESSAGE ID "{0}" called with: "Sentence factory: com.inquira.nlp.factory.OLTSentenceFactory@6375ae6c"

[682602 Local Workclient-default-taskrun (468)] UNKNOWN MESSAGE ID "{0}" called with: "Sentence factory: com.inquira.nlp.factory.OLTSentenceFactory@6375ae6c"
[682603 Local Workclient-default-taskrun (468)] UNKNOWN MESSAGE ID "{0}" called with: "Initializing OLTIQSentence :ë§Œë³´ê³„ì„¤ì •ì„ì‚¬ìš©ìží™”í•˜ë ¤ë©´, 1 기타메뉴에서,ì²´ë ¥ê´€ë¦¬ë¥¼ì„ íƒí•˜ê³ ì„¤ì •ì„ì„ íƒí•˜ì‹­ì‹œì˜¤."
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007ff27bb3e9ec, pid=29282, tid=140679444560192
#
# JRE version: Java(TM) SE Runtime Environment (7.0_79-b15) (build 1.7.0_79-b15)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (24.79-b02 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# C [libolt.so+0x2479ec] CanlMorphTrace::GetString(CanlLanguage const&) const+0x23c
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /ngs/app/fsnt/nu/bususrt/CRMBASE/Scopes/iknow/InQuira_8.5_Search/InQuira_8.5/instances/iknow/hs_err_pid29282.log
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
#
JVM received a signal UNKNOWN (6).
JVM process is gone.
JVM exited unexpectedly.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms