APAR status
Closed as program error.
Error description
This fixes some admin code, as they're currently displaying
the PID of a LinuxThread (really a LWP Lightweight Process).
There is a way to obtain it (Jared Jurkiewicz, figured out a
way), and this should be fixed in the 5.0.X stream's
cumulative fixpack approach (ASV502 tree)
The overall PID much more useful than any of the Linuxthread
LWP PID's.
Local fix Problem summary
****************************************************************
* USERS AFFECTED: WebSphere Application Server Users on Linux *
****************************************************************
* PROBLEM DESCRIPTION: When process.id() is called, the PID *
* returned is that of the current *
* thread, not of the overall process. *
****************************************************************
* RECOMMENDATION: *
****************************************************************
When process.id() is called, the PID returned is that of the
current thread, not of the overall process. The overall PID is
much more useful than any of the LinuxThread LWP PIDs.
Problem conclusion
Problem was corrected by writing an adaptive varient of
getpid() that can correctly determine the main process ID,
regardlesss of the underlying threading model (NPTL,
LinuxThreads, et al). The code is Linux specific,
and is only used by the Linux built version of
libWs50ProcessManagement.so.
Temporary fix Comments
APAR information |
APAR number |
PQ78479 |
Reported component name |
WAS BASE 5.0 |
Reported component ID |
5630A3600 |
Reported release |
00I |
Status |
CLOSED PER |
PE |
NoPE |
HIPER |
NoHIPER |
Special Attention |
NoSpecatt |
Submitted date |
2003-09-15 |
Closed date |
2004-04-29 |
Last modified date |
2004-04-29 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
Publications Referenced
Applicable component levels |
R00I PSY |
UP |
|