GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Java app threading problem on HP-UX
Operating System - HP-UX
1847211
Members
7542
Online
110263
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
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
10-23-2001 02:37 AM
10-23-2001 02:37 AM
Java app threading problem on HP-UX
Hello, I am using an application using Weblogic and Java on a HP9000N and I am getting some deadlocking problem (but only on HP-UX). I am trying to localize the origine of the problem (Java?, Weblogic?, our application?) and for the moment I suspect it could be a threading problem in the JVM itself.
The reason why I believe this is that when I try to request the JVM for a thread dump (Sending a SIGQUIT to the JVM process) it works usually well except when the locking happen.
Do you know if the thread dump request should always work or if there are situations where it is expected that the JVM will not answer the SIGQUIT?
I am also asking myself if this could be related to PHKL_24943 which has been recently called back (but which apparently was made to solve some threading problems).
Thanks for your help.
Regards,
Gilles.
The reason why I believe this is that when I try to request the JVM for a thread dump (Sending a SIGQUIT to the JVM process) it works usually well except when the locking happen.
Do you know if the thread dump request should always work or if there are situations where it is expected that the JVM will not answer the SIGQUIT?
I am also asking myself if this could be related to PHKL_24943 which has been recently called back (but which apparently was made to solve some threading problems).
Thanks for your help.
Regards,
Gilles.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-23-2001 03:15 AM
10-23-2001 03:15 AM
Re: Java app threading problem on HP-UX
PHKL_24943 has come with a warning in which inactive threads can become corrupt, where when called again can cause system panic. I've attached the exact email from hp for the exact lingo. I have been told that it has been a rare occurrance, so I believe it to be a judgement call on your part. I have delayed installing it and instead kept 22504 and others like 22589, 22568, etc.
Hope this helps
Chris
Hope this helps
Chris
It wasn't me!!!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-23-2001 04:15 AM
10-23-2001 04:15 AM
Re: Java app threading problem on HP-UX
I agree about PHKL_24943, I got the same warning from HP.
It is why I was also asking myself if the fact that I was not able to get a thread dump from the JVM could also have been a clue...
Have you tried the JVM thread dump? (by doing kill -3 JVM_PROCESS_NUMBER). If yes, did it work always reliably? Or has it the tendancy do not give any result for a yes or for a no?? (Because if it is a reliable tool then I would really suspect that something strange is happening).
Thanks again for your help,
Gilles.
It is why I was also asking myself if the fact that I was not able to get a thread dump from the JVM could also have been a clue...
Have you tried the JVM thread dump? (by doing kill -3 JVM_PROCESS_NUMBER). If yes, did it work always reliably? Or has it the tendancy do not give any result for a yes or for a no?? (Because if it is a reliable tool then I would really suspect that something strange is happening).
Thanks again for your help,
Gilles.
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 2026 Hewlett Packard Enterprise Development LP