Oracle MVA

Tales from a Jack of all trades

WLS, nodemanager and

with 2 comments

It’s been a while since I blogged, been way to busy working on a couple of production systems. Anyway, while running an SR with Oracle about the nodemanager and some crash recovery issues  (a blog post will follow as soon as a solution is found) I ran into yet another documentation “feature”.

The Fusion Middleware documentation contains lots of “practices” (I wouldn’t call them best 🙂 ) which have little to do with the technical functioning of the product and everything to do with personel preferences (i.e. “it worked for me”). Some engineer setting up a fusion middleware environment for some customer and promoting his personal notes to be best practices is not the type of “Best Practice” or manual I would like to see from Oracle. A population of one (1) is not a valid sample for a “Best Practice”.

As an example, this part of documentation says:

Step 7: Define the Administration Server Address Make sure that a listen address is defined for each Administration Server that will connect to the Node Manager process. If the listen address for an Administration Server is not defined, when Node Manager starts a Managed Server it will direct the Managed Server to contact localhost for its configuration information.

I think this is incorrect because the nodemanager checks a file when it starts up a managed server. This file can be found at $DOMAIN_HOME/servers/$SERVER_NAME/data/nodemanager/ An example of this file from one of my testservers is:

#Server startup properties
#Sat Feb 05 10:41:39 CET 2011\=true\=true -Xmanagement\:ssl\=false,authenticate\=false,port\=7091\\=file\:/dev/./urandom\=/u01/app/oracle/user_projects/domains/base_domain/config/fmwconfig/jps-config.xml -Xms5g -Xmx5g -XXtlaSize\:min\=2k,preferred\=512k -XXcompaction\:percentage\=20\=true -Dweblogic.ReverseDNSAllowed\=false

It contains the AdminURL ( resolves to the AdminServer of my test setup). This property file is setup upon first startup of the managed server. When you boot the managed server this leads to the following startup parameter for the jvm (found in the .out file of the managed server):

So I don’t agree that the managed server checks localhost if the AdminServer has no listen-address. I think that line in de docs should be corrected as a documentation error (at best it’s incomplete)

When you learn more about the, you also know that the statement that you should always need to use the script to start the AdminServer after domain creation is false. Yes you get an error when you start the AdminServer from the nodemanager if it’s the first time you boot this AdminServer, but if you manually create the file and optionally the (if you run in production mode) you can start the AdminServer from WLST (which helps when you script your deployments).

hope this helps.


Written by Jacco H. Landlust

February 7, 2011 at 11:23 pm

2 Responses

Subscribe to comments with RSS.

  1. There’s a WLST method you can call to generate the based on config.xml – it’s called nmGenBootStartupProps()

    Amjad Ashkar

    March 22, 2011 at 7:32 pm

    • Hi Amjad, thanks for your reply.

      The nmGenBootStartupProps only works if you are connected to the AdminServer. So you cannot generate the and file for the AdminServer itself. For other managed servers you can use this command. Thanks for mentioning the option though.

      Jacco H. Landlust

      April 5, 2011 at 9:17 pm

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: