Starting managed servers using Nodemanager

When I try to start a manage server using the nodemanager sitting on the same machine
as the Admin Server and the nodemanager itself, I get the following message:
<Error> <NodeManager> <Could not start server 'serverA' via Node Manager - reason:
'[SecureSocketListener: Could not load certificate '.\\c:\weblogic6.1\wlserver6.1/config/mydomain/demo.crt'
of type 'RSA' - reason: '.\\c:\weblogic6.1\wlserver6.1/config/mydomain/demo.crt
(The filename, directory name, or volume label syntax is incorrect)']'>
What's causing this?

Hi,
Try deactivating Hostname Verification to None in the admin server throught the WLS console. If you have configured the nodemanager.hosts with the ip of the admin server with this step should work. I fthe admin server is with dns name then you need to enable reverse DNS lookup in the nodemanager.properties file, or with the command-line argument:
ReverseDnsEnabled=true

Similar Messages

  • Problem while starting managed server using nodemanager

    Hi everyone,
    I am using WLST of Weblogic server 10.3, to automate the creation of domain, managed servers,JDBC,JMS resources etc.. and trying to start the managed servers using node manager. I have an environment which contains few domains. All the domains are using machine named "X".
    Now, i am creating the same machine in my domain WLSTDomain. I have the following doubts.
    Is there a way to check whether the nodemanager(of X) is already running.
    If there is a way to check that, how can we start the managed servers in WLSTDomain using that existing nodemanager.

    1. yes you can check if the nodemanage is running using the following ways.
    For linux env:-
    a. Check if the JAVA process for nodemanager is running ps -ef | grep java and see the nodemanager process else /usr/sbin/lsof -i:$port (port of nodemanager).
    b. Login to Admin Console --> Environment --> Machines --> Click on Machines --> Nodemanager --> Monitoring will give you nodemanager status from Admin console.
    c. use nm() command with WLST
    Example:
    wls:/mydomain/serverConfig> nm()
    Currently connected to Node Manager that is monitoring the domain "mydomain"
    wls:/mydomain/serverConfig> nm()
    Not connected to any Node Manager
    wls:/mydomain/serverConfig>
    To see if WLST connects to nodemanager or not?
    help('nmLog') --> to check the nm logs
    2. To start the nodemanager using WLST here are the commands
    Example:
    For single managed Server
    wls:/mydomain/serverConfig> start('myserver', 'Server', block='false')
    Starting server 'myserver' ...
    The server 'myserver' started successfully.
    wls:/mydomain/serverConfig>
    For Cluster
    wls:/mydomain/serverConfig> start('mycluster', 'Cluster')
    Starting the following servers in Cluster, mycluster: MS1, MS2, MS3...
    All servers in the cluster mycluster are started successfully.
    wls:/mydomain/serverConfig>

  • Failes to start Managed server using Nodemanager from admin console

    Hi
    I have created the cluster using Weblogic version 9.2 MP3 with
    Machine 1 --> Admin (AS) + Managed server (MS1)
    Machine 2 --> Managed server(MS2)
    All the servers(AS,MS1,MS2) are SSL configured to run in production mode.
    Machine is associated with each managed server and node manager is up and running.
    I have made Host name verification as "None"
    When i start the MS 1 from admin console it comes up in running.However MS2 is not coming in running mode.
    The server logs states that "Could not connect to admin server"
    Cannot decrypt the password ,username and TrustKeyStorePrivatepassphrase.
    Even when i write the clear text password and username in Server_Name/data/nodemanager/boot.properties,then also it throws the same error.
    Node manager is not configured to SSL.
    Any Clue what i am missing????

    Is your Machine #2 shown as "Reachable" in the admin console ( Machines -> Machine2 -> Monitoring )?
    Does your managed server #2 have the same userid and password on its Server -> Configuration -> Server Start page ( UserName & Password fields ) as managed server #1?
    Your boot.properties only needs 2 lines, like:
    password=your plain text password
    username=your plain text username

  • Starting managed servers

    Hi,
    Environment: WebLogic 6.1 SP2, JDK1.3.1, Solaris 8
    1. How to start the managed servers using NodeManager from the command line? Already
    NodeManager configured and able to start managed servers from the Admin Console.
    So from the console start/stop/kill managed servers is fine. From the command
    line, if I use `weblogic.Server` to start managed server it's not using the node
    manager.
    2. In the `java weblogic.nodemanager.NodeManager help`, option `starttemplate`
    defaults to `nodemanager.sh`. Any details on this please ?
    3. Each time we start managed server with Node Manager, it writes the output to
    the new file `OutputFile=./config/NodeManagerlogs/<server>/startserver-<XXXX.log`.
    From the documentation it looks like we can set logs directory
    `-Dweblogic.nodemanager.savedLogsDirectory=path`, however is it possible to specify
    the log file name also?
    4. Where is the location of the java applications `System.out`, if the managed
    server is started with NodeManager. If the managed server is started with `weblogic.Server`
    the `System.out` are printed to the console. So this enables us to redirect to
    a file.
    thanks
    Sarva Meduri

    I think you can configure the NodeMgr to start ManagedServers instead of having the
    Windows Service start the servers. Basically you configure NodeMgr as a Windows Service
    and then let NM take care of starting other servers. I believe you have to set
    ManagedServer's HostsMigratableServices attribute to false to enable NM start the server.
    By default it is true.
    prasen
    Gerardo Rojas wrote:
    Hi:
    I have been trying to configure my WebLogic environment to start the managed servers
    in a domain automatically when the machine is rebooted. I have done some testing
    with Node Manager but, as I understood, Node Manager only restarts a server if
    it was started using Node Manager and the server crashes or fails. On the other
    hand, if the server is installed as a Windows service, it will be started at reboot
    time, but not when the server (not the machine) crashes or fails. So, both solutions
    seems to be uncompatible. Is it right?? Is it possible to have both benefits,
    that is, to get the managed servers started at boot time (as done by Windows services)
    and restarted each time they fail (as done by Node Manager)?
    Thanks,
    Gerardo

  • Starting managed Servers under WLS 8.1 using Operator Role

    Hi,
    we've configured a user who is acting in the default 'Operator' role.
    He can shutdown a managed server using the admin console, but when
    trying to restart that managed server via node manager he fails with an exception.
    weblogic.management.NoAccessRuntimeException: Access not allowed for subject:
    principals=[oper, Operators], on ResourceType: Server Action: write, Target: ExpectedToRun
    According to the documentation http://edocs.bea.com/wls/docs81/secwlres/secroles.html
    this role should be allowed to start managed servers.
    -- What are we doing wrong ? --
    Cheers,
    Robert

    I believe this is a known problem, please contact BEA support for a patch.
    Thanks,
    -satya
    Robert Akolk wrote:
    Hi,
    we've configured a user who is acting in the default 'Operator' role.
    He can shutdown a managed server using the admin console, but when
    trying to restart that managed server via node manager he fails with an exception.
    weblogic.management.NoAccessRuntimeException: Access not allowed for subject:
    principals=[oper, Operators], on ResourceType: Server Action: write, Target: ExpectedToRun
    According to the documentation http://edocs.bea.com/wls/docs81/secwlres/secroles.html
    this role should be allowed to start managed servers.
    -- What are we doing wrong ? --
    Cheers,
    Robert

  • Unable to start Manager server using Node Manager

    Hi,
    I have deployed Admin server in one of my unix machine(machine1) and i able to start my Admin server using node manager, and when i try to start my Managed server in another machine(machine2) using the node manager(that machine node manager) its throwing error;
    Note: am able to start Managed server using Adminurl and able to connect to Managed server node manager successfully,
    but not able to start Managed server using node manager
    its giving exception as below;
    error:- wls:/nm/webdomain> nmStart('ms1')
    Starting server ms1 ...
    Error Starting server ms1: weblogic.nodemanager.NMException: Exception while starting server 'ms1'
    Managed server log: -
    <Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
    [root@LinuxVM ~]# cat /root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00071
    <Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Starting WebLogic server with command line: /root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/bin/java -Dweblogic.Name=ms1 -Dbea.home=/root/Oracle/Middleware -Djava.security.policy=/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Djava.library.path="/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386/jrockit:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/../lib/i386:/root/Oracle/Middleware/patch_wls1035/profiles/default/native:/root/Oracle/Middleware/patch_ocp360/profiles/default/native:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686/oci920_8" -Djava.class.path=/root/Oracle/Middleware/patch_wls1035/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/patch_ocp360/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/lib/tools.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/root/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.5.0.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/root/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/root/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/root/Oracle/Middleware -Dweblogic.system.BootIdentityFile=/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true weblogic.Server >
    <Dec 13, 2011 3:40:17 PM> <INFO> <NodeManager> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
    Nodemanager log:
    <Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Rotated server output log to "/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00070">
    <Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server error log also redirected to server log>
    <Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Starting WebLogic server with command line: /root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/bin/java -Dweblogic.Name=ms1 -Dbea.home=/root/Oracle/Middleware -Djava.security.policy=/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Djava.library.path="/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386/jrockit:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/lib/i386:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/jre/../lib/i386:/root/Oracle/Middleware/patch_wls1035/profiles/default/native:/root/Oracle/Middleware/patch_ocp360/profiles/default/native:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686:/root/Oracle/Middleware/wlserver_10.3/server/native/linux/i686/oci920_8" -Djava.class.path=/root/Oracle/Middleware/patch_wls1035/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/patch_ocp360/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/root/Oracle/Middleware/jrockit_160_24_D1.1.2-4/lib/tools.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/root/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.5.0.jar:/root/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/root/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/root/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/root/Oracle/Middleware -Dweblogic.system.BootIdentityFile=/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true weblogic.Server >
    <Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Working directory is '/root/Oracle/Middleware/user_projects/domains/webdomain'>
    <Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Rotated server output log to "/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out00071">
    <Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server error log also redirected to server log>
    <Dec 13, 2011 3:40:17 PM> <INFO> <webdomain> <ms1> <Server output log file is '/root/Oracle/Middleware/user_projects/domains/webdomain/servers/ms1/logs/ms1.out'>
    <Dec 13, 2011 3:40:26 PM> <INFO> <webdomain> <ms1> <Server failed during startup so will not be restarted>
    <Dec 13, 2011 3:40:26 PM> <WARNING> <Exception while starting server 'ms1'>
    java.io.IOException: Server failed to start up. See server output log for more details.
    at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:200)
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:119)
    at weblogic.nodemanager.server.Handler.run(Handler.java:71)
    at java.lang.Thread.run(Thread.java:662)

    You can start a managed server as follows:
    print 'START NODE MANAGER';
    startNodeManager(verbose='true', NodeManagerHome=nodemanagerhomelocation, ListenPort='5556', ListenAddress='localhost');
    print 'CONNECT TO NODE MANAGER';
    nmConnect(adminusername, adminpassword, 'localhost', '5556', domainname, domainlocation, 'ssl');
    print 'START ADMIN SERVER';
    nmStart('AdminServer');
    nmServerStatus('AdminServer');
    print 'CONNECT TO ADMIN SERVER';
    connect(adminusername, adminpassword);
    print 'START MANAGED SERVER';
    start('VideotheekWebServer','Server');
    nmServerStatus('VideotheekWebServer');
    print 'START CLUSTER';
    start('VideotheekCluster','Cluster');
    nmServerStatus('VideotheekServer1');
    nmServerStatus('VideotheekServer2');JVM properties are set using the admin console and edit the startup properties of your managed server (configuration, server start).
    The properties file (startup.properties) is saved in the directory <domain-home>/servers/<server-name>/data/nodemanager.

  • Unable to start managed servers from Admin Console "FAILED_NOT_RESTARTABLE"

    I recently installed WebLogic 10.3.5, JRockit, and ECM 11.1.1.5. I'm to the point where I am trying to get Nodemanager configured so I can stop/start managed servers through the admin console. I have the following listed in Environment > Servers:
    AdminConsole - running
    IBR_server1 - FAILED_NOT_RESTARTABLE
    managedServer1 - FAILED_NOT_RESTARTABLE
    UCM_server1 - FAILED_NOT_RESTARTABLE
    I followed the tutorial at http://blogs.oracle.com/jamesbayer/entry/weblogic_nodemanager_quick_sta to get to the point where the AdminServer starts when the server reboots, so I think Nodemanager is working there. If I view Machines > Monitoring, it says Nodemanager "Reachable." However, when I go to restart IBR_server1, managedServer1, or UCM_server1, I get the FAILED_NOT_RESTARTABLE status. I am using the weblogic server's IP for the machine name/host because our DNS is still screwed up. Would that have any affect on this?
    I'm completely unsure what to do now. The Nodemanager log shows:
    INFO - <Loading domains file: E:\oracle\MIDDLE~1\WLSERV~1.3\common\nodemanager\nodemanager.domains>
    WARNING - <Domains file not found: E:\oracle\MIDDLE~1\WLSERV~1.3\common\nodemanager\nodemanager.domains>
    INFO - <Loading identity key store: FileName=E:/oracle/MIDDLE~1/WLSERV~1.3/server\lib\DemoIdentity.jks, Type=jks, PassPhraseUsed=true>
    WARNING - <Node manager configuration properties file 'E:\oracle\MIDDLE~1\WLSERV~1.3\common\nodemanager\nodemanager.properties' not found. Using default settings.>
    So I'm confused why it's saying the properties file and domains file are not found... I've checked and they exist at
    E:\oracle\middleware\wlserver_10.3\common\nodemanager\nodemanager.properties
    and
    E:\oracle\middleware\wlserver_10.3\common\nodemanager\nodemanager.domains
    The domains file contains
    base_domain=e\:\\oracle\\middleware\\user_projects\\domains\\base_domain
    Which is correct.
    Any idea what I'm missing here? I can provide more detail if needed. Thank you.
    EDIT: I should add that I can start the UCM and IBR managed servers using the start up scripts on the server, but that's not what I'm after. I want everything controlled through the AdminConsole and want to be sure that when the server reboots, all the managed servers come back up correctly.
    Edited by: user5824683 on Oct 5, 2011 5:04 PM
    Edited by: user5824683 on Oct 5, 2011 5:09 PM

    I did a bit of digging, and it seems I have an issue with -Xnohup... I've verified this arugment exists in all of my managed servers properties files, yet it still bombs when I try to restart from the webLogic console. I should note that if I start fresh from the server, I can start all my manager servers using WLST nmStart().
    starting weblogic with Java version:
    java version "1.6.0_24"
    Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
    Oracle JRockit(R) (build R28.1.3-11-141760-1.6.0_24-20110301-1430-windows-x86_64, compiled mode)
    Starting WLS with line:
    E:\java\JROCKI~1.1\bin\java -jrockit -Xms256m -Xmx512m -Dweblogic.Name=IBR_server1 -Djava.security.policy=E:\oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=E:\oracle\middleware\user_projects\domains\base_domain\servers\IBR_server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xnohup -Xverify:none -da -Dplatform.home=E:\oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=E:\oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=E:\oracle\MIDDLE~1\WLSERV~1.3\server -Dcommon.components.home=E:\oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1 -Djrockit.optfile=E:\oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\FMWCON~1\servers\IBR_server1 -Doracle.domain.config.dir=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\FMWCON~1\carml -Digf.arisidstack.home=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\servers\IBR_server1\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=E:\oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,E:\oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Ducm.oracle.home=E:\oracle\MIDDLE~1\ORACLE~2 -Dem.oracle.home=E:\oracle\middleware\oracle_common -Djava.awt.headless=true -Dweblogic.management.discover=false -Dweblogic.management.server=http://138.126.180.177:7001 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=e:\oracle\MIDDLE~1\patch_wls1035\profiles\default\sysext_manifest_classpath weblogic.Server
    Exception in thread "Main Thread" java.lang.NoClassDefFoundError: –Xnohup
    Caused by: java.lang.ClassNotFoundException: –Xnohup
         at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
         at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
         at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
    Could not find the main class: –Xnohup. Program will exit.
    <Oct 6, 2011 12:38:13 PM> <FINEST> <NodeManager> <Waiting for the process to die: 4252>
    <Oct 6, 2011 12:38:13 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
    <Oct 6, 2011 12:38:13 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>

  • HANDSHAKE_FAILURE problem when starting managed server via NOdeManager

    hi all, i am trying to start a managed server using nodeManager, but i keep on
    getting following exception:
    weblogic.nodemanager.NodeManagerException: [Could not execute command start for
    server managedServer via the Node Manager - reason: [CommandInvoker: Failed to
    send command: 'online to server 'managedServer' to NodeManager at host: 'localhost:5555'
    with exception FATAL Alert:HANDSHAKE_FAILURE - The handshake handler was unable
    to negotiate an acceptable set of security parameters.. Please ensure that the
    NodeManager is active on the target machine].] at weblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeManagerRuntime.java:472)
    at weblogic.nodemanager.NodeManagerRuntime.start(NodeManagerRuntime.java:76) at
    java.lang.reflect.Method.invoke(Native Method) at
    here is my script for starting nodemanager
    set JAVA_HOME=c:\bea\jdk131
    set WL_HOME=c:\bea\weblogic700
    set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
    set CLASSPATH=.;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar
    java -hotspot -ms16m -mx16m -classpath %CLASSPATH% -Dbea.home=C:\bea\weblogic700
    -Djava.security.policy=C:\bea\weblogic700\server\lib\weblogic.policy -Dweblogic.nodemanager.weblogicHome=C:\bea\weblogic700
    -Dweblogic.nodemanager.listenAddress=172.21.73.94 -Dweblogic.nodemanager.listenPort=5555
    -Dweblogic.nodemanager.trustedHosts=C:\bea\weblogic700\common\nodemanager\config\nodemanager.hosts
    -Dweblogic.nodemanager.certificateFile=C:\bea\weblogic700\common\nodemanager\config\demo.crt
    weblogic.nodemanager.NodeManager
    i have created an admin server, called adminserver
    then i have created in the same domain a server called managedserver
    both servers run on the same machine,at different port number.
    i have created a machine, and associated managedserver to it.
    in the machine/configuration/nodemanager i have set listenaddress localhost and
    listenport 5555.
    my nodemanager starts automatically at htat port. however, when i try to start
    the managed server via adminserver console, i got the exception mentioned in
    the subject.
    can anyone help?
    regards
    marco
    can anyone point me to the right direction for solving this problem?
    in the adminserver console i have defined a machine for teh managedserver, and
    nodemanager is supposed to run at localhost:5555 (and indeed it does, because
    ihave started it successfully).
    thanx in advance and regards marco

    Marco.
    Sorry, this is not a solution to your problem but i am trying to solve the same
    problem for a week now.
    I have wl7.0 sp2, 1 admin server, 2 managed servers on the same box. I get the
    same error. I know that the default certificate installed provides a hostname
    verification of weblogic.com. I turned the hostname verification off, i put in
    the Dweblogic.nodemanager.sslHostNameVerificationEnabled=false, i get the same
    error when starting the managed server. I went ahead and created my own certificate
    for machine called mallik, created my own passphrase, created a new keystore,
    made the admin server view the keystore, used the same certificate for both the
    admin server and the node manager. It still fails with the same error. I went
    ahead and added the machine 'mallik' to nodeManager.hosts file. It fails. I am
    totally confused now what needs to be done.
    My nodeManger.hosts looks like this:
    mallik 10.100.10.130
    managedServer1 10.100.10.130
    managedServer2 10.100.10.13
    Below is the startNodeManager.cmd.
    @echo off
    @rem *************************************************************************
    @rem This script can be used to start the WebLogic NodeManager
    @rem
    @rem This script sets the following variables before starting the NodeManager:
    @rem
    @rem WL_HOME - The root directory of your WebLogic installation.
    @rem NODEMGR_HOME - The home directory for this NodeManager instance.
    @rem JAVA_HOME - Location of the version of Java used to start WebLogic
    @rem Server. This variable must point to the root directory of
    @rem a JDK installation and will be set for you by the
    @rem          installer. See the WebLogic platform support page
    @rem (http://e-docs.bea.com/wls/platforms/index.html) for an up-to-date
    list of
    @rem supported JVMs on Windows NT.
    @rem PATH - Adds the JDK and WebLogic directories to the system path.
    @rem CLASSPATH - Adds the JDK and WebLogic jars to the classpath.
    @rem JAVA_OPTIONS - Java command-line options for running the server. (These
    @rem will be tagged on to the end of the JAVA_VM and MEM_ARGS)
    @rem JAVA_VM - The java arg specifying the VM to run. (i.e. -server,
    @rem -client, etc.)
    @rem MEM_ARGS - The variable to override the standard memory arguments
    @rem passed to java
    @rem
    @rem *************************************************************************
    SETLOCAL
    set WL_HOME=C:\bea7.0\weblogic700
    set NODEMGR_HOME=%WL_HOME%\common\nodemanager
    set JAVA_HOME=C:\bea7.0\jdk131_06
    Call %WL_HOME%\common\bin\commEnv.cmd
    @rem If NODEMGR_HOME does not exist, create it
    :checkNodeManagerHome
    if exist %NODEMGR_HOME% goto checkJava
    echo.
    echo NODEMGR_HOME %NODEMGR_HOME% does not exist, creating it..
    mkdir %NODEMGR_HOME%
    @rem Check that java is where we expect it to be
    :checkJava
    if exist %JAVA_HOME%\bin\java.exe goto runNodeManager
    echo The JDK wasn't found in directory %JAVA_HOME%.
    echo Please edit this script so that the JAVA_HOME
    echo variable points to the location of your JDK.
    goto finish
    :runNodeManager
    if not "%JAVA_VM%" == "" goto noResetJavaVM
    rem set JAVA_VM=-hotspot
    set JAVA_VM=%COMM_VM%
    :noResetJavaVM
    if not "%MEM_ARGS%" == "" goto noResetMemArgs
    set MEM_ARGS=-Xms32m -Xmx200m
    :noResetMemArgs
    @echo on
    set CLASSPATH=.;%JAVA_HOME%\lib\tools.jar;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar;%CLASSPATH%
    set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
    cd %NODEMGR_HOME%
    #"%JAVA_HOME%\bin\java.exe" %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% -classpath "%CLASSPATH%"
    "-Dbea.home=C:\bea7.0" "-Dweblogic.security.SSL.trustedCAKeyStore=%WL_HOME%\server\lib\cacerts"
    "-Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy" "-Dweblogic.nodemanager.reverseDnsEnabled=true"
    "-Dweblogic.nodemanager.javaHome=%JAVA_HOME%" weblogic.nodemanager.NodeManager
    "%JAVA_HOME%\bin\java.exe" %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% -classpath "%CLASSPATH%"
    "-Dbea.home=C:\bea7.0" "-Dweblogic.security.SSL.trustedCAKeyStore=%WL_HOME%\server\lib\cacerts"
    "-Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy" "-Dweblogic.nodemanager.certificateFile=C:\bea7.0\user_projects\myDomain\mallikcert.pem"
    "-Dweblogic.nodemanager.sslHostNameVerificationEnabled=false" "-Dweblogic.nodemanager.javaHome=%JAVA_HOME%"
    "-Dweblogic.ListenAddress=mallik" "-Dweblogic.nodemanager.nativeVersionEnabled=true"
    "-Dweblogic.nodemanager.reverseDnsEnabled=true" "-Dweblogic.nodemanager.javaHome=%JAVA_HOME%"
    "-Dweblogic.nodemanager.trustedHosts=%WL_HOME%\common\nodemanager\config\nodemanager.hosts"
    "-Dweblogic.management.pkpassword=weblogic" weblogic.nodemanager.NodeManager
    goto finish
    :finish
    ENDLOCAL
    I would appreciate if anybody can help me.
    Mallik.
    "Marco" <[email protected]> wrote:
    >
    hi all, i am trying to start a managed server using nodeManager, but
    i keep on
    getting following exception:
    weblogic.nodemanager.NodeManagerException: [Could not execute command
    start for
    server managedServer via the Node Manager - reason: [CommandInvoker:
    Failed to
    send command: 'online to server 'managedServer' to NodeManager at host:
    'localhost:5555'
    with exception FATAL Alert:HANDSHAKE_FAILURE - The handshake handler
    was unable
    to negotiate an acceptable set of security parameters.. Please ensure
    that the
    NodeManager is active on the target machine].] at weblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeManagerRuntime.java:472)
    at weblogic.nodemanager.NodeManagerRuntime.start(NodeManagerRuntime.java:76)
    at
    java.lang.reflect.Method.invoke(Native Method) at
    here is my script for starting nodemanager
    set JAVA_HOME=c:\bea\jdk131
    set WL_HOME=c:\bea\weblogic700
    set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
    set CLASSPATH=.;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar
    java -hotspot -ms16m -mx16m -classpath %CLASSPATH% -Dbea.home=C:\bea\weblogic700
    -Djava.security.policy=C:\bea\weblogic700\server\lib\weblogic.policy
    -Dweblogic.nodemanager.weblogicHome=C:\bea\weblogic700
    -Dweblogic.nodemanager.listenAddress=172.21.73.94 -Dweblogic.nodemanager.listenPort=5555
    -Dweblogic.nodemanager.trustedHosts=C:\bea\weblogic700\common\nodemanager\config\nodemanager.hosts
    -Dweblogic.nodemanager.certificateFile=C:\bea\weblogic700\common\nodemanager\config\demo.crt
    weblogic.nodemanager.NodeManager
    i have created an admin server, called adminserver
    then i have created in the same domain a server called managedserver
    both servers run on the same machine,at different port number.
    i have created a machine, and associated managedserver to it.
    in the machine/configuration/nodemanager i have set listenaddress localhost
    and
    listenport 5555.
    my nodemanager starts automatically at htat port. however, when i try
    to start
    the managed server via adminserver console, i got the exception mentioned
    in
    the subject.
    can anyone help?
    regards
    marco
    can anyone point me to the right direction for solving this problem?
    in the adminserver console i have defined a machine for teh managedserver,
    and
    nodemanager is supposed to run at localhost:5555 (and indeed it does,
    because
    ihave started it successfully).
    thanx in advance and regards marco

  • Starting Manage Server using node manager

    Hi,
    Hi,
    I am using Weblogic server 11g and I have deployed Admin server in one of my unix machine(machine1) and i able to start my Admin server using node manager, and when i try to start my Managed server in another machine(machine2) using the node manager(that machine node manager) its throwing error;
    Note: am able to start Managed server using Adminurl and able to connect to Managed server node manager successfully,
    but not able to start Managed server using node manager
    its giving exception as below;
    error:- wls:/nm/webdomain> nmStart('ms1')
    Starting server ms1 ...
    Error Starting server ms1: weblogic.nodemanager.NMException: Exception while starting server 'ms1'
    plz help me out in this
    Thanks in advance

    An example to start managed servers on different machine is provided here: http://middlewaremagic.com/weblogic/?p=6637
    "By default, WebLogic is installed and configured with the DemoIdentity.jks keystore. This certificate and key are created by utils.CertGen with the default options of containing only the host name in the common name field (cn), and not the fully-qualified DNS name. As a result, attempts to establish SSL connections may fail in some situations due to a host name verification exception. When using the demo certificates in a multi-server domain, managed server instances will fail to boot if they cannot establish an SSL connection with the Admin Server and the a BAD_CERTIFICATE error is generated. This error occurs because the host name verifier, which is enabled by default in all WebLogic domains and which is used during the SSL handshake, compares the value of the cn field in the certificate with the fully-qualified DNS name of the SSL server that accepts the SSL connection. If these names do not match, the SSL connection is dropped."

  • Unable to start Managed servers from admin console

    Hello!
    We have a problem to start Managed Servers throw Node manager.
    We get an error:
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Boot identity properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/boot.properties">
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
    INFO: Boot identity properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/boot.properties"
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Startup configuration properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/startup.properties">
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
    INFO: Startup configuration properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/startup.properties"
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server error log also redirected to server log>
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.LogFileRotationUtil log
    INFO: Server error log also redirected to server log
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Starting WebLogic server with command line: /software/psoft/pt851/webserv/peoplesoft/bin/startManagedWebLogic.sh >
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
    INFO: Starting WebLogic server with command line: /software/psoft/pt851/webserv/peoplesoft/bin/startManagedWebLogic.sh
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Working directory is '/software/psoft/pt851/webserv/peoplesoft'>
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
    INFO: Working directory is '/software/psoft/pt851/webserv/peoplesoft'
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Rotated server output log to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out00001">
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.LogFileRotationUtil log
    INFO: Rotated server output log to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out00001"
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server error log also redirected to server log>
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.LogFileRotationUtil log
    INFO: Server error log also redirected to server log
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server output log file is '/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out'>
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
    INFO: Server output log file is '/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out'
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server failed during startup so will not be restarted>
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
    INFO: Server failed during startup so will not be restarted
    <Jan 26, 2012 2:17:54 PM> <WARNING> <Exception while starting server 'PIA1'>
    java.io.IOException: Server failed to start up. See server output log for more details.
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
    at weblogic.nodemanager.server.Handler.run(Handler.java:70)
    at java.lang.Thread.run(Thread.java:662)
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.Handler handleStart
    WARNING: Exception while starting server 'PIA1'
    java.io.IOException: Server failed to start up. See server output log for more details.
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
    at weblogic.nodemanager.server.Handler.run(Handler.java:70)
    at java.lang.Thread.run(Thread.java:662)
    Additional information:
    weblogic 10.3.3
    PT8.51.11
    Linux x86_64 RH5
    When we starting Manged servers manualy, it's works fine.
    Thank you.

    Hello!
    The problem is found.
    We tried to startup managed server by running startManagedServer.sh script, but this script expecting to get parameters.
    The NodeManager unable to send parameters to script that appears in nodemanager.properties file (StartScriptName).
    So, I created a new script startPIA.sh, that calls to startManagedServer.sh and sends it 2 parameters:
    ./startManagedWebLogic.sh $SERVER_NAME $ADMIN_URL
    Now, we can start and stop managed servers from admin console, BUT we still have an error in NodeManager:
    <Jan 29, 2012 11:15:39 AM> <INFO> <peoplesoft> <PIA1> <Server failed during startup so will not be restarted>
    Jan 29, 2012 11:15:39 AM weblogic.nodemanager.server.ServerManager log
    INFO: Server failed during startup so will not be restarted
    <Jan 29, 2012 11:15:39 AM> <WARNING> <Exception while starting server 'PIA1'>
    java.io.IOException: Server failed to start up. See server output log for more details.
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
    at weblogic.nodemanager.server.Handler.run(Handler.java:70)
    at java.lang.Thread.run(Thread.java:662)
    Jan 29, 2012 11:15:39 AM weblogic.nodemanager.server.Handler handleStart
    WARNING: Exception while starting server 'PIA1'
    java.io.IOException: Server failed to start up. See server output log for more details.
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
    at weblogic.nodemanager.server.Handler.run(Handler.java:70)
    at java.lang.Thread.run(Thread.java:662)
    There are no errors in managed servers logs.
    PIA1.out:
    <Jan 29, 2012 11:15:38 AM> <INFO> <NodeManager> <Server output log file is '/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out'>
    Attempting to start WebLogic Server PIA1
    No activity will be logged to this window.
    Server activity will be logged to /software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1_*
    PID for WebLogic Server PIA1 is: 27018
    <Jan 29, 2012 11:15:39 AM> <FINEST> <NodeManager> <Waiting for the process to die: 26847>
    <Jan 29, 2012 11:15:39 AM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
    <Jan 29, 2012 11:15:39 AM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
    The status of managed server in admin console is RUNNING, but "Status of Last Action" is FAILED.
    What can be the reason?
    Thank you.

  • Cannot start Managed server from NodeManager

    Hello All,
    Software version installed:-
    Oracle Jdeveloper 11.1.1.7
    Weblogic 10.3.6
    RCU:- 11.1.1.7
    SOA suite:-11.1.1.7
    OSB 11.1.1.7
    OS windows 7 ultimate 64 bit
    =====================
    Sucessfully installed all the above software. I planned to install AIA Foundation Pack and for this i need to configure node manager do start
    manage servers.
    Node manager configuration sucessfully done by following  @http://neeraj-soa-tips.blogspot.in/2010/06/part-1-how-to-configure-node-manager-to.html
    after this i am see node manger status as reachable in weblogic console.
    From admin console under servers control tab, i tried starting soa_server1 but i am getting below error in nodemanger window.
    java.io.IOException: Cannot run program "E:\Oracle\MiddleWare\wlserver_10.3\comm
    on\bin\bin\startWebLogic.cmd" (in directory "E:\Oracle\MiddleWare\wlserver_10.3\
    common\bin"): CreateProcess error=2, The system cannot find the file specified
            at java.lang.ProcessBuilder.start(ProcessBuilder.java:1041)
            at weblogic.nodemanager.server.WLSProcessImpl.start(WLSProcessImpl.java:
    44)
            at weblogic.nodemanager.server.WLSProcess.startProcess(WLSProcess.java:1
    94)
            at weblogic.nodemanager.server.AbstractServerMonitor.startWLSProcess_inn
    er(AbstractServerMonitor.java:419)
            at weblogic.nodemanager.server.AbstractServerMonitor.startWLSProcess(Abs
    tractServerMonitor.java:358)
            at weblogic.nodemanager.server.AbstractServerMonitor.start(AbstractServe
    rMonitor.java:103)
            at weblogic.nodemanager.server.ServerMonitor.start(ServerMonitor.java:25
            at weblogic.nodemanager.server.AbstractServerManager.startServer(Abstrac
    tServerManager.java:210)
            at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServe
    rManager.java:181)
            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:744)
    Caused by: java.io.IOException: CreateProcess error=2, The system cannot find th
    e file specified
            at java.lang.ProcessImpl.create(Native Method)
            at java.lang.ProcessImpl.<init>(ProcessImpl.java:385)
            at java.lang.ProcessImpl.start(ProcessImpl.java:136)
            at java.lang.ProcessBuilder.start(ProcessBuilder.java:1022)
            ... 13 more
    I request everyone that if any one has idea on the above error then please throw light on me , this issue is really annoying me.
    Also to make sure i tried starting startManagedWebLogic.cmd and sucessfull can see soa_server1 in running state.

    Note that it is saying that it cannot the file
    " Cannot run program "E:\Oracle\MiddleWare\wlserver_10.3\common\bin\bin\startWebLogic.cmd" (in directory "E:\Oracle\MiddleWare\wlserver_10.3\common\bin"): CreateProcess error=2, The system cannot find the file specified"
    What is somewhat strange is that it is expecting startWebLogic to be present in ${WL_HOME}/common/bin/bin. The second /bin/ does not exist (well not in normal installations). Also the location of startWebLogic is odd, usually this should be present, in the ${DOMAIN_HOME}/bin directory. Could be there are some paths incorrect in JDeveloper.

  • Starting UCM Servers from Nodemanager

    Hi,
    We wanted to start UCM servers from nodemanager. But, when I am starting AdminServer from nodemanager, EM and FMW Welcome Page Application (11.1.0.0.0) applications are failing to deloy. Admin logs are complaining for ClassNotFound like below:-
    <Feb 10, 2012 10:03:07 AM IST> <Critical> <WebLogicServer> <BEA-000286> <Failed to invoke startup class "JRF Startup Class", java.lang.ClassNotFoundException: oracle.jrf.wls.JRFStartup
    java.lang.ClassNotFoundException: oracle.jrf.wls.JRFStartup
         at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
         at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
         at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
         Truncated. see log file for complete stacktrace
    >
    <Feb 10, 2012 10:03:07 AM IST> <Critical> <WebLogicServer> <BEA-000286> <Failed to invoke startup class "JPS Startup Class", java.lang.ClassNotFoundException: oracle.security.jps.wls.JpsWlsStartupClass
    java.lang.ClassNotFoundException: oracle.security.jps.wls.JpsWlsStartupClass
         at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
         at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
         at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
         Truncated. see log file for complete stacktrace
    >
    <Feb 10, 2012 10:03:07 AM IST> <Critical> <WebLogicServer> <BEA-000286> <Failed to invoke startup class "ODL-Startup", java.lang.ClassNotFoundException: oracle.core.ojdl.weblogic.ODLConfiguration
    java.lang.ClassNotFoundException: oracle.core.ojdl.weblogic.ODLConfiguration
         at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
         at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
         at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
         Truncated. see log file for complete stacktrace
    >
    <Feb 10, 2012 10:03:07 AM IST> <Critical> <WebLogicServer> <BEA-000286> <Failed to invoke startup class "AWT Application Context Startup Class", java.lang.ClassNotFoundException: oracle.jrf.AppContextStartup
    java.lang.ClassNotFoundException: oracle.jrf.AppContextStartup
         at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
         at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
         at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
         Truncated. see log file for complete stacktrace
    >
    <Feb 10, 2012 10:03:07 AM IST> <Critical> <WebLogicServer> <BEA-000286> <Failed to invoke startup class "JMX Framework Startup Class", java.lang.ClassNotFoundException: oracle.as.jmx.framework.wls.spi.StartupListener
    java.lang.ClassNotFoundException: oracle.as.jmx.framework.wls.spi.StartupListener
         at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
         at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
         at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
         Truncated. see log file for complete stacktrace
    >
    <Feb 10, 2012 10:03:07 AM IST> <Critical> <WebLogicServer> <BEA-000286> <Failed to invoke startup class "JOC-Startup", java.lang.ClassNotFoundException: oracle.ias.cache.Startup
    java.lang.ClassNotFoundException: oracle.ias.cache.Startup
         at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
         at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
         at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
         Truncated. see log file for complete stacktrace
    >
    <Feb 10, 2012 10:03:07 AM IST> <Critical> <WebLogicServer> <BEA-000286> <Failed to invoke startup class "DMS-Startup", java.lang.ClassNotFoundException: oracle.dms.wls.DMSStartup
    java.lang.ClassNotFoundException: oracle.dms.wls.DMSStartup
         at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
         at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
         at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
         Truncated. see log file for complete stacktrace
    >
    <Feb 10, 2012 10:03:10 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STANDBY>
    <Feb 10, 2012 10:03:10 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <Feb 10, 2012 10:03:29 AM IST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'DMS Application [Version=11.1.1.1.0]' due to error java.lang.NoClassDefFoundError: oracle/dms/http/Request.
    java.lang.NoClassDefFoundError: oracle/dms/http/Request
         at java.lang.Class.getDeclaredFields0(Native Method)
         at java.lang.Class.privateGetDeclaredFields(Class.java:2291)
         at java.lang.Class.getDeclaredFields(Class.java:1743)
         at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.getFields(BaseJ2eeAnnotationProcessor.java:1024)
         at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.getFields(BaseJ2eeAnnotationProcessor.java:1017)
         Truncated. see log file for complete stacktrace
    Caused By: java.lang.NoClassDefFoundError: oracle/dms/http/Request
         at java.lang.Class.getDeclaredFields0(Native Method)
         at java.lang.Class.privateGetDeclaredFields(Class.java:2291)
         at java.lang.Class.getDeclaredFields(Class.java:1743)
         at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.getFields(BaseJ2eeAnnotationProcessor.java:1024)
         at weblogic.j2ee.dd.xml.BaseJ2eeAnnotationProcessor.getFields(BaseJ2eeAnnotationProcessor.java:1017)
         Truncated. see log file for complete stacktrace
    >
    <Feb 10, 2012 10:03:29 AM IST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'FMW Welcome Page Application [Version=11.1.0.0.0]' due to error weblogic.management.DeploymentException: .
    weblogic.management.DeploymentException:
         at weblogic.application.internal.flow.BaseLifecycleFlow$CreateMainClassAction.run(BaseLifecycleFlow.java:270)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:104)
         at weblogic.application.internal.flow.HeadLifecycleFlow.createMainClass(HeadLifecycleFlow.java:86)
         Truncated. see log file for complete stacktrace
    Caused By: java.lang.ClassNotFoundException: oracle.jrf.wls.StartupClassesAppExecutor
         at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:280)
         at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:253)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
         at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:177)
         Truncated. see log file for complete stacktrace
    >
    When processing WebService module 'wsil.war'. Failed to load servlet Class: oracle.j2ee.ws.server.wsil.WSILServlet
    Ignoring: unable to load class:java.lang.ClassNotFoundException: oracle.j2ee.ws.server.wsil.WSILServlet at: weblogic.xml.schema.binding.util.ClassUtil.loadClass(ClassUtil.java:76)
    When processing WebService module 'wsil.war'. Failed to load servlet Class: oracle.j2ee.ws.server.wsil.WSILServlet
    Ignoring: unable to load class:java.lang.ClassNotFoundException: oracle.j2ee.ws.server.wsil.WSILServlet at: weblogic.xml.schema.binding.util.ClassUtil.loadClass(ClassUtil.java:76)
    <Feb 10, 2012 10:03:29 AM IST> <Error> <Deployer> <BEA-149205> <Failed to initialize the application 'em' due to error weblogic.management.DeploymentException: .
    weblogic.management.DeploymentException:
         at weblogic.application.internal.flow.BaseLifecycleFlow$CreateListenerAction.run(BaseLifecycleFlow.java:176)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:104)
         at weblogic.application.internal.flow.HeadLifecycleFlow.createListener(HeadLifecycleFlow.java:117)
         Truncated. see log file for complete stacktrace
    Caused By: java.lang.ClassNotFoundException: oracle.security.jps.wls.listeners.JpsApplicationLifecycleListener
         at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:280)
         at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:253)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
         at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:177)
         Truncated. see log file for complete stacktrace
    >
    Feb 10, 2012 10:03:31 AM com.sun.faces.config.ConfigureListener contextInitialized
    INFO: Initializing Sun's JavaServer Faces implementation (1.2_03-b04-FCS) for context '/console'
    Feb 10, 2012 10:03:31 AM com.sun.faces.config.ConfigureListener contextInitialized
    INFO: Completed initializing Sun's JavaServer Faces implementation (1.2_03-b04-FCS) for context '/console'
    <Feb 10, 2012 10:03:33 AM IST> <Error> <HTTP> <BEA-101165> <Could not load user defined filter in web.xml: ServletContext@35590877[app:wsil-wls module:/inspection.wsil path:/inspection.wsil spec-version:2.5] oracle.dms.wls.DMSServletFilter.
    java.lang.ClassNotFoundException: oracle.dms.wls.DMSServletFilter
         at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:280)
         at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:253)
         at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:56)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
         Truncated. see log file for complete stacktrace
    >
    <Feb 10, 2012 10:03:33 AM IST> <Error> <Deployer> <BEA-149231> <Unable to set the activation state to true for the application 'wsil-wls'.
    weblogic.application.ModuleException:
         at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1514)
         at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:486)
         at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:425)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:119)
         Truncated. see log file for complete stacktrace
    Caused By: java.lang.ClassNotFoundException: oracle.dms.wls.DMSServletFilter
         at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:280)
         at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:253)
         at weblogic.utils.classloaders.ChangeAwareClassLoader.findClass(ChangeAwareClassLoader.java:56)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
         Truncated. see log file for complete stacktrace
    >
    <Feb 10, 2012 10:03:33 AM IST> <Notice> <Log Management> <BEA-170027> <The Server has established connection with the Domain level Diagnostic Service successfully.>
    <Feb 10, 2012 10:03:33 AM IST> <Critical> <WebLogicServer> <BEA-000286> <Failed to invoke startup class "Audit Loader Startup Class", java.lang.ClassNotFoundException: oracle.security.audit.ajl.loader.JEEAuditLoader
    java.lang.ClassNotFoundException: oracle.security.audit.ajl.loader.JEEAuditLoader
         at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
         at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
         at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
         Truncated. see log file for complete stacktrace
    <Feb 10, 2012 10:46:59 AM IST> <Warning> <netuix> <BEA-423420> <Redirect is executed in begin or refresh action. Redirect url is /console/console.portal?_nfpb=true&_pageLabel=AppApplicationOverviewPage&AppApplicationOverviewPortlethandle=com.bea.console.handles.AppDeploymentHandle%28%22com.bea%3AName%3DFMW+Welcome+Page+Application%2311.1.0.0.0%2CType%3DAppDeployment%22%29.>
    java.lang.ClassNotFoundException: oracle.as.jmx.framework.util.MBeansXmlServletContextListenerSupport
         at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:280)
         at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:253)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
         at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:177)
         at weblogic.servlet.internal.WebAnnotationProcessorImpl.processListeners(WebAnnotationProcessorImpl.java:249)
         at weblogic.servlet.internal.WebAnnotationProcessorImpl.processJ2eeAnnotations(WebAnnotationProcessorImpl.java:211)
         at weblogic.servlet.internal.WebAnnotationProcessorImpl.processAnnotations(WebAnnotationProcessorImpl.java:108)
         at weblogic.application.compiler.WARModule.processAnnotations(WARModule.java:433)
         at weblogic.application.compiler.EARModule.processAnnotations(EARModule.java:227)
         at weblogic.application.compiler.WARModule.merge(WARModule.java:483)
         at weblogic.application.compiler.flow.MergeModuleFlow.compile(MergeModuleFlow.java:23)
         at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:70)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
         at weblogic.application.compiler.FlowDriver$CompilerFlowDriver.compile(FlowDriver.java:97)
         at weblogic.application.compiler.ReadOnlyEarMerger.merge(ReadOnlyEarMerger.java:50)
         at weblogic.application.compiler.flow.AppMergerFlow.mergeInput(AppMergerFlow.java:88)
         at weblogic.application.compiler.flow.AppMergerFlow.compile(AppMergerFlow.java:42)
         at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDriver.java:70)
         at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:41)
         at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36)
         at weblogic.application.compiler.FlowDriver$CompilerFlowDriver.compile(FlowDriver.java:97)
         at weblogic.application.compiler.AppMerge.runBody(AppMerge.java:157)
         at weblogic.utils.compiler.Tool.run(Tool.java:158)
         at weblogic.utils.compiler.Tool.run(Tool.java:116)
         at weblogic.application.compiler.AppMerge.merge(AppMerge.java:170)
         at weblogic.deploy.api.internal.utils.AppMerger.merge(AppMerger.java:88)
         at weblogic.deploy.api.internal.utils.AppMerger.getMergedApp(AppMerger.java:63)
         at weblogic.deploy.api.model.internal.WebLogicDeployableObjectFactoryImpl.createDeployableObject(WebLogicDeployableObjectFactoryImpl.java:181)
         at weblogic.deploy.api.model.internal.WebLogicDeployableObjectFactoryImpl.createDeployableObject(WebLogicDeployableObjectFactoryImpl.java:163)
         at weblogic.deploy.api.tools.SessionHelper.initialize(SessionHelper.java:727)
         at weblogic.deploy.api.tools.SessionHelper.initializeConfiguration(SessionHelper.java:557)
         at weblogic.deploy.api.tools.SessionHelper.initializeConfiguration(SessionHelper.java:545)
         at weblogic.deploy.api.tools.SessionHelper.initializeConfiguration(SessionHelper.java:628)
         at com.bea.console.utils.DeploymentConfigurationHelper$1.execute(DeploymentConfigurationHelper.java:760)
         at com.bea.console.utils.DeploymentUtils.runDeploymentAction(DeploymentUtils.java:5000)
         at com.bea.console.utils.DeploymentConfigurationHelper.initDeploymentConfiguration(DeploymentConfigurationHelper.java:747)
         at com.bea.console.utils.DeploymentConfigurationHelper.<init>(DeploymentConfigurationHelper.java:352)
         at com.bea.console.utils.DeploymentConfigurationManager.createDeploymentConfigurationHelper(DeploymentConfigurationManager.java:238)
         at com.bea.console.utils.DeploymentConfigurationManager.getDeploymentConfiguration(DeploymentConfigurationManager.java:104)
         at com.bea.console.utils.DeploymentConfigurationManager.getDeploymentConfiguration(DeploymentConfigurationManager.java:65)
         at com.bea.console.utils.PersistenceUtils.getPersistenceUnitNames(PersistenceUtils.java:76)
         at com.bea.console.utils.PersistenceUtils.hasPersistenceUnits(PersistenceUtils.java:52)
         at com.bea.console.utils.AppDeploymentBackingFile.preRender(AppDeploymentBackingFile.java:103)
         at com.bea.netuix.servlets.controls.Backable$Impl.preRender(Backable.java:191)
         at com.bea.netuix.servlets.controls.AdministeredBackableControl.preRender(AdministeredBackableControl.java:104)
         at com.bea.netuix.servlets.controls.window.Window.preRender(Window.java:432)
         at com.bea.netuix.servlets.controls.page.Page.preRender(Page.java:247)
         at com.bea.netuix.nf.ControlLifecycle$6.visit(ControlLifecycle.java:429)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:727)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
         at com.bea.netuix.nf.ControlTreeWalker.walkRecursivePreRender(ControlTreeWalker.java:739)
         at com.bea.netuix.nf.ControlTreeWalker.walk(ControlTreeWalker.java:146)
         at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:395)
         at com.bea.netuix.nf.Lifecycle.processLifecycles(Lifecycle.java:361)
         at com.bea.netuix.nf.Lifecycle.runOutbound(Lifecycle.java:208)
         at com.bea.netuix.nf.Lifecycle.run(Lifecycle.java:162)
         at com.bea.netuix.servlets.manager.UIServlet.runLifecycle(UIServlet.java:389)
         at com.bea.netuix.servlets.manager.UIServlet.doPost(UIServlet.java:258)
         at com.bea.netuix.servlets.manager.UIServlet.doGet(UIServlet.java:212)
         at com.bea.netuix.servlets.manager.UIServlet.service(UIServlet.java:196)
         at com.bea.netuix.servlets.manager.SingleFileServlet.service(SingleFileServlet.java:253)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:821)
         at com.bea.console.utils.MBeanUtilsInitSingleFileServlet.service(MBeanUtilsInitSingleFileServlet.java:47)
         at weblogic.servlet.AsyncInitServlet.service(AsyncInitServlet.java:131)
         at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
         at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
         at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:300)
         at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:27)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
         at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
         at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:57)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.doIt(WebAppServletContext.java:3684)
         at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3650)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2268)
         at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2174)
         at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1446)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    <Feb 10, 2012 10:47:28 AM IST> <Error> <Deployer> <BEA-149265> <Failure occurred in the execution of deployment request with ID '1328851041750' for task '0'. Error is: 'weblogic.management.DeploymentException: '
    weblogic.management.DeploymentException:
         at weblogic.application.internal.flow.BaseLifecycleFlow$CreateMainClassAction.run(BaseLifecycleFlow.java:270)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
         at weblogic.application.internal.flow.BaseLifecycleFlow$BaseAction.invoke(BaseLifecycleFlow.java:104)
         at weblogic.application.internal.flow.HeadLifecycleFlow.createMainClass(HeadLifecycleFlow.java:86)
         Truncated. see log file for complete stacktrace
    Caused By: java.lang.ClassNotFoundException: oracle.jrf.wls.StartupClassesAppExecutor
         at weblogic.utils.classloaders.GenericClassLoader.findLocalClass(GenericClassLoader.java:280)
         at weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClassLoader.java:253)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:303)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
         at weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClassLoader.java:177)
         Truncated. see log file for complete stacktrace
    >
    Thanks,
    Sanjeev

    Thanks Srinath! It worked, however nodemanager is not coming reachable from ADMIN console :(. nodemanager log contains
    <Feb 13, 2012 9:46:12 AM> <WARNING> <Uncaught exception in server handlerjavax.net.ssl.SSLHandshakeException: [Security:090476]Invalid/unknown SSL header was received from peer PUNITP196433D.ad.infosys.com - 10.76.246.81 during SSL handshake.>
    javax.net.ssl.SSLHandshakeException: [Security:090476]Invalid/unknown SSL header was received from peer PUNITP196433D.ad.infosys.com - 10.76.246.81 during SSL handshake.
         at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(Unknown Source)
         at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertSent(Unknown Source)
         at com.certicom.tls.record.ReadHandler.fireAlert(Unknown Source)
    Regards,
    Sanjeev

  • Node Manager starting managed servers under different users

    Hi all,
    I have multiple domains running on the same server.
    Is it possible to get node manager to start managed servers from different domains under different users?
    Default is the user under which node manager was started originally.
    Thanks
    Arnaud

    Oracle documentation is still in confussion state for Unix platform nodemanager.
    NodeManager Admin Guide had chapter 3 for General configuration of nodemanger. Chapter 5 is for script based nodemanager.
    In chapter 5 there is clear way defined for " Starting a node manger for Unix machine".
    chapter 3 is mess there is clear-cut direction to reach the remote startup of servers.
    Why we have so many types of nodemanager for connect. howbout start them?
    Can someone expert in Oracle WebLogic please respond to this.
    *Nodemanagers are NOT meant for multiuser development env.
    They are defined for production env and for HA, FailOver.*
    Edited by: PavanBhavanishekhar on Jan 6, 2010 9:10 PM

  • Start Admin Server using NodeManager without 'boot.properties'

    Hi All,
    I am trying to stat Admin Server using nodemanager through below code.
    public static void main(String args[]) {
              try{
              System.out.println("Starting...");
              InteractiveInterpreter  interpreter = new WLSTInterpreter();
              interpreter.exec("nmConnect('weblogic', 'weblogic123', '10.0.0.100', '5556', 'domain1','D:/oracle/MiddleWare/user_projects/domains/domain1','ssl')");
              interpreter.exec("nmServerStatus('AdminServer')");
              interpreter.exec("nmStart('AdminServer')");
              interpreter.exec("nmDisconnect()");
              System.out.println("End.");
              }catch(Exception ex){
                   System.out.println("Hello...");
                   ex.printStackTrace();
         }Everything is working fine but we need a property file 'boot.properties' under location 'Bea Home/user_projects/domain/domain1/servers/AdminServer/data/nodemanager' having username and password.
    Please let me know if there is any way to start Admin Server using nodemanager without using 'boot.properties' file.
    Is there any way to provide username and password directly to 'nmStart()' method.
    Please let me know...
    Edited by: Rajesh Panchal on Jun 14, 2011 1:56 AM

    Hi Rajesh,
    Maybe you are looking for something like:
    wls:/nm/IDMDomain> pr=makePropertiesObject("username=weblogic;password=weblogic0");
    wls:/nm/IDMDomain> nmStart('AdminServer',props=pr);
    Then, in your source code it should be something like:
    interpreter.exec("pr=makePropertiesObject('username=weblogic;password=weblogic0')");
    interpreter.exec("nmStart('AdminServer',props=pr)");
    Hope it works.
    -Cris

  • Problem in starting Managed Servers

    I am getting probelm in starting managed servers in WL 6.0,i tried with giving
    password while starting
    [wlerror.txt]

    I think your port number are conflicting.
    Check your port number for both the server
    "Shridhar" <[email protected]> wrote:
    >
    >
    >
    I am getting probelm in starting managed servers in WL 6.0,i tried with
    giving
    password while starting

Maybe you are looking for