Container not starting in Apple Silicon Sonoma 14.3.x version but worked fine in 14.2.x - JVMJ9VM011W Unable to load j9jit29

[shivaperumalsamy]

Hi,

this is a mac version specific issue, the same container worked fine in Sonoma 14.2.x but not in 14.3.x version. the error is
JVMJ9VM011W Unable to load j9jit29: /opt/IBM/WebSphere/AppServer/java/8.0/jre/lib/amd64/compressedrefs/libj9jit29.so

2024-02-20 08:41:16 Starting server ................... 2024-02-20 08:41:20 ADMU0116I: Tool information is being logged in file 2024-02-20 08:41:20 /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1/startServer.log 2024-02-20 08:41:24 ADMU0128I: Starting tool with the AppSrv01 profile 2024-02-20 08:41:24 ADMU3100I: Reading configuration for server: server1 2024-02-20 08:41:47 ADMU0111E: Program exiting with error: java.lang.UnsatisfiedLinkError: 2024-02-20 08:41:47 Ws60ProcessManagement 2024-02-20 08:41:47 (/opt/IBM/WebSphere/AppServer/lib/native/linux/x86_64/libWs60ProcessManagement.so: 2024-02-20 08:41:47 cannot enable executable stack as shared object requires: Invalid 2024-02-20 08:41:47 argument) 2024-02-20 08:41:47 ADMU1211I: To obtain a full trace of the failure, use the -trace option. 2024-02-20 08:41:47 ADMU0211I: Error details may be seen in the file: 2024-02-20 08:41:47 /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/server1/startServer.log 2024-02-20 08:41:54 WASX7357I: By request, this scripting client is not connected to any server process. Certain configuration and application operations will be available in local mode. 2024-02-20 08:42:11 WASX7303I: The following options are passed to the scripting environment and are available as arguments that are stored in the argv variable: "[/work/config-ibm/webContainer.props]"

has anyone faced this issue. workaround will be much appreciated. thanks in advance.

[mingcyu]

Hi there, please see this thread: docker/for-mac#7180

This was an issue caused by Apple's emulation. It seems to have been fixed in MacOS 14.4