JDK-4852638 : [1.4.1_01-b01] Core dumps within 5 min with 7.0 EE App server
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 1.4.1_01
  • Priority: P1
  • Status: Closed
  • Resolution: Duplicate
  • OS: solaris_8
  • CPU: sparc
  • Submitted: 2003-04-23
  • Updated: 2003-06-19
  • Resolved: 2003-06-19
Related Reports
Duplicate :  
Description
While running iMM application with EE app server and 1.4.1_01-b01 JDK we get core dumps withing 5 mins.

Here is the stack trace :
t@20 (l@20) terminated by signal ABRT (Abort)
0xfe29d998: __lwp_kill+0x0008:  bgeu,a  __lwp_kill+0x1c
(/usr/dist/pkgs/forte_dev,v6.2/SUNWspro/bin/../WS6U2/bin/sparcv9/dbx) where
current thread: t@20
=>[1] __lwp_kill(0x0, 0x6, 0x0, 0xfe2ba000, 0x7ce, 0x0), at 0xfe29d998
  [2] raise(0x6, 0x0, 0x729fdaa8, 0x0, 0x103598, 0x729fdbc0), at 0xfe24c804
  [3] abort(0x0, 0x729fdb38, 0x0, 0xfffffff8, 0x0, 0x729fdb61), at 0xfe2357
b0
  [4] os::abort(0x1, 0xfd9c35f8, 0x729fe3c0, 0xfd96adb0, 0xfd96ad4e, 0xff00
), at 0xfd8809c0
  [5] report_error(0x729fe3d8, 0xea4, 0xfd9db884, 0xe8, 0xfd90af8c, 0xfd90c
963), at 0xfd78c89c
  [6] PhaseCFG::DFS(0x0, 0x0, 0x978ec0, 0x2a, 0x729ff454, 0x0), at 0xfd5153
60
  [7] PhaseCFG::DFS(0x1, 0x6f00a0, 0x6f00a0, 0x28, 0x14, 0x1c), at 0xfd5154
3c
  [8] PhaseCFG::DFS(0x1, 0x6f0190, 0x6f0190, 0x26, 0xfd986000, 0x97bfd5), a
t 0xfd51543c
  [9] PhaseCFG::DFS(0x1, 0x6f0280, 0x6f0280, 0x24, 0x14, 0x97c395), at 0xfd
51543c
  [10] PhaseCFG::DFS(0x1, 0x6f031c, 0x6f031c, 0x22, 0x14, 0x1c), at 0xfd515
43c
  [11] PhaseCFG::DFS(0x1, 0x6f0410, 0x6f0410, 0x20, 0xfd986000, 0x1c), at 0
xfd51543c
  [12] PhaseCFG::DFS(0x1, 0x6f04ac, 0x6f04ac, 0x1e, 0x0, 0x11d28fd), at 0xf
d51543c
  [13] PhaseCFG::DFS(0x1, 0x6f05f0, 0x6f05f0, 0x1c, 0x0, 0x0), at 0xfd51543
c
  [14] PhaseCFG::DFS(0x1, 0x6f068c, 0x6f068c, 0x1a, 0x729ff454, 0x0), at 0x
fd51543c
  [15] PhaseCFG::DFS(0x1, 0x979538, 0x979538, 0x19, 0x14, 0x1c), at 0xfd515
43c
  [16] PhaseCFG::DFS(0x1, 0x6f07c4, 0x6f07c4, 0x18, 0xfd986000, 0x97bfd5),
at 0xfd5153dc
  [17] PhaseCFG::DFS(0x1, 0x6f08b4, 0x6f08b4, 0x16, 0x14, 0x97c395), at 0xf
d51543c
  [18] PhaseCFG::DFS(0x1, 0x6f0950, 0x6f0950, 0x14, 0x14, 0x1c), at 0xfd515
43c
  [19] PhaseCFG::DFS(0x1, 0x0, 0x6f0a44, 0x12, 0xfd986000, 0x1c), at 0xfd51
543c
  [20] PhaseCFG::DFS(0x1, 0x6f0c08, 0x6f0c08, 0x10, 0x0, 0x11d28fd), at 0xf
d51543c
  [21] PhaseCFG::DFS(0x1, 0x6f0ca4, 0x6f0ca4, 0xe, 0x0, 0x0), at 0xfd51543c
  [22] PhaseCFG::DFS(0x1, 0x6ef4b0, 0x6ef4b0, 0xc, 0x729ff454, 0x0), at 0xf
d51543c
  [23] PhaseCFG::DFS(0x1, 0x6ef5f4, 0x6ef5f4, 0x8, 0x14, 0x1c), at 0xfd5154
3c
  [24] PhaseCFG::DFS(0x1, 0x978534, 0x978534, 0x7, 0xfd986000, 0x97bfd5), a
t 0xfd51543c
  [25] PhaseCFG::DFS(0x1, 0x6ef6d0, 0x6ef6d0, 0x4, 0x14, 0x97c395), at 0xfd
51543c
  [26] PhaseCFG::DFS(0x1, 0x978b00, 0x978b00, 0x3, 0x14, 0x1c), at 0xfd5154
3c
  [27] PhaseCFG::DFS(0x1, 0x8f8ffc, 0x8f8ffc, 0x2, 0xfd986000, 0x1c), at 0x
fd5153dc
  [28] PhaseCFG::DFS(0x0, 0x0, 0x8f8cd0, 0x1, 0x0, 0x11d28fd), at 0xfd51543
c
  [29] PhaseCFG::Dominators(0x11d28f4, 0x0, 0xfd9cdf70, 0x0, 0x0, 0x0), at
0xfd5e6144
  [30] Compile::Code_Gen(0x729ff540, 0x729ff314, 0x729ff454, 0x52c368, 0x72
9ff454, 0x0), at 0xfd5e7aa8
  [31] Compile::Compile(0xec1d14, 0x612384, 0x0, 0x7cf0a8, 0xffffffff, 0x1)
, at 0xfd617410
  [32] C2Compiler::compile_method(0x98360, 0x729ffd38, 0x0, 0x7cf0a8, 0xfff
fffff, 0x0), at 0xfd613e2c
  [33] CompileBroker::invoke_compiler_on_method(0x26b, 0x0, 0xffffffff, 0x4
d5ecc, 0xfd9c5074, 0x4d5e40), at 0xfd61366c
  [34] CompileBroker::compiler_thread_loop(0x4d5e40, 0x4d5e40, 0x48a9c8, 0x
4d63e0, 0x301d38, 0xfd6841b0), at 0xfd6cb3e0
  [35] JavaThread::run(0x4d5e40, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfd6841d8
  [36] _start(0x4d5e40, 0x0, 0x0, 0x0, 0x0, 0x0), at 0xfd680624


###@###.### 2003-04-23
###@###.### 2003-04-23

Comments
EVALUATION ###@###.### 2003-04-25 This may be a duplicate of 4682728. I've added the path to a webrev in its suggested fix section. It is also possible that this occurs due to unverified bytecodes, several similar problems were helped by using -verify on the command-line. Please confirm status with 1.4.2_beta. -----
11-06-2004