In the last weeks I have had a bunch of Service Requests where a JVM argument ("-D" or "-X") is set as startup setting of a server on the WebLogic Server Administration Console, then the server is started up through the console (running a shell script) and the specified settings do not take effect.
This is an expected behavior because, according to the WebLogic lifecycle, the arguments set on the administration console (web) work only when the managed server is started up through the console. Arguments set on the shell script work for any way of start up.
So, keep this in mind:
- Set the JVM arguments on the startup script to make sure they will take effect
- Or if you set those parameters through the WebLogic Server Administration Console, then you should start the managed server using the console too instead of the startManagedWebLogic.sh, startManagedWebLogic.cmd or any other script