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

Similar Messages

  • 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

  • Node Manager installed as service does not start managed servers. WLS 10.3

    Hi All,
    I have installed the node manager as a windows service. When the service starts up it does start the managed servers.
    In the nodemanager.log file it shows that the node manager is reading the startup.properties file for all of the managed servers.
    <Jul 24, 2009 6:38:13 AM> <INFO> <Loading domains file: C:\bea\WLSERV~1.3\common\NODEMA~1\nodemanager.domains>
    <Jul 24, 2009 6:38:13 AM> <INFO> <Loaded node manager configuration properties from 'C:\bea\WLSERV~1.3\common\nodemanager\nodemanager.properties'>
    <Jul 24, 2009 6:38:13 AM> <Info> <SalesIllustrationDomain> <IntegrationServer> <Startup configuration properties loaded from "C:\bea\user_projects\domains\SalesIllustrationDomain\servers\IntegrationServer\data\nodemanager\startup.properties">
    <Jul 24, 2009 6:38:13 AM> <Info> <SalesIllustrationDomain> <ProdBackupServer> <Startup configuration properties loaded from "C:\bea\user_projects\domains\SalesIllustrationDomain\servers\ProdBackupServer\data\nodemanager\startup.properties">
    <Jul 24, 2009 6:38:13 AM> <Info> <SalesIllustrationDomain> <QAServer> <Startup configuration properties loaded from "C:\bea\user_projects\domains\SalesIllustrationDomain\servers\QAServer\data\nodemanager\startup.properties">
    <Jul 24, 2009 6:38:13 AM> <INFO> <Plain socket listener started on port 5556, host localhost>
    The node manager properties file contains the following
    #Mon Apr 20 10:54:45 PDT 2009
    DomainsFile=C\:\\bea\\WLSERV~1.3\\common\\NODEMA~1\\nodemanager.domains
    LogLimit=0
    PropertiesVersion=10.3
    JavaHome=C\:\\bea\\JROCKI~1
    AuthenticationEnabled=false
    NodeManagerHome=C\:\\bea\\WLSERV~1.3\\common\\NODEMA~1
    LogLevel=INFO
    DomainsFileEnabled=true
    StartScriptEnabled=false
    StartScriptName=startWebLogic.cmd
    ListenAddress=localhost
    NativeVersionEnabled=true
    ListenPort=5556
    LogToStderr=true
    SecureListener=false
    LogCount=1
    StopScriptEnabled=false
    QuitEnabled=false
    LogAppend=true
    StateCheckInterval=500
    CrashRecoveryEnabled=true
    LogFile=C\:\\bea\\WLSERV~1.3\\common\\NODEMA~1\\nodemanager.log
    LogFormatter=weblogic.nodemanager.server.LogFormatter
    ListenBacklog=50
    The managed servers' boot.properties file and startup file are below
    boot.properties:
    #Thu Jul 23 13:48:26 PDT 2009
    CustomTrustKeyStoreFileName=C\:\\bea\\wlserver_10.3\\common\\ssl\\supportTrust2008.jks
    TrustKeyStore=CustomTrust
    password={3DES}mvtUK8oB8JEiQoVES4AQIQ\=\=
    CustomTrustKeyStorePassPhrase={3DES}34+15HRlP6qqpZX3bTPp+Q\=\=
    CustomTrustKeyStoreType=JKS
    username={3DES}P5mMHiWLnf2UtssZbQtezkDtIS0COiHW
    startup.properties:
    #Server startup properties
    #Thu Jul 23 13:48:27 PDT 2009
    Arguments=-Xms1024m -Xmx1024m -Xnohup
    JavaHome=C\:\\bea\\jrockit_160_05
    SSLArguments=-Dweblogic.security.SSL.ignoreHostnameVerification\=false -Dweblogic.ReverseDNSAllowed\=false
    RestartMax=2
    RestartDelaySeconds=0
    RestartInterval=3600
    BeaHome=C\:\\bea
    ClassPath=C\:\\bea\\user_projects\\domains\\SalesIllustrationDomain\\servers\\lib\\itext\\WEB-INF\\lib\\itext.jar;C\:\\bea\\wlserver_10.3\\server\\lib\\weblogic_sp.jar;C\:\\bea\\wlserver_10.3\\server\\lib\\weblogic.jar;C\:\\bea\\user_projects\\domains\\SalesIllustrationDomain\\servers\\ProdBackupServer\\applications\\massmutual\\WEB-INF\\classes\\;C\:\\bea\\user_projects\\domains\\SalesIllustrationDomain\\servers\\ProdBackupServer\\applications\\assuritylife\\WEB-INF\\classes\\;C\:\\bea\\user_projects\\domains\\SalesIllustrationDomain\\servers\\ProdBackupServer\\applications\\minnesotalife\\WEB-INF\\classes\\;C\:\\bea\\user_projects\\domains\\SalesIllustrationDomain\\servers\\ProdBackupServer\\lib\\ltclibrary\\WEB-INF\\classes\\
    AdminURL=http\://localhost\:7001
    JavaVendor=BEA
    AutoRestart=true
    AutoKillIfFailed=false
    I am wondering if I left out a parameter some where.
    Any help would be greatly appreciated.
    Thanks,
    Greg

    First of all, I assume you mean "... up it does NOT start ..."?
    It might be helpful to point out that the purpose of the NodeManager is not to start the servers, but to "control" the servers through remote commands. When the NodeManager starts back up, it tries to reset the servers to the last known state it set them to, based on remote commands.
    For instance, if your system was running and you stopped the servers through the admin console and then restarted the machine, the NodeManager would not start the servers on machine startup, because the last controlled state of the servers was down. If all of your WebLogic servers were running as a result of NodeManager commands, and you pulled the plug on the box, when you restarted the machine, the NodeManager probably would restart the servers.

  • 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>

  • 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

  • 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

  • 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.

  • Multicast Error When Starting Managed Servers

    Environment: HP-UX 11i, Weblogic 8.1 SP1.
              We're getting the following error when we start managed servers in our clustered environment:
              <Feb 24, 2004 6:33:12 PM CST> <Error> <Cluster> <BEA-000116> <Failed to join cluster PDICluster at address 2
              37.0.0.1 due to: java.net.SocketException: Can't assign requested address.
              java.net.SocketException: Can't assign requested address
              at java.net.PlainDatagramSocketImpl.join(Native Method)
              at java.net.PlainDatagramSocketImpl.join(PlainDatagramSocketImpl.java:134)
              at java.net.MulticastSocket.joinGroup(MulticastSocket.java:274)
              at weblogic.cluster.FragmentSocket.initializeMulticastSocket(FragmentSocket.java:92)
              at weblogic.cluster.FragmentSocket.start(FragmentSocket.java:109)
              at weblogic.cluster.MulticastManager.startListening(MulticastManager.java:164)
              at weblogic.cluster.ClusterCommunicationService.initialize(ClusterCommunicationService.java:52)
              at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:922)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:664)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:342)
              at weblogic.Server.main(Server.java:32)
              >
              We also get the same error when we try the util.multicastTest application. So far, we've done the following things to troubleshoot this:
              1) Different multicast addresses/ports;
              2) The util.multicastTest app.
              3) We're researching whether or machine or network may be causing this, but since the admin. server and managed servers are running on the same server, I don't see how the network could be causing this.
              Can anyone give me any ideas as to what might be going wrong? We've set this up on other machines before with the same OS and same version of Weblogic. So I'm at a loss at the moment as to what might be going wrong.
              Thanks in advance for any help...
              Brian
              

    Environment: HP-UX 11i, Weblogic 8.1 SP1.
              We're getting the following error when we start managed servers in our clustered environment:
              <Feb 24, 2004 6:33:12 PM CST> <Error> <Cluster> <BEA-000116> <Failed to join cluster PDICluster at address 2
              37.0.0.1 due to: java.net.SocketException: Can't assign requested address.
              java.net.SocketException: Can't assign requested address
              at java.net.PlainDatagramSocketImpl.join(Native Method)
              at java.net.PlainDatagramSocketImpl.join(PlainDatagramSocketImpl.java:134)
              at java.net.MulticastSocket.joinGroup(MulticastSocket.java:274)
              at weblogic.cluster.FragmentSocket.initializeMulticastSocket(FragmentSocket.java:92)
              at weblogic.cluster.FragmentSocket.start(FragmentSocket.java:109)
              at weblogic.cluster.MulticastManager.startListening(MulticastManager.java:164)
              at weblogic.cluster.ClusterCommunicationService.initialize(ClusterCommunicationService.java:52)
              at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:922)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:664)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:342)
              at weblogic.Server.main(Server.java:32)
              >
              We also get the same error when we try the util.multicastTest application. So far, we've done the following things to troubleshoot this:
              1) Different multicast addresses/ports;
              2) The util.multicastTest app.
              3) We're researching whether or machine or network may be causing this, but since the admin. server and managed servers are running on the same server, I don't see how the network could be causing this.
              Can anyone give me any ideas as to what might be going wrong? We've set this up on other machines before with the same OS and same version of Weblogic. So I'm at a loss at the moment as to what might be going wrong.
              Thanks in advance for any help...
              Brian
              

  • Using wlserver to start managed servers

    Hi, all. I was wondering if someone could help me out in understanding how wlserver works. I'm using WL 8.4SP4. I have a cluster with two nodes, and I have the node manager configured properly. I can log in to the Admin console and start and stop the nodes (one of which is on a seperate machine than the admin server). I would like to be able to do this using wlserver in Ant on my local machine (not the Admin server machine), but it seems like it wants to use local jar files to start the managed server locally (wants me to give it beahome and weblogichome). I want to point it to the admin server and just tell it the node in the cluster to start. Is this possible?

    I don't know what commands you use in ant script. Maybe this will help you:
    http://e-docs.bea.com/wls/docs81/admin_ref/cli9.html#1193968
    You can use weblogic.Admin (This is a java command tool utils provided by
    WebLogic) to start your managed servers. But you should do some work before
    using this tool, see
    http://e-docs.bea.com/wls/docs81/admin_ref/cli.html#1346187 "Required
    Environment for the weblogic.Admin Utility" to get more information.
    <David Matheson> wrote in message news:[email protected]..
    Hi, all. I was wondering if someone could help me out in understanding
    how wlserver works. I'm using WL 8.4SP4. I have a cluster with two
    nodes, and I have the node manager configured properly. I can log in to
    the Admin console and start and stop the nodes (one of which is on a
    seperate machine than the admin server). I would like to be able to do
    this using wlserver in Ant on my local machine (not the Admin server
    machine), but it seems like it wants to use local jar files to start the
    managed serve
    r locally (wants me to give it beahome and weblogichome). I want to point
    it to the admin server and just tell it the node in the cluster to start.
    Is this possible?

  • How to start managed servers simultaneously using WLST?

    Hi folks,
    I am trying to write a simple script to provide a simple way to bounce my env, I am pretty much done. However, my script now starts (and stops) the managed servers sequentially which is not what I wanted.
    I am wondering if there is a way to start (and stop) the managed servers within a domain in parallel as I can definitely do that using Admin Console.
    I do have an idea in mind:
    Write a simple python script to start/stop a single managed server, then use another shell script to trigger the python script in background mode.
    But I think this approach is really ugly, and am wondering if there is a native way to do that in WLST.
    Thanks for your repose in advance.

    This does not solve my problem, what I am trying to do is to being a an indefinite about of managed servers at the same time, not all the managed servers.
    For example, suppose I have 5 clusters in a domain, and there are 3 servers in each cluster. I might want to bring up all the major servers first at the same time,
    which mean to bring up one server in each cluster at the same time.
    Please help.

  • Error while starting managed servers in a cluster

    Hi,
              I have Weblogic 8.1.3 deployed on my system. We've have a Ant script that set's up the project domain etc. We have an admin server and two other managed servers which are part of a cluster. I am able to start the admin server and access the admin console without any errors. However when I start any of the managed servers in the cluster, using the following command (startManagedWebLogic.cmd Reactor-1 http://localhost:80 OR startManagedWebLogic.cmd Reactor-2 http://localhost:80)
              I get the error listed below. The same Ant script was used to setup the project on another system and it worked but I haven't been able to set it up on my system.
              The error says that it could be due to servers having duplicate names in the cluster but thats not the case here, the managed servers are named Reactor-1 and 2.
              Also, the IP address being accessed, 192.168.141.50:81 is not my system, its another system on the network. I've done a full text search for the IP address but I've not been able to find it in ANY file under c:\bea.
              Can someone please tell me if I've missed something? I'd appreciated any help with this.
              Thanks
              Ameeth
              <Mar 21, 2005 4:52:43 PM GMT+05:30> <Notice> <Cluster> <BEA-000142> <Trying to download cluster JNDI tree from server Reactor-1
              .>
              <Mar 21, 2005 4:52:44 PM GMT+05:30> <Warning> <Net> <BEA-000905> <Could not open connection with host: 127.0.0.1 and port: 81.>
              <Mar 21, 2005 4:52:44 PM GMT+05:30> <Error> <Cluster> <BEA-000141> <TCP/IP socket failure occurred while fetching statedump ove
              r HTTP from Reactor-1.
              java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP to server: '127.0.0.1', port: '81'
              at weblogic.net.http.HttpClient.openServer(Ljava.lang.String;I)V(HttpClient.java:275)
              at weblogic.net.http.HttpClient.openServer()V(HttpClient.java:329)
              at weblogic.net.http.HttpClient.<init>(Ljava.net.URL;Lweblogic.security.SSL.SSLClientInfo;Lweblogic.security.SSL.SSLSoc
              ketFactory;I)V(HttpClient.java:128)
              at weblogic.net.http.HttpClient.New(Ljava.net.URL;Lweblogic.security.SSL.SSLClientInfo;Lweblogic.security.SSL.SSLSocket
              Factory;I)Lweblogic.net.http.HttpClient;(HttpClient.java:196)
              at weblogic.net.http.HttpURLConnection.connect()V(HttpURLConnection.java:119)
              at weblogic.cluster.MemberManager.waitForSync(J)V(MemberManager.java:213)
              at weblogic.cluster.MemberManager.waitToSyncWithCurrentMembers()V(MemberManager.java:160)
              at weblogic.cluster.ClusterCommunicationService.initialize()V(ClusterCommunicationService.java:58)
              at weblogic.t3.srvr.T3Srvr.initializeHere()V(T3Srvr.java:924)
              at weblogic.t3.srvr.T3Srvr.initialize()V(T3Srvr.java:670)
              at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String)I(T3Srvr.java:344)
              at weblogic.Server.main([Ljava.lang.String)V(Server.java:32)
              >
              <Mar 21, 2005 4:52:47 PM GMT+05:30> <Notice> <Security> <BEA-090170> <Loading the private key stored under the alias DemoIdenti
              ty from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
              <Mar 21, 2005 4:52:47 PM GMT+05:30> <Notice> <Security> <BEA-090171> <Loading the identity certificate stored under the alias D
              emoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
              <Mar 21, 2005 4:52:47 PM GMT+05:30> <Warning> <WebLogicServer> <BEA-000311> <Attempting to use low strength (exportable) certif
              icates with a full strength (domestic) license.>
              <Mar 21, 2005 4:52:47 PM GMT+05:30> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C
              :\bea\weblogic81\server\lib\DemoTrust.jks.>
              <Mar 21, 2005 4:52:47 PM GMT+05:30> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C
              :\bea\JROCKI~1\jre\lib\security\cacerts.>
              <Mar 21, 2005 4:52:48 PM GMT+05:30> <Notice> <WebLogicServer> <BEA-000355> <Thread "SSLListenThread.Default" listening on port
              7002, ip address 127.0.0.1>
              <Mar 21, 2005 4:52:48 PM GMT+05:30> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default" listening on port 81,
              ip address 127.0.0.1>
              <Mar 21, 2005 4:52:48 PM GMT+05:30> <Notice> <Cluster> <BEA-000102> <Joining cluster ReactorCluster on 237.0.0.1:7001>
              <Mar 21, 2005 4:52:48 PM GMT+05:30> <Notice> <WebLogicServer> <BEA-000332> <Started WebLogic Managed Server "Reactor-1" for dom
              ain "ReactorAdminServer" running in Development Mode>
              <Mar 21, 2005 4:52:48 PM GMT+05:30> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
              <Mar 21, 2005 4:52:51 PM GMT+05:30> <Warning> <Net> <BEA-000905> <Could not open connection with host: 127.0.0.1 and port: 82.>
              <Mar 21, 2005 4:52:52 PM GMT+05:30> <Error> <Cluster> <BEA-000141> <TCP/IP socket failure occurred while fetching statedump ove
              r HTTP from 8288749592481618145S:localhost:[81,81,-1,-1,81,-1,-1,0,0]:192.168.141.50:81,192.168.141.50:82:ReactorAdminServer:Re
              actor-1.
              java.io.IOException: Reference to server no longer exists.
              Possible reasons for failure include having servers with duplicate names running on a cluster. Please check your configuratio
              n for this error.
              at weblogic.rmi.cluster.ServerInfoManager.updateServerInfo(Lweblogic.rmi.cluster.ServerInfo)V(ServerInfoManager.java:1
              11)
              at weblogic.rmi.cluster.ServerInfoManager.readUpdate(Ljava.lang.Object)V(ServerInfoManager.java:95)
              at weblogic.cluster.MemberAttributes.readExternal(Ljava.io.ObjectInput)V(MemberAttributes.java:103)
              at java.io.ObjectInputStream.readExternalData(Ljava.io.Externalizable;Ljava.io.ObjectStreamClass)V(Unknown Source)
              at java.io.ObjectInputStream.readOrdinaryObject(Z)Ljava.lang.Object;(Unknown Source)
              at java.io.ObjectInputStream.readObject0(Z)Ljava.lang.Object;(Unknown Source)
              at java.io.ObjectInputStream.readObject()Ljava.lang.Object;(Unknown Source)
              at weblogic.cluster.HTTPExecuteRequest.execute(Lweblogic.kernel.ExecuteThread)V(HTTPExecuteRequest.java:91)
              at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest)V(ExecuteThread.java:219)
              at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
              at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread)V(Unknown Source)

    make sure you use a unique cluster multicast ip address. are you sure that your etc/hosts file has proper entries for localhost?

  • While starting managed servers asks for password of localhost

    We have a clustered environment and we are using Virtual IPs for the Managed servers. The managed servers in the forst node is not starting.
    The problem I have narrowed down is that there are startup.properties file for the managed servers.
    It has argument like -Dtangosol.coherence.localhost\=xgsoapd5v1.ea.com (for SOA1)
    While SOA1 it is asking for password for the above host and the managed server is not starting.
    Now SOA2 has the similar argument -Dtangosol.coherence.localhost\=xgsoapd5v2.ea.com (for SOA2), but it is not asking for any password and so the SOA2 managed server is sta! rting.
    Similarly the while starting BAM1 it is asking for a password , but for BAM2 it is not asking for password and it is starting.
    I could not yet figure out why it is behaving differently in the first node.
    This is a copy of production with a chnage in the network. That means only the IP addresses are changed. xgsoapd5v1.ea.com and xgsoapd5v2.ea.com are the hostnames
    It works perfectly in production environment.

    Hi
    Under your domain root folder say in the main machine where you have the AdminServer, you should have a folder structure something like this:
    ../user_projects/domains/yourBPMDomain1/servers. Under the servers folder you can see list of each server. On the main machine you will see one AdminServer folder. Under this there should be a sub-folder named security with one file named boot.properties. This boot.properties file will have encrypted username and password for the weblogic domain.
    If this security/boot.properties exist under the each server folder, then when you start the managed server, it will NOT prompt for the username/password. If it DO NOT exist, it will ask for the credentials.
    Solution is go to each Machine where you the ManagedServers (SOA Server or BAM Server does not matter). Go to each server and under that create a folder named security and create a file named boot.properties and in this file enter plain text username and password something like this and save the file. Now restart all those servers.
    username=domainadminusername
    password=doaminadminpassword
    When you start the servers, server should start taking the above information. AND server will automatically ENCRYPT the above plain text data into hash codes.
    In a nut shell, go to each Server folder across all the remote machines and under that particular managed server create a folder security with one file boot.properties.
    Exmaple locations:
    On Machine1 - user_projects/domains/bpmDomain1/servers/soa_server1/security/boot.properties
    On Machine2 - user_projects/domains/bpmDomain1/servers/bam_server1/security/boot.properties
    You DO NEED the admin username and password in plain text for one time to put in boot.properties. Later on it will get encrypted, so there is no threat for any security loop holes.
    Thanks
    Ravi Jegga

  • Have NodeManager start managed servers on machine reboot

    Is there any way to have the Node Manager start all the managed servers belonging to a domain when a server reboots?
    I know I could create a separate Windows service for each of the managed servers I want running when the server comes on-line, or I could do some fancy scripting at start-up to connect to the Node Manager and have it start the managed servers.
    But I was hoping there would be a more elegant way of having the NM start them when it comes on-line.
    Ideas appreciated,
    dmac.

    Hi Dmac,
    To achieve this in Windows, you must consider the following WLS Components:
    1. Node Manager
    2. Admin Server
    3. Managed Server
    Node Manager
    For Node Manager, if you want the component to start automatically on boot up, your best option is to create a Windows Service. You may have selected the option to create a service for Node Manager during the WebLogic Server installation. Use Start -> Run -> services.msc from the Start menu to load the Windows Services Manager. If there is no service for Node Manager, use the following steps to create one.
    Create a Windows service for Node Manager:
    1. WL_HOME\server\bin\installNodeMgrSvc.cmd
    2. Verify in Windows Services that a service was created.
    Admin Server
    For the Admin Server, you can also create a Windows Service. Here are the steps for doing so:
    Create a Windows service for the Admin Server
    1. Create a text file named %MIDDLEWARE_HOME%\user_projects\domains\<domain name>\servers\AdminServer\security\boot.properties. Add the following lines:
    username=weblogic
    password=<the weblogic username password>
    2. Create a command script called installAdmServer_Service.cmd which you will want to make sure has lines like:
    SETLOCAL
    set DOMAIN_NAME=<your wls domain>
    set USERDOMAIN_HOME=<path to domain> # e.g., C:\middleware\FMW11g\user_projects\domains\ClassicDomain
    set SERVER_NAME=AdminServer
    set PRODUCTION_MODE=true
    cd %USERDOMAIN_HOME%
    call %USERDOMAIN_HOME%\bin\setDomainEnv.cmd
    call "<your middleware home>\wlserver_10.3\server\bin\installSvc.cmd"
    ENDLOCAL
    3. For troubleshooting/debugging purposes it is helpful to redirect standard out and error to a text file. Although most information is captured in the AdminServer server log files, you will not see all standard out and error when the server is started via a MS Windows Service (unlike when you start an AdminServer from the command prompt using startWebLogic.cmd). To redirect standard out to a text file, backup and edit installSvc.cmd and change the line at the bottom of the file so it includes the -log parameter, e.g.
    "%WL_HOME%\server\bin\beasvc" -install -svcname:"%DOMAIN_NAME%_%SERVER_NAME%" -javahome:"%JAVA_HOME%" -execdir:"%USERDOMAIN_HOME%" -extrapath:"%WL_HOME%\server\bin" -password:"%WLS_PW%" -cmdline:%CMDLINE% -log:"<your middleware home>\user_projects\domains\<your wls domain name>\servers\AdminServer\logs\AdminServer-stdout.txt"
    4. Now run "installAdmServer_Service.cmd." The Service should be installed. It will have a name like "beasvc %DOMAIN_NAME%_%SERVER_NAME%" (e.g. beasvc ClassicDomain_AdminServer). The Service "Startup Type" will be "Automatic." Start the Service. The Service will come back fairly quickly to say it is started. The actual time taken for the admin server to start and reach a state of 'RUNNING' will be longer - perhaps two or three minutes. The state of the server can be monitored by reviewing the stdout txt file.
    Managed Server
    For the Managed Server, you can also create a Windows Service. Here are the steps for doing so:
    Create a Windows service for the Managed Server (using wls_forms as an example)
    1. Create a text file named %MIDDLEWARE_HOME%\user_projects\domains\<domain name>\servers\WLS_FORMS\security\boot.properties. Add the following lines:
    username=weblogic
    password=<the weblogic username password e.g manager11g>
    2. Create a command script called installWLSFORMS_Service.cmd which has lines like
    SETLOCAL
    set DOMAIN_NAME=<your wls domain>
    set USERDOMAIN_HOME=<path to domain> # e.g. C:\middleware\FMW11g\user_projects\domains\ClassicDomain
    set SERVER_NAME=WLS_FORMS
    set PRODUCTION_MODE=true
    set ADMIN_URL=http://mymachine.mycompany.com:7001
    cd %USERDOMAIN_HOME%
    call %USERDOMAIN_HOME%\bin\setDomainEnv.cmd
    call "<your middleware home>\wlserver_10.3\server\bin\installSvc.cmd"
    ENDLOCAL
    NOTES:
    a. The ADMIN_URL value should reference the AdminServer hostname and listen port.
    b. The SERVER_NAME value is case sensitive. For example, if you are creating a MS Windows service for a different managed server such as 'wls_ods1' then the value needs to match the case of the server name otherwise the startup of the server via the MS Windows service will fail.
    c. Be careful that there are no trailing spaces after each line in the command file - trailing spaces will cause the managed server to fail at startup. For example a trailing space in the ADMIN_URL value will result in the error
    <19-Jan-2010 11:37:58 o'clock GMT> <Error> <EmbeddedLDAP> <BEA-171524> <Cannot determine the Listen address for the Admin server
    3. Now run "installWLSFORMS_Service.cmd." The Service should be installed, it will have a name like "beasvc %DOMAIN_NAME%_%SERVER_NAME%" (e.g. beasvc ClassicDomain_WLS_FORMS). The Service "Startup Type" will be "Automatic." Start the Service. The Service will come back fairly quickly to say it is started. The actual time taken for the managed server to start and reach a state of 'RUNNING' will be longer - perhaps two or three minutes. The state of the server can be monitored by reviewing the stdout txt file.
    Configuring the Windows service to restart upon failure
    As with any Windows Service, it is possible to configure the service to restart itself upon failure. These are standard options available when configuring a Windows Service in the context of Windows Services Manager. However, it is important to understand that Windows Services Manager only monitors the JVM process. If the JVM process fails (shuts down), then Windows Services Manager will attempt to restart it. But there are some scenarios where the Admin Server or Managed Server may go into an unhealthy or failed state but the JVM is still running. The Windows Service will not know to restart the process in these cases, whereas if the Admin Server and Managed Server had been started using Node Manager, Node Manager would recognize such a state and restart the process accordingly. So it may be desirable to start Node Manager with a Windows Service and then start the Admin Server and Managed Servers with Node Manager to take advantage of this monitoring feature. Below you will find one such example of how to do this.
    Example of starting the Admin Server and a Managed Server using Node Manager
    1. Create a batch script similar to this:
    Myscript.cmd
    call D:\Product\Oracle\Middleware\user_projects\domains\base_domain\bin\setDomainEnv.cmd
    java weblogic.WLST D:\Product\Oracle\Middleware\user_projects\domains\base_domain\ServerStart.py
    2. Create a Python script similar to this:
    ServerStart.py
    nmConnect('weblogic', 'welcome1', '192.168.0.101', '5556', 'base_domain','D:\Product\Oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1','ssl')
    nmStart('AdminServer')
    connect ('weblogic','welcome1','t3://192.168.0.101:7001')
    nmstart('myserver','Server','t3://192.168.0.101:7002')
    If you want this to happen automatically on boot up, you can run the script (myscript.cmd) from the Windows Scheduler. You must configure the scheduler to run the script on system startup. This will execute the script without requiring an interactive login to Windows (unattended).
    Some Additional Information to Remember
    The startup.properties file for the Admin and Managed servers must have "AutoRestart=true." This can be set in the "Health Monitoring" tab for each respective server in the WLS console.
    The boot.properties file must be configured and present for each server that you plan to start automatically so that you are not prompted for the user name and password each time. If you are not currently prompted when you start the servers then it is already done.
    The nodemanager.properties file must have "StartScriptEnabled=true" and "StartScriptName=StartWeblogic.cmd" in place.

  • How nodemanager starts managed servers?

    Hello All,
    I'm facing strange issue with weblogic server. Currently i'm using WLS 8.1 SP 4 on solaris 9 server.
    To start weblogic i have customize the script such that when server goes on reboot it will pick the startweblogic.sh script from /opt/bin and start the weblogic. Where as in startweblogic.sh i have mentioned -
    NMLOG=/u001/wls8/bea/user_projects/prodDomain/logs/optbin/nodemanager.log; export WL8NMLOG
    ADMINLOG=/u001/wls8/bea/user_projects/prodDomain/logs/optbin/adminserver.log; export WL8ADMINLOG
    CLUSTERLOG=/u001/wls8/bea/user_projects/prodDomain/logs/optbin/cluster.log; export WL8CLUSTERLOG
    cd /u001/wls8/bea/weblogic81/server/bin/
    su weblogic -c "./startNodeManager.sh >> $NMLOG 2>&1" &
    sleep 60
    cd /u001/wls8/bea/user_projects/prodDomain/
    su weblogic -c "./startadminserver.sh >> $ADMINLOG 2>&1" &
    sleep 1200
    cd /u001/wls8/bea/user_projects/prodDomain/
    su weblogic -c "./startcluster.sh >> $CLUSTERLOG 2>&1" &
    Though the script works as expected till adminserver is UP/Running, but script doesn't wait for 1200 secs. to start cluster. Somehow nodemanager starts the managed servers immediately after the adminserver is UP.
    I have checked the nodemanager.properties file, there is nothing such mentioned. Also, from console i have unchecked the option of AutoStart for both managed servers.
    Can anyone tell me how nodemanager starts the managed servers automatically??
    Thanks,
    HK

    can you please tell me what is this .startCluster.sh script.
    is it your custom script?
    And the idea i have in my mind is that after
    cd /u001/wls8/bea/weblogic81/server/bin/
    su weblogic -c "./startNodeManager.sh >> $NMLOG 2>&1" &
    sleep 60
    cd /u001/wls8/bea/user_projects/prodDomain/
    su weblogic -c "./startadminserver.sh >> $ADMINLOG 2>&1" &
    sleep 1200
    you can give the command to start the individual managed servers like:
    cd /u001/wls8/bea/user_projects/prodDomain/
    su weblogic -c "./startManagedWebLogic.sh <arguments> >> $CLUSTERLOG 2>&1" &
    I think this way it will work....

  • Error while starting Managed server in wls

    I am using WebLogic Server Version: 10.3.4.0. I have created one managed server thru admin console. I am starting managed server using startManagedWebLogic.cmd batch file. Chnages I made in this cmd file is added managed server name and wls userid/password.
    When execute this, I get below error:
    Server
    Exception in thread "Main Thread" java.lang.NoClassDefFoundError: weblogic/Server
    Caused by: java.lang.ClassNotFoundException: weblogic.Server
    at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
    at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
    at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
    Could not find the main class: weblogic.Server.  Program will exit.
    The contents of the startManagedWebLogic.cmd is as below:
    @ECHO OFF
    @REM WARNING: This file is created by the Configuration Wizard.
    @REM Any changes to this script may be lost when adding extensions to this configuration.
    SETLOCAL
    @REM --- Start Functions ---
    GOTO :ENDFUNCTIONS
    :usage
         echo Need to set SERVER_NAME and ADMIN_URL environment variables or specify
         echo them in command line:
         echo Usage: %1 SERVER_NAME {ADMIN_URL}
         echo for example:
         echo %1 managedserver1 http://localhost:7001
    GOTO :EOF
    :ENDFUNCTIONS
    @REM --- End Functions ---
    @REM *************************************************************************
    @REM This script is used to start a managed WebLogic Server for the domain in
    @REM the current working directory. This script can either read in the SERVER_NAME and
    @REM ADMIN_URL as positional parameters or will read them from environment variables that are
    @REM set before calling this script. If SERVER_NAME is not sent as a parameter or exists with a value
    @REM as an environment variable the script will EXIT. If the ADMIN_URL value cannot be determined
    @REM by reading a parameter or from the environment a default value will be used.
    @REM
    @REM For additional information, refer to "Managing Server Startup and Shutdown for Oracle WebLogic Server"
    @REM (http://download.oracle.com/docs/cd/E17904_01/web.1111/e13708/overview.htm)
    @REM *************************************************************************
    @REM Set SERVER_NAME to the name of the server you wish to start up.
    Set SERVER_NAME=*ManagedServer1*
    set DOMAIN_NAME=mydomain
    set ADMIN_URL=http://localhost:7001
    @REM Set WLS_USER equal to your system username and WLS_PW equal
    @REM to your system password for no username and password prompt
    @REM during server startup. Both are required to bypass the startup
    @REM prompt.
    set WLS_USER=*weblogic*
    set WLS_PW=*weblogic1*
    @REM Set JAVA_OPTIONS to the java flags you want to pass to the vm. i.e.:
    @REM set JAVA_OPTIONS=-Dweblogic.attribute=value -Djava.attribute=value
    set JAVA_OPTIONS=-Dweblogic.security.SSL.trustedCAKeyStore="d:\Perforce\weblogic1\src_16020jr\bea\wlserver_10.3\server\..\server\lib\cacerts" %JAVA_OPTIONS%
    @REM Set JAVA_VM to the java virtual machine you want to run. For instance:
    @REM set JAVA_VM=-server
    set JAVA_VM=
    @REM Set SERVER_NAME and ADMIN_URL, they must by specified before starting
    @REM a managed server, detailed information can be found at
    @REM http://download.oracle.com/docs/cd/E17904_01/web.1111/e13708/overview.htm
    if "%1"=="" (
         if "%SERVER_NAME%"=="" (
              CALL :usage %0
              GOTO :EOF
    ) else (
         set SERVER_NAME=%1
         shift
    if "%1"=="" (
         if "%ADMIN_URL%"=="" (
              CALL :usage %0
              GOTO :EOF
    ) else (
         set ADMIN_URL=%1
         shift
    @REM Export the admin_url whether the user specified it OR it was sent on the command-line
    set ADMIN_URL=%ADMIN_URL%
    set SERVER_NAME=%SERVER_NAME%
    set DOMAIN_HOME=D:\Perforce\weblogic1\dev\src_crmod\wls\mytest
    if "%1"=="" (
         @REM Call Weblogic Server with our default params since the user did not specify any other ones
         call "%DOMAIN_HOME%\bin\startWebLogic.cmd" nodebug noderby noiterativedev notestconsole noLogErrorsToConsole
    ) else (
         @REM Call Weblogic Server with the params the user sent in INSTEAD of the defaults
         call "%DOMAIN_HOME%\bin\startWebLogic.cmd" %1 %2 %3 %4 %5 %6 %7 %8 %9
    ENDLOCAL
    Any help is really appreciated.

    I could see calling to setDomainEnv.cmd script:
    *@REM Call setDomainEnv here.*
    set DOMAIN_HOME=D:\Perforce\weblogic1\dev\src_crmod\wls\mytest
    for %%i in ("%DOMAIN_HOME%") do set DOMAIN_HOME=%%~fsi
    call "%DOMAIN_HOME%\bin\setDomainEnv.cmd" %*
    set SAVE_JAVA_OPTIONS=%JAVA_OPTIONS%
    set SAVE_CLASSPATH=%CLASSPATH%
    But in my environment I do not see these variable set to any, JAVA_HOME, DERBY_CLASSPATH, JAVA_OPTIONS, CLASS_PATH.
    This might be the issue? Or anything else?

Maybe you are looking for