IREL Throws Core Dump From Java Binary
Last updated on SEPTEMBER 21, 2016
Applies to:Oracle Communications Billing and Revenue Management - Version: 184.108.40.206.1 to 220.127.116.11.1 - Release: 6.5.0 to 7.3.1
HP 9000 HP-UX 11.0 (32 bit)
Checked for relevance on 22-Oct-2008
IREL dumped core and Program terminating with signal 11, Segmentation fault.
pin_rel is pointing to the Java binary which is in $PIN_HOME/bin/java and the version is:
java version "1.4.1.01"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1.01-030304-15:40)
Java HotSpot(TM) Server VM (build 1.4.1 1.4.1.01-030304-17:08-PA_RISC2.0 PA2.0, mixed mode)
While loading EDR data using IREL, the first file picked up caused a core dump.
The gdb debugger output is not providing enough assistance.
opt/portal/6.5/vf_pinb/apps/pin_rel/0.0.0.2/MMS/core: Permission denied.
> /home/vf_dev/langtools/bin/gdb /opt/portal/6.5/vf_pinb/bin/java /opt/portal/6.5/vf_pinb/apps/pin_rel/0.0.0.2/MMS/core
HP gdb 2.1
Copyright 1986 - 1999 Free Software Foundation, Inc.
Hewlett-Packard Wildebeest 2.1 (based on GDB 5.0-hpwdb-20000630)
Wildebeest is free software, covered by the GNU General Public License, and
you are welcome to change it and/or distribute copies of it under certain
conditions. Type "show copying" to see the conditions. There is
absolutely no warranty for Wildebeest. Type "show warranty" for details.
Wildebeest was built for PA-RISC 1.1 or 2.0 (narrow), HP-UX 11.00.
Core was generated by 'java'.
Program terminated with signal 11, Segmentation fault.
#0 0xd94f3418 in ?? ()
#0 0xd94f3418 in ?? ()
#1 0xd94f33f8 in ?? ()
Cannot access memory at address 0x6ff884d8
(gdb) p 0xd94f3418
$1 = 3645846552
(gdb) p 0xd94f33f8
$2 = 3645846520
There were no changes to JRE/JDK from the default installation
The core file is from the Java binary and also there are no error messages which can
be associated with the core in the IREL's log files.
copy of vf_pinb/irel_failure_log
2005/01/22 05:35.41 IRELPMMS failed with Error 1
2005/01/22 05:37.43 IRELPTVR failed with Error 1
2005/01/22 05:39.44 IRELPIUM failed with Error 1
2005/01/22 05:41.27 IRELPGS2 failed with Error 1
2005/01/22 05:41.27 IRELPBMD failed with Error 1
2005/01/22 05:54.46 IRELPGS3 failed with Error 1
2005/01/24 05:59.52 IRELPMMS failed with Error 139
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