|
Quick Lists
|
|
Bug ID:
|
4545731
|
|
Votes
|
1
|
|
Synopsis
|
JVM 1.3.1 hang : thread deadlock (SIGSEGV)
|
|
Category
|
java:runtime
|
|
Reported Against
|
1.3.1_01
|
|
Release Fixed
|
|
|
State
|
11-Closed,
Will Not Fix,
bug
|
|
Priority:
|
4-Low
|
|
Related Bugs
|
|
|
Submit Date
|
03-DEC-2001
|
|
Description
|
This is a libthread issue. When the customer switched to the alternative
libthread and using jdk1.3.1_02 the hang does not appear. Also using their
original configuration, which was jdk1.3.1_01 with the default libthread for
Solaris 8 (T1), and using -XX:+UseBoundThreads the hang cannot be reproduced.
The customer has accepted and feels more comfortable with the boundthreads
workaround and is unwilling to persue this further.
xxxxx@xxxxx 2001-12-17
Servlet engine using Oracle jdbc causes JVM 1.3.1 to hang on heavy load.
truss, dbx and pstack during the hang show thread deadlocks. It is not
possible to make a thread dump.
Information provided in attachment :
- pstack output during hang
- truss 1min before and after the hang
- showrev -p
- prtdiag of the system
- dbx stacks of several threads
Other information available :
- gcore of the jvm during the hang.
|
|
Work Around
|
1) -XX:+UseBoundThreads
or
2) alternative libthread: export LD_LIBRARY_PATH=/usr/lib/lwp
jdk1.3.1_02
-XX:+OverrideDefaultLibthread
|
|
Evaluation
|
JPSE
This is a libthread issue. When the customer switched to the alternative
libthread and using jdk1.3.1_02 the hang does not appear. Also using their
original configuration, which was jdk1.3.1_01 with the default libthread for
Solaris 8 (T1), and using -XX:+UseBoundThreads the hang cannot be reproduced.
The customer has accepted and feels more comfortable with the boundthreads
workaround and is unwilling to persue this further.
xxxxx@xxxxx 2001-12-17
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
 |