Migrate to Java Based Node Manager

Hi all ,
We are planning to migrate from script based node manager to Java based node manager . Can any one suggest the procedure or detailed steps in doing the same . If you have any documents then its really helpful .
thanks,
Kiran

Hi,
I couldn't find direct way of saying whether node manager is running or not but here is the work around. Using WLST when you say "startNodeManager", if the node manager is running this command throw an output saying "node manager is already running". Let me know if this solution works for you, if it works then I can give you java program for this if required or you can use "WLST JAVA Mode".
Thanks.
Vijay Bheemineni.

Similar Messages

Setting up the Script Based Node Manager

I noticed that someone has already asked this question from the Java side but I was wondering about the process for the node manager used for Solaris. I have been through the process in the documentation but I have yet to complete the dots to get a working nodemanager. The node manager starts up but then the admin console is unable to start down servers. I can shut a managed server down but I cannot bring it back up unless I physically (well virtually) log into each WLS and start them from the command line as root (yes, I have some servers running in privileged port ranges). I got it so when it starts, the servers switch users from root to my weblogic user. I just cant figure out the rest of the configuration.
Any feedback here?
Here is what I do:
1. Installed Weblogic and configured my domain.
2. I setup my SSL Trusts between boxes.
3. Set the weblogic nodemanger password and port.
4. Configured the nodemanager for each managed server in the console (I am totally unsure if I did this right or not).
5. Ran NMEnroll on all of my wls machines including the AdminServer.
6. Started the NodeManger on all machines.
7. Tested and was unable to control any of the managed servers from the console from a shutdown state.

I think I figured out whats going on. I think maybe I confused the two types of node managers. It appears to me that the way the script based one works is that you give it a command and then it uses a SSH shell connection to issue the command. Here is my case, I am on Solaris 10 and I have servers running on ports in the privileged range. I ran the test in the manual and it will not startup. The command works, but I am being stopped by the OS. How do you modify the script node manager to run as root over SSH when you need to sudo? I would normally consider setting up sudo to run without a password only for the weblogic server startup commands. However, I know in a production system the security folks would never permit this. Right now I can stop servers but I cannot start them remotely without manually SSHing in and using sudo to start the managed servers.

ALSB2.6/WLS9.2 Node Manager Monitoring Issue

Hi,
We have configured a java based node manager on weblogic 9.2 platform, using our customized scripts, for ALSB domain.
Node manager uses a customized server startup script to start the servers. This start-up script does some custom tasks and then starts the weblogic managed server with java options specified in this start-up script.
We are able to start / stop the managed servers from admin console but the node manager is not able to monitor the health of the managed servers. Node manager's log file also shows that server is in failed state whereas the managed servers log files show running state.
Can you please help how can we make the java based node manager (which uses a script to start the server) to monitor/check health of the managed server.
Also we've noticed a change in the way parameters are passed to server start-up script (which is called by the node manager ) between WLS8.1 and 9.2.
In 8.1 arguments were passed to the script in$1,$2,$3 and $4 ($4 pointing to the pid file of managed server). However these arguments are no longer available in 9.2.

I think when nodemanager.properties runs at the start of node manager, there is one line in it, i.e.
StartScriptName=startWeblogic.cmd
now there are few lines in the startWeblogic.cmd, those are:
@REM Set IP Mask.
if NOT "%NetMask%"=="" (
set IPMASK=%NetMask%
) else (
set IPMASK=
@REM Perform IP Migration if SERVER_IP is set by node manager.
if NOT "%SERVER_IP%"=="" (
call "%WL_HOME%\common\bin\wlsifconfig.cmd" -addif "%IFNAME%" "%SERVER_IP%" "%IPMASK%"
now I think that's why everytime the node manager tries to start the server the IP address is changed or masked to different one in startup.properties file, what I have mentioned in previous post...and what is indicated in log file...
any guru...plz

What is Node Manager ?

Hi
I have been reading documents on Oracle Fusion Middleware 11g. At lot of places 'Node Manager' is mentioned across these documents.
Please can someone explain here what is Node Manager and what it is its role in OFMW 11g ?
Cheers
Mayur

Hi Mayur,
For more details please refer to: http://weblogic-wonders.com/weblogic/2010/06/18/weblogic-initials/
 What is NodeManager?
A Node Manager process is not associated with a specific WebLogic domain but with a machine. Node Manager process to control server instances in any WebLogic Server domain until the server instances reside on the same machine as the Node Manager process.
Node Manager is a WebLogic Server utility that enables you to start, shut down, and restart Administration Server and Managed Server instances from a remote location. Although Node Manager is optional, it is recommended if your WebLogic Server environment hosts applications with high availability requirements.
A Node Manager process is not associated with a specific WebLogic domain but with a machine. You can use the same Node Manager process to control server instances in any WebLogic Server domain, as long as the server instances reside on the same machine as the Node Manager process.
Why We Need Nodemanagers?
1). It can Start, Shut Down, and Restart an Administration Server which has assigned a Machine.
2). It can Start, Shut Down, and Restart an Managed Server which has assigned a Machine.
3). It can Restart Administration and Managed Servers. (Crash Recovery of Servers is an Interesting feature)
4). It can be used to Monitor Servers and View Log Data
Types of NodeManagers?
*1). Java Based Nodemanager:* This can be used in Windiows as well as UNIX based Operating systems. Java Based Node Manager is not supported on Open VMS, OS/390, AS400, UnixWare, or Tru64 UNIX.
*2). Script Based Nodemanager:* This nodemanager can be used in UNIX based operating systems. The advantage of the script-based Node Manager is that it can remotely manage servers over a network that has been configured to use SSH.
For More Information on NodeManager please refer to:
http://download.oracle.com/docs/cd/E13222_01/wls/docs90/server_start/nodemgr.html
And
http://blogs.oracle.com/jamesbayer/2010/01/weblogic_nodemanager_quick_sta.html
Thanks
Jay SenSharma

Server state failed when starting through node manager

Hi,
I'm getting the below error while starting the managed server through node manager
<Sep 14, 2010 3:49:34 PM> <Warning> <Exception while starting server 'ms01': java.io.IOException: Server failed to start up. See server
output log for more details.>
java.io.IOException: Server failed to start up. See server output log for more details.
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:303)
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:542)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:119)
at weblogic.nodemanager.server.Handler.run(Handler.java:66)
at java.lang.Thread.run(Thread.java:619)
I have checked the server logs and it shows the below error code
./admin-stdout.log:<Sep 15, 2010 4:15:56 PM PDT> <Error> <NodeManager> <BEA-300048> <Unable to start the server ms01 : Exception while starting server 'ms01': java.io.IOException: Server failed to start up. See server output log for more details.>
I have also checked WebLogic documentation for BEA-300048. It says "Cause: The most likely cause is a configuration error in the Shell/SSH/RSH NodeManager configuration".
but I'm using Java based node manager
All this is coming up when I enable StartScriptEnabled to true in nodemanager.properties.
What could be reason for failure?

Hi.
If you are not using the latest service pack (sp2) please do so. If you are and are still seeing this
problem please open a case with support.
Thanks
Michael
Tim Dawson wrote:
I get this message whenever I try to use the console to start a managed server
on a remote system.
<Jan 12, 2002 8:18:26 AM PST> <Emergency> <WebLogicServer> <Unable to create a
server socket for: weblogic2.dev.wamnet.com/172.17.27.84, port: 7001. java.net.BindException:
Cannot assign requested address: JVM_Bind Perhaps the address weblogic2.dev.wamnet.com/172.17.27.84
is incorrect or another process is using port 7001.>
I've checked and checked and the only thing running on that box is the node manager!
The console will start a managed server on the local system (i.e. the system
that the admin server is running on) without any complaints.
Any ideas? Thanks,
Tim--
Michael Young
Developer Relations Engineer
BEA Support

Node Manager Not Reachable

Hi Everyone,
I'm very new to WebLogic, so I apologize if this is a dumb question.
I'm trying to install WebLogic as server for OBIEE. My environment is pretty simple. I have two Oracle Red Hat Linux 32-bit physical machines, let's call them WLS_SERVER and OBIEE_SERVER. I installed OBIEE on the OBIEE_SERVER and tested it using the out of the box OC4J container and that worked fine.
Then I installed WebLogic 11g on the WLS_SERVER machine and I ran the config.sh script. I used the configuration GUI to register the two physical machines and an additional server object called BIServer. Out of the box, web logic comes with AdminServer server object. I heard it's a bad practice to deploy applications to the AdminServer, hence why I created the BIServer object. I associated BIServer with the OBIEE_SERVER machine.
I went to start the BIServer and I got the following error:
"For server BIServer, the Node Manager associated with machine OBIEE_SERVER is not reachable."
How do I setup a Node Manager on the OBIEE_SERVER? Do I also need to physical put the WebLogic install file on the OBIEE_SERVER box and also run the installer there? Or there a copy paste thing I do? What am I missing here?
I appreciate the help!
-Joe

I'm trying to install WebLogic as server for OBIEEI have not heard about OBIEE, but if your aim is to use weblogic as a server for hosting this then you definitely need to install weblogic on the physical box where OBIEE will be hosted.
I associated BIServer with the OBIEE_SERVER machine.
I went to start the BIServer and I got the following error:
"For server BIServer, the Node Manager associated with machine OBIEE_SERVER is not reachable."Again not sure what is BIServer but I think you are missing a number of steps here. If you are trying to run BIServer
on weblogic you definitely need to install WLS on this physical machine [OBIEE_SERVER]. You will then need to configure a node manager on OBIEE_SERVER machine to enable it to start remotely from the admin machine.
Link for Node Manager. Since you are in Linux you can try setting up script based node manager.
http://download.oracle.com/docs/cd/E13222_01/wls/docs92/server_start/nodemgr.html#wp1099239

Juniper Java Secure Application Manager does not work with Snow Leopard

Anyone else having issues as well? I'm not using a client - its basically the Java based application manager for VPN connections to work (so I can remote desktop to my work PC).
Once logged in, it gives a "Restart your browser" error.
Thanks for your help

OK - so I got it to work. Here's what I did. Let me know if it works for you:
I wasn't able to follow the instructions exactly as noted in the original link I posted above.
The terminal command, specifically wget would not work - there is no wget.
I manually downloaded the Java 1.5 version, by following the link (just clicked on it). I 'unzipped' it and moved it into the library/frameworks/JavaVM.framework/versions folder.
So now the 1.5.0 is not an alias (as it is by default in SL), but the older version of Java.
I then followed the instruction related to changing the order in JAVA PREFERENCES.
The final stop - and I think this is key, is that I forced Safari to start in 32 bit mode. You can do this by going to Applications, highlighting Safari and hitting CMD-I. Then check the 32 bit option.
Start Safari, go to the appropriate URL and login. The Java Secure Application Manager should then start as it used to do in Leopard. You should be all set.
Hope this helps - let me know if someone has questions.

WL 7.0 Node Manager - auto restart after system boot fails

I have configured node manager to automatically restart managed servers on my Solaris
2.8 host. When I kill the managed server from the command line, node manager automatically
restarts the managed server just as I would expect. But when I reboot the system,
node manager does not restart the managed server. I started the managed server before
the reboot using node manager/admin console as the documentation states. I see nothing
in the logs that indicate any attempt by node manager to start the previously running
managed server, although node manager itself starts up OK after the reboot. Any
suggestions on how to get this working?
Here is my node manager config.xml contents:
#Saved configuration for webdevDomain_apps
#Sun Jul 14 23:12:08 EDT 2002
serverListenProtocol=http
serverListenHost=198.242.140.49
serverHealthCheckIntervalSeconds=180
TimeStamp=1026702630479
javaHome=/usr/jdk1.3
serverRestartDelaySeconds=60
command=online
ts2={3DES}QQj3hoYUACzB1csbrEth8Q\=\=
ts1=system
serverHealthCheckTimeoutSeconds=60
weblogic.Name=apps
java.security.policy=/home/weblogic/weblogic700/server/lib/weblogic.policy
RootDirectory=/home/webdev/weblogic700
serverStartArgs=-Xms64m -Xmx256m
- John

you are 100% right.
NM restarts MS's incase of
i) server crashes
ii) system reboots.
Kumar
John wrote:
Actually we were given a solution to this problem:
The node manager (NM) should restart managed servers (MS) upon reboot of the box.
There is one exception however - this can't happen if the MS is part of a cluster
and it hosts a migratable service. Currently there are two migratable services
- JMS and JTA. You need to have explicitly setup the migratable services for the
MS via the console.
Assuming you are not using these as migratable services you must explicitly set
a flag to indicate the MS is not hosting migratable services. This can be done
via the command line. It only needs to be done once and it will update the config.xml
file. The command line is:
java weblogic.Admin -url t3://adminhost:port -username <user> -password <password>
SET -mbean <domain>:Name=<MS name>,Type=Server -property HostsMigratableServices
false
You should see a simple reply of 'OK'.
Once this is done your should be able to reboot the box and after restart the
managed server should be running.
It worked!
Kumar Allamraju <[email protected]> wrote:
NM will only restart managed server's if they are abruptly killed.
We have no mechanism inplace to start managed server's upon system reboot.
May be you should write some startup scripts to start WLS upon system
start.
Kumar
John wrote:
I have configured node manager to automatically restart managed servers
on my Solaris
2.8 host. When I kill the managed server from the command line, node
manager automatically
restarts the managed server just as I would expect. But when I reboot
the system,
node manager does not restart the managed server. I started the managed
server before
the reboot using node manager/admin console as the documentation states.
I see nothing
in the logs that indicate any attempt by node manager to start the
previously running
managed server, although node manager itself starts up OK after the
reboot. Any
suggestions on how to get this working?
- John

NPE while starting Node Manager in SOA 11.1.1.5

I have installed SOA Suite 11g (11.1.1.5) as per Oracle Quick Start Guide for SOA Suite 11.1.1.5.
I start the database and Weblogic admin server. When I try to start the node manager, I am getting following error:
1 Nov, 2011 9:23:28 AM weblogic.nodemanager.server.NMServer <init>
WARNING: Node manager configuration properties file 'C:\Oracle\MIDDLE~3\WLSERV~1
.3\common\NODEMA~1\nodemanager.properties' not found. Using default settings.
<1 Nov, 2011 9:23:28 AM> <INFO> <Saving node manager configuration properties to
'C:\Oracle\MIDDLE~3\WLSERV~1.3\common\NODEMA~1\nodemanager.properties'>
1 Nov, 2011 9:23:28 AM weblogic.nodemanager.server.NMServer <init>
INFO: Saving node manager configuration properties to 'C:\Oracle\MIDDLE~3\WLSERV
~1.3\common\NODEMA~1\nodemanager.properties'
<1 Nov, 2011 9:23:28 AM> <SEVERE> <Fatal error in node manager server>
java.lang.NullPointerException
at java.util.Hashtable.containsKey(Hashtable.java:314)
at weblogic.nodemanager.server.NMServerConfig.initNetworkInfoList(NMServ
erConfig.java:491)
at weblogic.nodemanager.server.NMServerConfig.getNetworkInfoList(NMServe
rConfig.java:481)
at weblogic.nodemanager.server.NMServerConfig.getConfigProperties(NMServ
erConfig.java:545)
at weblogic.nodemanager.server.NMServer.<init>(NMServer.java:154)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:375)
at weblogic.NodeManager.main(NodeManager.java:31)
1 Nov, 2011 9:23:28 AM weblogic.nodemanager.server.NMServer main
SEVERE: Fatal error in node manager server
java.lang.NullPointerException
at java.util.Hashtable.containsKey(Hashtable.java:314)
at weblogic.nodemanager.server.NMServerConfig.initNetworkInfoList(NMServ
erConfig.java:491)
at weblogic.nodemanager.server.NMServerConfig.getNetworkInfoList(NMServe
rConfig.java:481)
at weblogic.nodemanager.server.NMServerConfig.getConfigProperties(NMServ
erConfig.java:545)
at weblogic.nodemanager.server.NMServer.<init>(NMServer.java:154)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:375)
at weblogic.NodeManager.main(NodeManager.java:31)
C:\Oracle\MIDDLE~3\WLSERV~1.3\common\NODEMA~1>goto finish
C:\Oracle\MIDDLE~3\WLSERV~1.3\common\NODEMA~1>ENDLOCAL
C:\Oracle\Middleware\wlserver_10.3\server\bin>
I checked "C:\Oracle\Middleware\wlserver_10.3\common\nodemanager" directory. There is no nodemanager.properties file there. Do I need to create it manually?
Please advise.
Thanks,
Vivek

I cut and paste the description of the note. There is a statement with the cause that states
"This issue happens only when the display name of a NIC configured for migration in nodemanager is null"
and it is a little ambigious. It implies there is a workaround of setting the display name, but doesn't discuss how to apply this workaround; the display name it refers to generated by a code call to the NetworkInterface.getDisplayName() method from the JDK.
I assume that the display name here is the parameter called Interface within the nodemanger.properties, but there is nothing within the note that confirms this, nor if setting this to the NICE name will fix this issue. here is a full list of the nodemanger.propertes file -> http://download.oracle.com/docs/cd/E12840_01/wls/docs103/nodemgr/java_nodemgr.html#wp1068415
I'd download and try the patch in your place; it's a WLS patch (as nodemanager is part of WLS) so shouldn't affect SOA Suite. Failing that, open a SR.

Starting managed server using node manager

When i try to start the managed server using node manager i get the following error
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
Abort - core dumped
<Sep 21, 2010 3:58:07 PM> <FINEST> <NodeManager> <Waiting for the process to die: 22708>
<Sep 21, 2010 3:58:07 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<Sep 21, 2010 3:58:07 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
The managed server lok file is deleted, port is not in use. With similar node manager settings the managed server on the redundant server starts fine

Hi,
I am getting same issue. Not able to start the soa_server1. Can you pleae tell me the soulution if you able to reslove the issue.
starting weblogic with Java version:
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
[ERROR] aborted
JRockit aborted: Unknown error (50)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
Starting WLS with line:
D:\Oracle\MIDDLE~1\JROCKI~1.0-6\bin\java -jrockit -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms512m -Xmx512m -Dweblogic.Name=soa_server1 -Djava.security.policy=D:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=D:\Oracle\Middleware\user_projects\domains\domain2\servers\soa_server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xverify:none -da:org.apache.xmlbeans... -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=D:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=D:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=D:\Oracle\MIDDLE~1\WLSERV~1.3\server -Ddomain.home=D:\Oracle\MIDDLE~1\USER_P~1\domains\domain2 -Dcommon.components.home=D:\Oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Djrockit.optfile=D:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.domain.config.dir=D:\Oracle\MIDDLE~1\USER_P~1\domains\domain2\config\FMWCON~1 -Doracle.server.config.dir=D:\Oracle\MIDDLE~1\USER_P~1\domains\domain2\config\FMWCON~1\servers\soa_server1 -Doracle.security.jps.config=D:\Oracle\MIDDLE~1\USER_P~1\domains\domain2\config\fmwconfig\jps-config.xml -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Digf.arisidbeans.carmlloc=D:\Oracle\MIDDLE~1\USER_P~1\domains\domain2\config\FMWCON~1\carml -Digf.arisidstack.home=D:\Oracle\MIDDLE~1\USER_P~1\domains\domain2\config\FMWCON~1\arisidprovider -Dweblogic.alternateTypesDirectory=D:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,D:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Dweblogic.jdbc.remoteEnabled=false -Doracle.security.jps.policy.migration.validate.principal=false -da:org.apache.xmlbeans... -Dsoa.archives.dir=D:\Oracle\Middleware\Oracle_SOA1\soa -Dsoa.oracle.home=D:\Oracle\Middleware\Oracle_SOA1 -Dsoa.instance.home=D:\Oracle\MIDDLE~1\USER_P~1\domains\domain2 -Dtangosol.coherence.clusteraddress=227.7.7.9 -Dtangosol.coherence.clusterport=9778 -Dtangosol.coherence.log=jdk -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Djava.protocol.handler.pkgs="oracle.mds.net.protocol|oracle.fabric.common.classloaderurl.handler|oracle.fabric.common.uddiurl.handler|oracle.bpm.io.fs.protocol" -Dweblogic.transaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.net.ssl.trustStore=D:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoTrust.jks -Dem.oracle.home=D:\Oracle\Middleware\oracle_common -Djava.awt.headless=true -Dbam.oracle.home=D:\Oracle\Middleware\Oracle_SOA1 -Dums.oracle.home=D:\Oracle\Middleware\Oracle_SOA1 -Dweblogic.management.discover=false -Dweblogic.management.server=http://192.168.1.102:7001 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=D:\Oracle\MIDDLE~1\patch_wls1033\profiles\default\sysext_manifest_classpath;D:\Oracle\MIDDLE~1\patch_oepe1033\profiles\default\sysext_manifest_classpath;D:\Oracle\MIDDLE~1\patch_ocp353\profiles\default\sysext_manifest_classpath weblogic.Server
[WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
[ERROR] aborted
JRockit aborted: Unknown error (50)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
<Oct 4, 2010 6:25:39 AM> <FINEST> <NodeManager> <Waiting for the process to die: 700>
<Oct 4, 2010 6:25:39 AM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<Oct 4, 2010 6:25:39 AM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>

Unable to start SOA server through Node Manager

Hi All,
I am trying to install AIA 11.1.1.6.0 on the top of SOA Suite 11.1.1.6.0.
I was able to install successfully the weblogic server, rcu, soa and osb servers. Now, before installing the AIA, the document i am following it says, make sure to start the soa server through the node manager.
Now i start the admin server, then the node manager, to make sure i have checked that the node manager is up, i logged in to the weblogic console, went to Machines, and i can see that it is up and reachable.
Now using the WLST commands, first i connected to the node manager using command nmConnect(), then i am trying to start the soa server through node manager using the command start('soa_server1') command.
I am getting an error while trying to start soa server with nmStart() command, below is the error message...
"Error starting server soa_server1: weblogic.nodemanager.NMException: Exception while starting server 'soa_server1'"
I executed the dumpStack() command, and i am getting the output as "No stack trace available"
If i am able to start the soa server through the node manager, i can go ahead and install the AIA pack but this is not letting me go forward.
I also tried to start the soa server through the weblogic console., go to servers tab, select the soa_server1 and start, the soa server state is going to "FAILED_NOT_RESTARTABLE".
I followed some of the blogs like...
http://neeraj-soa-tips.blogspot.com/2010/06/starting-admin-and-managed-servers.html
http://www.javamonamour.org/2011/09/nmconnect-nmstart-nmkill.html
Experts, please give your advice.
Many Thanks,
N

Hi Narsing,
I'm assuming that you've followed the required Pre-config steps. If it is not working, I'd suggest to start the Admin and SOA server without node manager first. Then start your node manager and see if it is reachable from the WLS console. Then shut down your SOA server from command prompt and restart your SOA server from WLS console.
Verify the Listen Address of your Node Manager and start your node manager from command prompt by explicitly specifying the same address and port.
As WLS console internally uses node manager only to start your server, you would not need to use WLST scripts to do the same and only SOA server needs to be started using node manager.
Regards,
Neeraj Sehgal
Hi Neeraj,
I made sure that in the weblogic console, in the machines tab, local machine-->configuration--->Node Manager, I have given the correct Listen Address (Narsing-PC) and the listen port 5556.
I have made sure the property StartScriptEnabled= true.
I have started the admin server through startWebLogic.cmd command, now i start the node manager by going to the C:\Oracle\Middleware\wlserver_10.3\server\bin and running the command startNodeManager.cmd, then i go to the weblogic console--->servers--->control--->soa_server1--->start , it is going to FAILED_NOT_RESTARTABLE status.
If i see the log messages in the nodemanager.log, this is the below message...
<Jun 28, 2012 11:25:09 PM> <INFO> <soa_domain> <soa_server1> <Server output log file is 'C:\Oracle\Middleware\user_projects\domains\soa_domain\servers\soa_server1\logs\soa_server1.out'>
<Jun 28, 2012 11:25:11 PM> <INFO> <soa_domain> <soa_server1> <Server failed during startup so will not be restarted>
<Jun 28, 2012 11:25:11 PM> <WARNING> <Exception while starting server 'soa_server1'>
java.io.IOException: Server failed to start up. See server output log for more details.
 at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:196)
 at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
 at weblogic.nodemanager.server.Handler.handleStart(Handler.java:609)
 at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
 at weblogic.nodemanager.server.Handler.run(Handler.java:71)
 at java.lang.Thread.run(Thread.java:662)
The log message in the soa_server1.out file is as below...
Starting WLS with line:
C:\Oracle\MIDDLE~1\JDK160~1\bin\java -client -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms512m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=soa_server1 -Djava.security.policy=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=C:\Oracle\Middleware\user_projects\domains\soa_domain\servers\soa_server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xverify:none -da:org.apache.xmlbeans... -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dcommon.components.home=C:\Oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1 -Djrockit.optfile=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\servers\soa_server1 -Doracle.domain.config.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\carml -Digf.arisidstack.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\servers\soa_server1\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol"|"oracle.fabric.common.classloaderurl.handler"|"oracle.fabric.common.uddiurl.handler"|"oracle.bpm.io.fs.protocol -Dweblogic.jdbc.remoteEnabled=false -Doracle.security.jps.policy.migration.validate.principal=false -da:org.apache.xmlbeans... -Dbpm.enabled=true -Dsoa.archives.dir=C:\Oracle\Middleware\Oracle_SOA1\soa -Dsoa.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dsoa.instance.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1 -Dtangosol.coherence.clusteraddress=227.7.7.9 -Dtangosol.coherence.clusterport=9778 -Dtangosol.coherence.log=jdk -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Dweblogic.transaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.net.ssl.trustStore=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoTrust.jks -Dem.oracle.home=C:\Oracle\Middleware\oracle_common -Djava.awt.headless=true -Dbam.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dums.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dweblogic.management.discover=false -Dweblogic.management.server=http://localhost:7001 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1036\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_oepe180\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_ocp371\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_adfr1111\profiles\default\sysext_manifest_classpath weblogic.Server
FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
ERROR: transport error 202: bind failed: Address already in use
ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
<Jun 28, 2012 11:25:11 PM> <FINEST> <NodeManager> <Waiting for the process to die: 4808>
<Jun 28, 2012 11:25:11 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
<Jun 28, 2012 11:25:11 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
Someone please help, if i am able to start the soa manged server, i can go ahead and install the AIA Foundation pack...
Many Thanks.

Can I run more than one Node Manager per machine?

Hia,
We have a situation in our project where we need to run different domains on a Solaris machine in different java modes.
Say Domain1 should be running in 32bit version of java where as Domain2 should be running in 64bit mode due to the nature of testing currently going on in different domains.
We could successfully get the two domains running in different java modes in parallel by modifying the start scripts to decide which Sud data model to start the servers based on certain parms. However, the pain here is with the Node Manager.
My understanding is that there should be one Node Manager running per machine for all the domains running on that machine. So when ever I have to run a domain in a java mode different to that of what Node Manager is running on, I had to kill the node manager and start it in the same version that I want to start the other servers in since Node Manager uses its starting parms internally to start the Managed Servers (Note: there is no issue in running the Admin Server regardless of the node manager mode as expected).
Can somebody advise me if there is any way to get around this hassle?
I want to know if we can run more than one node manager per machine.
Below are the details of my env.
Weblogic Server 10.3
Solaris 10 SPARC 64 bit (SunOS 5.10 Generic_142900-14 sun4v sparc)
java version "1.6.0_20"
Hope all this makes sense...
Cheers,
Satish.
Edited by: apsnaidu on Mar 15, 2013 3:29 PM

You can run as many node manager as you want in a particular machine.
At the time of starting the node manager you need to pass hostname & Port.
This will start the nodemanager on different ports of a machine.
sh startNodeManager.sh <hostname> <port>
eg:- sh startNodeManager.sh dev_machine_01 5556
sh startNodeManager.sh dev_machine_01 5557
sh startNodeManager.sh dev_machine_01 5558
After starting your node manager in different ports you need to change machine details from admin console.

Accessing an EJB 3.0 Enterprise Bean and Node Manager

Hi to all
I have got a problem in using Local(Remote) EJB Interface in Weblogic. I use Node Manager.
I have two servers:
1. AdminServer (working on port 7001)
2. Server1 (working on port 7003 under node manager control)
I have one EAR application file. This file contains jars with ejb 3.0. One jar called jarnumber1.jar is deployed on AdminServer. Second jar called jarnumber2.jar id deployed on Server1.
jarnumber1.jar constains EJBBean1 class.
jarnumber2.jar constains EJBBean2 class.
I want call EJBBean2 from EJBBean1 but I can't. I got exception 'NamingException'.
Example source code:
@Stateless(mappedName = "EJBBean1")
public class EJBBean1implements EJBBean1Remote {
@EJB private EJBBean2Remote eJBBean2Remote ; //injection doesn't work
I also tried method described here: http://middlewaremagic.com/weblogic/?p=5665 but it doesn't work.
AminServer has own JNDI Tree and Server1 has own JNDI Tree. It's seems to be that EJBBean1 can't see EJBBean2 from second JDNI tree.
Pleas help me.
With Regards,
ZK

Please try the following code:
HelloEJBBean.java:
@Stateless(name="Hello")
@Remote(value={Hello.class})
public class HelloEJBBean implements Hello { ... }
hello.jsp:
Context ctx = new InitialContext();
Hello h = (Hello)ctx.lookup("ejb/Hello");
web.xml:
<ejb-ref>
<ejb-ref-name>ejb/Hello</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<remote>fi.kronodoc.test.model.Hello</remote>
</ejb-ref>
i think you should also define jndi mappings for the references in orion-ejb-jar.xml and orion-web.xml but for some reason it seems to be working also without these.

After I do Node Manager nmConnect(...) I can no longer start a managed svr

I am running 10.3.2 on both windown and redhat
I have a domain with AdminServer and one managed server.
I can start AdminServer from the shell with startWebLogic.cmd
I can log into the web based 'console'
I can go to Environment -> Servers and start/shutdown the managed server.
If I use WLST and...
connect('user', 'pass', 't3://localhost:7001')
nmEnroll('fullPathToDomainDir')
I am still OK, I can still use the console to start and stop the managed server and I can so WLST start('managedSever')
I stop running the AdminServer from the shell - it is no longer running.
Now, I want to start the AdminServer with Node Manager, so (with WLST)...
nmConnect('user','pass','localhost','5556','domainName)
I get the error...
'Cannot connect to Node Manager: Access to domain 'domainname' for user 'user' denied
As suggested elsewhere, I go and edit nm_password.properties and change the hashed user/pass to
username=user
password=pass
I go back to WLST, now nmConnect works!!!
I can then do..
nmStart('AdminServer')
The AdminServer start, I go to the web console, and I try to start the managed server, I get...
'For server managedServer, the Node Manager associated with machine machineName is not reachable'
So it looks like the re-hashed password from nmConnect(...), while it works for WLST, it no longer works for the console.
Bottom line, I can get either get the console to start the managed server (if I do WLST connect(...) + nmEnroll(...)) or I can get WLST to start the servers (if I reset nm_password.properties and do nmConnect), but I can not get WLST to start the AdminServer and have the AdminSever console start the managed server.
I know for a fact that others have run into this, but in the threads I found, the thread stops before a soluton is posted.
Anyone know about this issue?
Regards

There are a couple of things you need to keep in mind:
-- There is one and only one valid username / passwrod for connecting to the node manager.
-- When you use nmEnroll, the username / password placed in the nm_password.properties file is taken from the admin server, hashed an placed in the nm_password file.
-- When you edit the nm_password.properties, and place the line "enter in username=user / password='pass',", in clear text, you have over ridden the U/P \thje admin server knows.
That is why you have a situation, oen of the two works but never both at the same time.
What you need to do is:
-- Log in to the WL Console.
-- in the Domain Tree, click at teh root level, which is the domain name.
-- Under the security tab, under advanced there is a node manager username / password.
-- Click on "Lock and edit", and change those to match what you are using through WLST.
-- Activate changes.
-- Just to make sure all is well, use nmEnroll to re enroll the node manager again , this way the nm_password.properties file will be set up correctly.
Now, both the WL Console should be able to talk to the node manager as well as nmConnect('user','pass','localhost','5556','domainName) would succeed.
Also, if you want to use node manager to start /servers, make sure you edit the file ( $WL_HOME/common/nodemanager/nodemanager.properties) and change the line
StartScriptEnabled=false
to
StartScriptEnabled=true
This will ensure all the proper class paths and properties etc needed are set up when using the node manager.
You would need to bounce the node manager for this change t take effect
Hope this helps.

I can not start a remote server via Node Manager

There is a workaround to this problem. The issue seems to be
that when the node manager tries to start the managed server
it can not find java.exe in the system path. So please go to
Control Panel->System->...->Environment, and modify your PATH
system environment variable to include the java bin directory
in it.
Then try using the node manager again to start the managed
servers and you should have no problems.
We are aware of the issue and working on having a fix for it.
Savvas
"Rakesh Chauhan" <[email protected]> wrote:
>
Hey Guys!
I am using WLS6.1 on WIN2000 boxes. And I am getting the same error on
the Admin
console when I try to start any of the two
managed servers.
<Sep 25,2001 1:39:12 PM EDT> <Info> <[email protected]:7002><WindowsProcessControl:
online successfully invoked on server 'server90', pid: 0> The interesting thing is that when I start managed server of its own,
it is started
successfully and you can Stop the managed
server from the Admin Console.
Really frusted, I hope I have configured everything correctly. Can somebody
help
me out ?
Thanks Rakesh
"Martin Matthews" <[email protected]> wrote:
This message is simply a message from the Admin Server saying that it
has asked
NodeManager on the remote machine to start a certain server.
To see the logs for server startup then you can find these either on
the Admin
machine at WL_HOME/config/NodeManagerClientLogs/<ManagedServerName>/*.log
or on the remote machine at
WL_HOME/config/NodeManagerLogs/<ManagedServerName>/*.log
Cheers
Martin
"Paul Nixon" <[email protected]> wrote:
I also would like to know the answer to the question below from Vincent.
I am getting
this message in the Admin console from either of my two managed servers
whenever
the console has successfully contacted the Node Manager in managed
server
host.
The Node Manager logs themselves also report "online successful". What
doesn't
seem to happen is WebLogic startup and I haven't found any error log
that explains
why.
I have set the Remote Startup parameters correctly [I think] for both
managed
servers so cannot see what further is required.
Any input appreciated.
Paul.
"Vincent Ducret" <[email protected]> wrote:
Hi everybody,
When I try to start a remote WLS 6.1 server from my computer, I receive
the message
below in my WLS administration console. The Node manager is runningon
the remote
machine and correctly configured, I hope!
What does this message mean ???
Thanks for your help
Vincent
<21 aoÃ»t 01 10:19:17 CEST> <Info> <[email protected]:5555>
<WindowsProcessControl:
online successfully invoked on server 'testserver', pid: 0>

Migrate to Java Based Node Manager

Similar Messages

Maybe you are looking for