Skip to main content

Summary This article clarifies a possible reason for Artix 5.5 it_container crash
Article Number 32182
Environment Artix 5.5 JAX-RPC Linux-Redhat 5.5
Question/Problem Description Artix 5.5 it_container crash
Artix 5.5 it_container core dump generating JVM crash report.


Stack trace from generated core file:

Program terminated with signal 6, Aborted.
#0 0x00000030e0e30265 in raise () from /lib64/libc.so.6
(gdb) where
#0 0x00000030e0e30265 in raise () from /lib64/libc.so.6
#1 0x00000030e0e31d10 in abort () from /lib64/libc.so.6
#2 0x00002aaaacf7f637 in os::abort(bool) () from /usr/java/jre/lib/amd64/server/libjvm.so
#3 0x00002aaaad0d2cf8 in VMError::report_and_die() () from /usr/java/jre/lib/amd64/server/libjvm.so
#4 0x00002aaaad0d3871 in crash_handler(int, siginfo*, void*) () from /usr/java/jre/lib/amd64/server/libjvm.so
#5 <signal handler called>
#6 0x00002aaaacf7cc06 in os::is_first_C_frame(frame*) () from /usr/java/jre/lib/amd64/server/libjvm.so
#7 0x00002aaaad0d1a91 in VMError::report(outputStream*) () from /usr/java/jre/lib/amd64/server/libjvm.so
#8 0x00002aaaad0d2bd5 in VMError::report_and_die() () from /usr/java/jre/lib/amd64/server/libjvm.so
#9 0x00002aaaacf85fe5 in JVM_handle_linux_signal () from /usr/java/jre/lib/amd64/server/libjvm.so
#10 0x00002aaaacf8230e in signalHandler(int, siginfo*, void*) () from /usr/java/jre/lib/amd64/server/libjvm.so
#11 <signal handler called>
#12 0x00002aaaad592d09 in from_c_str(IT_JNI_Utils::JNIEnvUtil*, char const*) ()
from /opt/artix/5.5.0/cxx_java/shlib/libit_jni_util_gcc34.so.5
#13 0x00002aaaad592f75 in IT_JNI_Utils::JNIString::JNIString(IT_JNI_Utils::JNIEnvUtil*, IT_Bus::String const&) ()
from /opt/artix/5.5.0/cxx_java/shlib/libit_jni_util_gcc34.so.5
#14 0x00002aaac027eb6a in IT_JNI_Bus::JNIServer::dispatch(IT_Bus::ServerOperation&) ()
from /opt/artix/5.5.0/cxx_java/shlib/libit_bus_jni_gcc34.so.5
#15 0x00002adc8314e3a3 in IT_Bus::ServantWrapper::dispatch(IT_Bus::ServerOperation&) ()
from /opt/artix/5.5.0/cxx_java/shlib/libit_bus_gcc34.so.5
#16 0x00002aaac1e9fdcb in IT_Bus::SoapInterceptor::intercept_around_dispatch(IT_Bus::ServerOperation&) ()
from /opt/artix/5.5.0/cxx_java/shlib/libit_soap_gcc34.so.5
#17 0x00002aaaac643a54 in IT_Bus::ServerEndpointHandlerImpl::message_received(IT_Bus::AnyType*, IT_Bus::ReceiveMessageContext*) () from /opt/artix/5.5.0/cxx_java/shlib/libit_messaging_port_gcc34.so.5
#18 0x00002aaaac63f224 in IT_Bus::ServerEndpointImpl::message_received(IT_Bus::BinaryBuffer&, IT_Bus::DispatchInfo&) ()
from /opt/artix/5.5.0/cxx_java/shlib/libit_messaging_port_gcc34.so.5
#19 0x00002aaaac645c47 in IT_Bus::DispatchContextImpl::execute() ()
from /opt/artix/5.5.0/cxx_java/shlib/libit_messaging_port_gcc34.so.5
#20 0x00002aaaac649044 in IT_Bus::MessagingTransportCallbackImpl::dispatch(IT_Bus::BinaryBuffer&, IT_Bus::DispatchInfo&, bool) () from /opt/artix/5.5.0/cxx_java/shlib/libit_messaging_port_gcc34.so.5
#21 0x00002aaaaac2f3ca in IT_HTTP::ArtixHTTPService::do_post(IT_ATLI2_HTTP::InputStream*, IT_ATLI2_HTTP::OutputStream*) ()
from /opt/artix/5.5.0/cxx_java/shlib/libit_at_http_gcc34.so.5
#22 0x00002aaaaac2c16c in IT_HTTP::ArtixHTTPService::service_request(IT_ATLI2_HTTP::InputStream*, IT_ATLI2_HTTP::OutputStream*) () from /opt/artix/5.5.0/cxx_java/shlib/libit_at_http_gcc34.so.5
#23 0x00002aaaabd7d3a7 in IT_ATLI2_HTTP::HTTPDispatchInterceptorImpl::recv(IT_WebIOP::InputStream*, IT_WebIOP::OutputStream*) () from /opt/artix/5.5.0/cxx_java/shlib/libit_http_gcc34.so.5
#24 0x00002aaaabd645bc in IT_ATLI2_HTTP::HTTPConnectionHandlerImpl::dispatch_request(IT_ATLI2_HTTP::HTTPInputStream*) ()
from /opt/artix/5.5.0/cxx_java
Clarifying Information
Error Message JVM crash report containing: # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00002aaaad592d09, pid=30664, tid=1979808064 # # JRE version: 6.0_26-b03 # Java VM: Java HotSpot(TM) 64-Bit Server VM (20.1-b02 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libit_jni_util_gcc34.so.5 0x6d09] from_c_str(IT_JNI_Utils::JNIEnvUtil*, char const*) 0x29
Defect/Enhancement Number
Cause This crash is caused by a lack of memory in the JVM. The indication for this is that the application receives  "GC overhead limit exceeded" exceptions and the JVM crash dump shows a couple of heap regions, eden space and object space, are used up as shown in the below extract:

