Beware the JVM arguments!

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
Comments:

Hi, The parameters are also used if you use a Node Manager. If you use a Node Manager and set StartScriptEnabled to false in nodemanager.properties parameters set in the shell scrips will not be set. Regards Peter

Posted by Peter Lorenzen on May 19, 2011 at 10:25 AM CLT #

Hi Peter,

Yes, that's right. If you set StartScriptEnabled to false in nodemanager.properties parameters then the parameters set in setDomainEnv.sh or setDomainEnv.cmd will not be set. However, if you hardcode properties in startManagedWebLogic.sh or startManagedWebLogic.cmd they keep being set, no matter the value of StartScriptEnabled.

Thank you so much for your comment, it's a very interesting fact to keep in mind.

-Cris

Posted by Cristóbal Soto on June 30, 2011 at 06:43 AM CLT #

Post a Comment:
  • HTML Syntax: NOT allowed
About


Principal Technical Support Engineer in the Exalogic Enterprise Support Team (EEST).

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today