Monday 23 May 2011

Tweaking Node manager

I faced really a hard time to start the managed server from node manager. My installation is quite simple,

  1. I downloaded Oracle VM from http://www.oracle.com/technetwork/server-storage/virtualbox/downloads/index.html and installed the same with extension pack.
  2. I installed OEL 5 on VM.
  3. Then I installed Oracle Database 11gR2 and SOA suite 11.1.1.5 on top of that on single machine.
  4. Everything went fine and able to start the weblogic server as well as all the managed server successfully.
  5. Then I tried to start the managed server from node manager and its got erroring out!

Yes, my node manager is reachable from admin server, but I’m getting something strange error in soa_server1.out file,”JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)”.I checked the Linux firewall and disabled the same but it persists.After wasting some more time I figured out I need to change some java property in setDomainEnv.sh file(Thanks to Google!),by default it was

if [ "${debugFlag}" = "true" ] ; then
    JAVA_DEBUG="-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=${DEBUG_PORT},server=y,suspend=n -Djava.compiler=NONE"

I changed to

if [ "${debugFlag}" = "true" ] ; then
    JAVA_DEBUG="-Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8000,server=y,suspend=n -Djava.compiler=NONE"

After changing the Java Debugging Interface binding address it started working Smile

Here is my nodemanager.properties file,

#Sun May 22 03:56:09 PDT 2011
DomainsFile=/u01/app/oracle/product/fmw/wlserver_10.3/common/nodemanager/nodemanager.domains
LogLimit=0
PropertiesVersion=10.3
DomainsDirRemoteSharingEnabled=false
javaHome=/u01/app/oracle/product/fmw/jdk160_24
AuthenticationEnabled=true
NodeManagerHome=/u01/app/oracle/product/fmw/wlserver_10.3/common/nodemanager
JavaHome=/u01/app/oracle/product/fmw/jrockit_160_24_D1.1.2-4/jre
LogLevel=INFO
DomainsFileEnabled=true
StartScriptName=startWebLogic.sh
ListenAddress=
NativeVersionEnabled=true
ListenPort=5556
LogToStderr=true
SecureListener=true
LogCount=1
DomainRegistrationEnabled=false
StopScriptEnabled=true
QuitEnabled=false
LogAppend=true
StateCheckInterval=500
CrashRecoveryEnabled=false
StartScriptEnabled=true
LogFile=/u01/app/oracle/product/fmw/wlserver_10.3/common/nodemanager/nodemanager.log
LogFormatter=weblogic.nodemanager.server.LogFormatter
ListenBacklog=50

And other important rules for configuring node managers,

  1. In Node Manager listener address of Admin server don’t ever set ‘localhost’ either provide machine IP address or FQDN.
  2. Your node manager should be reachable from admin server.
  3. Whatever the managed server you want to start from node manager, put boot.properties file under security folder of your server.It contains the credentials,
  4. #Sun May 22 06:31:16 PDT 2011
    password=welcome1
    username=weblogic

1 comment:

Anonymous said...

This is not a requirement or pre-req to start nodemanager. I think this is more of a work around and the actual root cause might be something else.