---------------  P R O C E S S  ---------------

VM state:at safepoint (normal execution)

VM Mutex/Monitor currently owned by a thread:  ([mutex/lock_event])
[0x00000000058f92e0] Threads_lock - owner thread: 0x00000000059c4de0
[0x00000000058f97e0] Heap_lock - owner thread: 0x00002aac029f4c30

Heap
 PSYoungGen      total 129024K, used 110592K [0x00000000f7000000, 0x0000000100000000, 0x0000000100000000)
  eden space 110592K, 100% used [0x00000000f7000000,0x00000000fdc00000,0x00000000fdc00000)
  from space 18432K, 0% used [0x00000000fee00000,0x00000000fee00000,0x0000000100000000)
  to   space 18432K, 0% used [0x00000000fdc00000,0x00000000fdc00000,0x00000000fee00000)
 ParOldGen       total 245760K, used 245756K [0x00000000e8000000, 0x00000000f7000000, 0x00000000f7000000)
  object space 245760K, 99% used [0x00000000e8000000,0x00000000f6fff030,0x00000000f7000000)
 PSPermGen       total 147456K, used 33985K [0x00000000df000000, 0x00000000e8000000, 0x00000000e8000000)
  object space 147456K, 23% used [0x00000000df000000,0x00000000e1130650,0x00000000e8000000)
Resolution Increase the memory for the JVM heap.

If the Artix log level is set to
    event_log:filters = ["*=FATAL ERROR"];
increase the Artix log level to include at least WARNING level as shown below, this provides more details necessary to investigate such a crash:
event_log:filters = ["*=FATAL ERROR WARNING"];

If the crash is reproducible, the Artix log level should be set to
    event_log:filters = ["*=*"];

Provide the new Artix log files together with the JVM crash dumps and stack traces from the generated core file to Micro Focus Customer Support.
Workaround
Notes
Attachment

Created date: 29 May 2012
Last Modified: 13 February 2013
Last Published: 29 May 2012
First Published date: 29 May 2012

#KnowledgeDocs
#Orbix