APAR status
Closed as program error.
Error description
After applying WAS_ND fix pack 8.5.5.17 on 32_bit Java runtime, the following exception is observed in the SystemOut.log during startup for dmgr and nodeagents: NodeDetectCom E ASND0001E: Exception occured in nodedetect: java.lang.UnsatisfiedLinkError: com/ibm/ws/xd/nodedetect/unix/Uni xNodeDetector.getCpuInfo()V at com.ibm.ws.xd.nodedetect.unix.UnixNodeDetector.getNodeDetect Info (UnixNodeDetector.java:60) at com.ibm.ws.xd.nodedetect.NodeDetectInfoReader.getNodeDetectI nfo( NodeDetectInfoReader.java:41) at com.ibm.ws.xd.nodedetect.NodeDetectComponentImpl.getNodeDete ctIn fo(NodeDetectComponentImpl.java:282) at com.ibm.ws.xd.nodedetect.NodeDetectComponentImpl.publishNode Stats(NodeDetectComponentImpl.java:216) Exception is preceded by one or more of the following 32 bit lib missing refs: DCUT0003E: 32 bit native library ProcessCPU could not be loaded. Embedded Exception=ProcessCPU (Not found in java.library.path) DCUT0003E: 32 bit native library NodeDetect could not be loaded. Embedded Exception=NodeDetect (Not found in java.library.path) DCUT0003E: 32 bit native library NTNodeDetector could not be loaded. Embedded Exception=NTNodeDetector (Not found in java.library.path) DCUT0003E: 32 bit native library HeapDetect could not be loaded. Embedded Exception=HeapDetect (Not found in java.library.path) Example of corresponding FFDC exception: FFDC Exception:com.ibm.ws.xd.util.XDLibraryException SourceId:com.ibm.ws.xd.pmi.processcpu.ProcessCPU.<clinit> ProbeId:26 com.ibm.ws.xd.util.XDLibraryException: ProcessCPU (Not found in java.library.path) at com.ibm.ws.xd.util.XD.loadLibrary(XD.java:650) at com.ibm.ws.xd.util.XD.loadLibrary(XD.java:576) at com.ibm.ws.xd.pmi.processcpu.ProcessCPU.<clinit>(ProcessCPU. java:136)
Local fix
Use 64bit JDK
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server WAS ND edition 8.5.5.17 using a 32 * * bit run-time. * **************************************************************** * PROBLEM DESCRIPTION: ASND0001E exception occurred in * * NodeDetect' after applying 8.5.5.17 on * * WAS ND 32bit * **************************************************************** * RECOMMENDATION: * **************************************************************** After applying WAS_ND fix pack 8.5.5.17 on 32_bit Java runtime, the following exception is observed in the SystemOut.log during startup for dmgr and nodeagents: NodeDetectCom E ASND0001E: Exception occured in nodedetect: java.lang.UnsatisfiedLinkError: com/ibm/ws/xd/nodedetect/unix/Uni xNodeDetector.getCpuInfo()V at com.ibm.ws.xd.nodedetect.unix.UnixNodeDetector.getNodeDetect Info (UnixNodeDetector.java:60) at com.ibm.ws.xd.nodedetect.NodeDetectInfoReader.getNodeDetectInfo( NodeDetectInfoReader.java:41) at com.ibm.ws.xd.nodedetect.NodeDetectComponentImpl.getNodeDetectIn fo(NodeDetectComponentImpl.java:282) at com.ibm.ws.xd.nodedetect.NodeDetectComponentImpl.publishNodeStat s(NodeDetectComponentImpl.java:216) Exception is preceded by one or more of the following 32 bit lib missing refs: DCUT0003E: 32 bit native library ProcessCPU could not be loaded. Embedded Exception=ProcessCPU (Not found in java.library.path) DCUT0003E: 32 bit native library NodeDetect could not be loaded. Embedded Exception=NodeDetect (Not found in java.library.path) DCUT0003E: 32 bit native library NTNodeDetector could not be loaded. Embedded Exception=NTNodeDetector (Not found in java.library.path) DCUT0003E: 32 bit native library HeapDetect could not be loaded. Embedded Exception=HeapDetect (Not found in java.library.path) Example of corresponding FFDC exception: FFDC Exception:com.ibm.ws.xd.util.XDLibraryException SourceId:com.ibm.ws.xd.pmi.processcpu.ProcessCPU.<clinit> ProbeId:26 com.ibm.ws.xd.util.XDLibraryException: ProcessCPU (Not found in java.library.path) at com.ibm.ws.xd.util.XD.loadLibrary(XD.java:650) at com.ibm.ws.xd.util.XD.loadLibrary(XD.java:576) at com.ibm.ws.xd.pmi.processcpu.ProcessCPU.<clinit>(ProcessCPU.java :136)
Problem conclusion
In WebSphere Application Server Network Deployment fix pack 8.5.5.17 some 32 bit Intelligent Management libraries were not included, resulting in java.lang.UnsatisfiedLinkErrors when running 32 bit java run-times. The missing libraries have been properly repackaged for installation. The fix for this APAR is currently targeted for inclusion in fix pack 8.5.5.18. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PH23775
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2020-03-26
Closed date
2020-06-30
Last modified date
2020-06-30
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R850 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
01 November 2021