Thanks for looking into this. Here are the responses to your queries
can you provide the Weblogic server version used ?
PK: WL 12.2.1.4.0
is there a security policy in place ? If yes, has it been modified from the defaults ?
PK: Yes, There is the default weblogic security policy used as a Java option. WL_HOME/wlserver/server/lib/weblogic.policy
if you are using -javaagent setup option, could you try the CLI attach once the server has started to see if the symptom persists ? If using the CLI attach method works, then it means we might have a rather easy work-around by delaying the agent start.
PK: I added the delay_agent_premain_ms=10000 key to elasticapm.properties and restarted the Java process and still see the errors.
By looking at the log4j-api jar path : /nas/apps/bea/applications/i04PME2/lib/log4j-api.jar, can we conclude this dependency is part of the i04PME2 webapp which is a deployed from a war/ear ? If no, is that a kind of "shared lib directory" for the whole Weblogic instance ?
PK: That is right. Its a shared library used by all war/ear deployed on the application servers.