Technote
(troubleshooting)Cause The Javaâ„¢ Virtual Machine that is included with IBM WebSphere Application Server is unable to link to the libic_jni.a file that is included with WebSphere Commerce. This can occur for the following reasons:
UnsatisfiedLinkError for the libic_jni.a file when running the WebSphere Commerce configuration manager Problem(Abstract) Run the config_server.sh command immediately fails with the following error:
java.lang.UnsatisfiedLinkError: WC_installDir/bin/libic_jni.a: load ENOEXEC on shared library(s) WC_installDir/bin/libic_jni.a
- The Java Virtual Machine is a 64-bit version. WebSphere Commerce does not support a 64-bit Java Virtual Machine. The libic_jni.a file that is included with WebSphere Commerce is a 32-bit version. The command fails because the Java binary that the command is attempting to connect to is the 64-bit version.
- The libic_jni.a file is corrupted. You can validate this library by issuing the following command:
$ dump -ov WC_installDir/bin/libic_jni.a
Verify that the result of this command has returned the object module header, that an 'EXEC' flag is listed in this header, and that it contains a valid magic number. For example:
Flags=(EXEC DYNLOAD SHROBJ )
..
Magic = 0x1df (32-bit XCOFF)
If the output does not contain a formatted header, 'EXEC' is not listed in 'Flags' section, or the Magic number does not indicate 32-bit, then the libic_jni.a file is invalid. Resolving the problem
- If you are using the 64-bit version of WAS, uninstall the 64-bit version, and reinstall the 32-bit edition.
- If the libic_jni.a file is corrupted. Reinstall WebSphere Commerce, or any APARs (fix packs) that were installed immediately before this error occurred. If a reinstallation does not resolve this problem, contact IBM Support.
Document Information Current web document: http://www.ibm.com/support/docview.wss?uid=swg21288863