HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Java SDK & JRE error (application coring)
Operating System - HP-UX
1828685
Members
2205
Online
109984
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-21-2001 03:24 AM
03-21-2001 03:24 AM
Java SDK & JRE error (application coring)
When I downloaded and installed SDK 1.2.07 from this site, I added /opt/java1.2/bin to the path and tried to execute 'java' -- and got the following error:
#
# Java version:
# HotSpot VM (1.0.1fcs, mixed mode, PA2.0 build 1.2.2.07-00/12/08-PA_RISC2.0)
#
# HotSpot Virtual Machine Error, Unexpected Signal 11
#
# occurred at pc=c0192a2c
# Error ID: /CLO/Components/JAVA_HOTSPOT/Src/build/hp-ux/../../src/os/hp-ux/vm/os_hp-ux.cpp, 2998
#
ABORT instruction (core dumped)
Has anyone gotten this error before? I absolutely cannot figure out what the problem is.
The machine is a HP A500, running HPUX 11.11 (OS installed previous to delivery). Any suggestions would be warmly welcomed.
Thanks!
#
# Java version:
# HotSpot VM (1.0.1fcs, mixed mode, PA2.0 build 1.2.2.07-00/12/08-PA_RISC2.0)
#
# HotSpot Virtual Machine Error, Unexpected Signal 11
#
# occurred at pc=c0192a2c
# Error ID: /CLO/Components/JAVA_HOTSPOT/Src/build/hp-ux/../../src/os/hp-ux/vm/os_hp-ux.cpp, 2998
#
ABORT instruction (core dumped)
Has anyone gotten this error before? I absolutely cannot figure out what the problem is.
The machine is a HP A500, running HPUX 11.11 (OS installed previous to delivery). Any suggestions would be warmly welcomed.
Thanks!
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-21-2001 04:30 AM
03-21-2001 04:30 AM
Re: Java SDK & JRE error (application coring)
Hi,
Im not sure of what is going on since Im not a java specialist at all..., but I just had to install a JDK 1.1.8.05 because a dba asked me to instal JRE 1.1.8 2 days before and it hasnt solved their install of OA problem. So I suggest that you install also the JRE that goes with your JDK version, the other thing I think of is to set all your java env in a script and load from the script in order to not have path, classpath... problems if you still have /opt/java (java 1.X) that doenst work the same way as /opt/java1.2 (java 2)
Just thoughts....
All the best
Victor
Im not sure of what is going on since Im not a java specialist at all..., but I just had to install a JDK 1.1.8.05 because a dba asked me to instal JRE 1.1.8 2 days before and it hasnt solved their install of OA problem. So I suggest that you install also the JRE that goes with your JDK version, the other thing I think of is to set all your java env in a script and load from the script in order to not have path, classpath... problems if you still have /opt/java (java 1.X) that doenst work the same way as /opt/java1.2 (java 2)
Just thoughts....
All the best
Victor
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-20-2001 06:05 AM
06-20-2001 06:05 AM
Re: Java SDK & JRE error (application coring)
You will more than likely need to tune the kernel when it comes to java. nproc and nkthreads are common ones required to increase.
strings the core file to see where it's coring out. or better yet use q4 if you have it installed.
Later,
Bill
strings the core file to see where it's coring out. or better yet use q4 if you have it installed.
Later,
Bill
It works for me (tm)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-02-2002 04:50 AM
02-02-2002 04:50 AM
Re: Java SDK & JRE error (application coring)
Here's are the kernel, etc. tuning params that had worked for me:
The max_thread_proc parameter set to at least 1024. Change the default value of 64 to 1024 (or higher).
The maxfiles and maxfiles_lim parameters set to at least 4096. The limit for both parameters is 60,000. However, the sam (System Administration Manager) program will not allow a value above 2048 without the following changes to the file /usr/conf/master.d/core-hpux:
Change *range maxfiles<=2048 to *range maxfiles<=60000
Change *range maxfiles_lim<=2048 to *range maxfiles_lim<=60000
The following parameters are set to values at least as large as the following:
maxuprc 512
nproc 1024
nflocks 8192
ninode 2048
nfile 4 * ninode
msgseg 32767 (or less)
msgmnb 65 535
msgmax 65 535
msgtql 1024
msgmap 258
msgmni 256
msgssz 16
semmni 512
semmap 514
semmns 1024
semmnu 1020 (nproc value minus 4)
shmmax 268 435 456 (see below)
shmseg 16
shmmni 300
As to the shmmax parameter, ensure that it is set to 134217728 or 90% of the physical memory (in bytes), whichever is higher
HP recommended Tuning:
Addressing FIN_WAIT2, FIN, LAST_ACK problems:
We'd like to test tuning the FIN_WAIT kernel parameter for sticking ports.
Command-
ndd -get /dev/tcp tcp_status (to get the status before the next change)
ndd -set /dev/tcp tcp_fin_wait_2_timeout 600000
ndd -get /dev/tcp tcp_status (to get the status before the next change)
ndd -set /dev/tcp tcp_fin_wait_2_timeout 600000
HP Patch Additions:
PHCO_17556 Oracle Recommended
PHCO_17792 Oracle Recommended
PHCO_18229 Oracle Recommended
PHCO_19666 ksleep fix
PHKL_19169 Required fix to PHKL_18543(apply after), Required for PHKL_17038, VxFS fix
PHKL_14750 Oracle Recommended
PHKL_17038 Required fix to PHKL_18543(apply after), dependency for 18543, data paging fix
PHKL_18543 sigtimewait fix
PHKL_20016 Required for PHKL_17038, Multi CPU fix
PHKL_20202 HP recommended companion to PHCO_19666, ksleep fix
PHKL_21392 Required for PHKL_17038, VxFS fix
PHKL_20674 Required for PHKL_17038, VxFS fix
PHKL_22562 kwakup fix
PHNE_19616 Oracle Recommended
PHSS_16849 Oracle Recommended
PHSS_17535 Oracle Recommended
PHSS_18066 Oracle Recommended
PHSS_18649 Oracle Recommended
PHSS_20544 Oracle Recommended
PHSS_17508 Oracle Recommended
PHSS_17691 Oracle Recommended
PHSS_17870 Oracle Recommended
(As of January 2001 there are superceeding patch requirements and I havc them for the HP9000/800 HPUX 11.0 series at work [but unfortunately not here at the moment]). They deal with MUTEX and thread locking/sleeping issues.
-Dan
The max_thread_proc parameter set to at least 1024. Change the default value of 64 to 1024 (or higher).
The maxfiles and maxfiles_lim parameters set to at least 4096. The limit for both parameters is 60,000. However, the sam (System Administration Manager) program will not allow a value above 2048 without the following changes to the file /usr/conf/master.d/core-hpux:
Change *range maxfiles<=2048 to *range maxfiles<=60000
Change *range maxfiles_lim<=2048 to *range maxfiles_lim<=60000
The following parameters are set to values at least as large as the following:
maxuprc 512
nproc 1024
nflocks 8192
ninode 2048
nfile 4 * ninode
msgseg 32767 (or less)
msgmnb 65 535
msgmax 65 535
msgtql 1024
msgmap 258
msgmni 256
msgssz 16
semmni 512
semmap 514
semmns 1024
semmnu 1020 (nproc value minus 4)
shmmax 268 435 456 (see below)
shmseg 16
shmmni 300
As to the shmmax parameter, ensure that it is set to 134217728 or 90% of the physical memory (in bytes), whichever is higher
HP recommended Tuning:
Addressing FIN_WAIT2, FIN, LAST_ACK problems:
We'd like to test tuning the FIN_WAIT kernel parameter for sticking ports.
Command-
ndd -get /dev/tcp tcp_status (to get the status before the next change)
ndd -set /dev/tcp tcp_fin_wait_2_timeout 600000
ndd -get /dev/tcp tcp_status (to get the status before the next change)
ndd -set /dev/tcp tcp_fin_wait_2_timeout 600000
HP Patch Additions:
PHCO_17556 Oracle Recommended
PHCO_17792 Oracle Recommended
PHCO_18229 Oracle Recommended
PHCO_19666 ksleep fix
PHKL_19169 Required fix to PHKL_18543(apply after), Required for PHKL_17038, VxFS fix
PHKL_14750 Oracle Recommended
PHKL_17038 Required fix to PHKL_18543(apply after), dependency for 18543, data paging fix
PHKL_18543 sigtimewait fix
PHKL_20016 Required for PHKL_17038, Multi CPU fix
PHKL_20202 HP recommended companion to PHCO_19666, ksleep fix
PHKL_21392 Required for PHKL_17038, VxFS fix
PHKL_20674 Required for PHKL_17038, VxFS fix
PHKL_22562 kwakup fix
PHNE_19616 Oracle Recommended
PHSS_16849 Oracle Recommended
PHSS_17535 Oracle Recommended
PHSS_18066 Oracle Recommended
PHSS_18649 Oracle Recommended
PHSS_20544 Oracle Recommended
PHSS_17508 Oracle Recommended
PHSS_17691 Oracle Recommended
PHSS_17870 Oracle Recommended
(As of January 2001 there are superceeding patch requirements and I havc them for the HP9000/800 HPUX 11.0 series at work [but unfortunately not here at the moment]). They deal with MUTEX and thread locking/sleeping issues.
-Dan
Yes, a job can be less than what you make of it... :)
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP