Thursday, March 20, 2014

weblogic startup.properties

I was trying desperately to pass an argument to the JVM:
-Dweblogic.security.SSL.ignoreHostnameVerification=true
by setting it in the JAVA_OPTIONS in the DOMAIN_HOME/bin/startManagedWebLogic.sh
Much to my dismay, the MS - started via NM with "usestartscript=true", would always come up with the same property=false.
After hours of grepping and swearing, I found out that in the domain_home/servers/AdminServer/data/nodemanager/startup.properties this value was set to false. this was overriding my settings. The same setting was in the startup.properties of every MS, but it was overwritten at startup, so no point in changing it.

http://docs.oracle.com/cd/E13222_01/wls/docs92/server_start/nodemgr.html#wp1101026
"Node Manager uses the startup.properties file to determine the startup and configuration when starting a server. This file is defined for each server instance and is located in:

domain_home/servers/server_name/data/nodemanager/startup.properties "

"Each Managed Server instance has its own startup.properties file with properties that control how Node Manager starts up and controls the server. Node Manager automatically creates this file by using properties passed to Node Manager when the Administrative Server was last used to start the server. This allows a Node Manager client or startup scripts to restart a Managed Server using the same properties last used by the Administrative Server. "


Once you change the startup.properties of the Admin, remember to restart the NM.

No comments: