Admin server is part of cluster?

          I have setup a cluster using on 2 unix boxes. 1 unix box contains 1 WL server
          that is both the admin server and a member of the cluster. It appears to be working
          ok.
          Will this cause me problems later?
          

          Admin server should not be part of cluster.
          Venkat
          "Bobbo" <[email protected]> wrote:
          >
          >I have setup a cluster using on 2 unix boxes. 1 unix box contains 1
          >WL server
          >that is both the admin server and a member of the cluster. It appears
          >to be working
          >ok.
          >
          >Will this cause me problems later?
          

Similar Messages

  • Error starting Admin Server in a OSB Cluster installation

    Greetings
    I have an environment with two osb nodes in cluster, when I start the Admin server the server start succesfully and the osb servers also works fine, but I got the following messages starting the admin server:
    <Oct 12, 2012 5:52:04 PM COT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.file. The Error was:
    The destination for the MDB PolledMessageListenerMDBEJB(Application: File Transport Provider, EJBComponent: filepoll.jar) could not be resolved at this time. Please ensure the destination is available at the JNDI name wlsb.internal.transport.task.queue.file. The EJB container will periodically attempt to resolve this MDB destination and additional warnings may be issued.>
    <Oct 12, 2012 5:52:04 PM COT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.sftp. The Error was:
    The destination for the MDB PolledMessageListenerMDBEJB(Application: SFTP Transport Provider, EJBComponent: sftp_transport.jar) could not be resolved at this time. Please ensure the destination is available at the JNDI name wlsb.internal.transport.task.queue.sftp. The EJB container will periodically attempt to resolve this MDB destination and additional warnings may be issued.>
    <Oct 12, 2012 5:52:04 PM COT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.ftp. The Error was:
    The destination for the MDB PolledMessageListenerMDBEJB(Application: Ftp Transport Provider, EJBComponent: ftp_transport.jar) could not be resolved at this time. Please ensure the destination is available at the JNDI name wlsb.internal.transport.task.queue.ftp. The EJB container will periodically attempt to resolve this MDB destination and additional warnings may be issued.>
    <Oct 12, 2012 5:52:04 PM COT> <Warning> <EJB> <BEA-010061> <The Message-Driven EJB: PolledMessageListenerMDBEJB is unable to connect to the JMS destination: wlsb.internal.transport.task.queue.email. The Error was:
    The destination for the MDB PolledMessageListenerMDBEJB(Application: Email Transport Provider, EJBComponent: emailtransport.jar) could not be resolved at this time. Please ensure the destination is available at the JNDI name wlsb.internal.transport.task.queue.email. The EJB container will periodically attempt to resolve this MDB destination and additional warnings may be issued.>
    I am worried because I see in the deployment screen that the applications File Transport Provider, SFTP Transport Provider, Ftp Transport Provider and Email Transport Provider are not running.
    How can I solve this issue?
    My installation is osb 11.1.1.6 and my operating system is solaris 11 (64 bits)
    Thanks!

    Hi Charan,
    if your ManagedServers are not in Configured for MSI Mode (Managed Server Indepence Mode) then you wont be able to start your Servers until the AdminServer is Already Running. I can see that the Exception u pasted that...your AdminServer is not reachable....It may be due to AdminServer Vs ManagedServer BOX Network Issue or Your AdminServer might be down when u tried to start the ManagedServer.
    Thanks
    Jay SenSharma
    http://weblogic-wonders.com/weblogic (WebLogic Wonders Are Here)

  • Admin server can't see session info when app is running in cluster

    All,
              We have 3 servers running WL6.0 sp1, 1 is running the admin server and the
              other 2 are running as part of a cluster.
              We have a web application that has been deployed to the cluster and is set
              for PersistantStoreType equal to replicated.
              Enable session monitoring is set.
              If one of the servers in the cluster is running and we connect to the admin
              server we can see both the servelet and session statistics for the
              application.
              If both servers are up and running, we can see the servelet statistics for
              both servers but the session information is always 0.
              Is this a bug or is there something else we need to have set.
              Thanks
              Eric
              

    Is this what you are looking for?
    monitor = new URLMonitor(new URLRequest("http://localhost/gateway.php"));
                   monitor.addEventListener(StatusEvent.STATUS,onStatus);
                    monitor.pollInterval = 5000;
                    monitor.start();
    I use it to poll a server every five seconds and when there is a change is status to connected it triggers the onStatus function I have defined elsewhere. Learned it from Lynda.com's videos...

  • About cluster and admin server

    I try to implement cluster like this
              admin server
              |
              |
              | |
              | mycluster |
              server1 server2
              (web) (web)
              admin server start as Administrator server
              server1 and server2 start as managed server. and all in mycluster. web has
              depoloyed to server1 and server2, but not deployed to admin server
              when I start admin server. it always say "web dot found". Why?
              

              airwing wrote:
              > What I say ''all in mycluster" does include admin server. In fact, I need
              > not include admin server in mycluster. but if not include, cluster services
              > will not start. I do not know how to solve.
              >
              That's not true. Starting a cluster has nothing to do with admin server.
              Infact we always recommend to exclude admin server from cluster view.
              >
              > web is not targetted to admin server. it targetted to server1 and server2.
              >
              If web is not targetted to admin server, how are you able to access this webapp
              from admin server.
              >
              > I do not know how to access web by proxy server or load balancer. I just
              > acces it from http://admin server ip:port/web. Is this right?
              >
              WLS ships proxy plugins for ISAPI,NSAPI, apache & HttpClusterServlet
              you may want to read our docs. http://e-docs.bea.com/wls/docs61
              Kumar
              >
              > I am new guy. try to learn cluster. if I do not describe my problem detaily,
              > will you show me a successful config example same like mine?Thanks
              >
              > "Kumar Allamraju" <[email protected]> ??????:[email protected]...
              > > when you say "all in mycluster" do you mean admin server is also part of
              > > MyCluster or
              > > only server1 & server2.
              > >
              > > If "web" is not targetted to admin server, t hen admin server should not
              > > complain about
              > > "web" upon it's startup. You may want to double check the targets of this
              > > webapp.
              > >
              > > Also how are you accessing this webapp? via proxy server or load balancer?
              > >
              > > --
              > > Kumar
              > >
              > > airwing wrote:
              > >
              > > > I try to implement cluster like this
              > > >
              > > > admin server
              > > > |
              > > > |
              > > > --------------------------
              > > > | |
              > > > | mycluster |
              > > > server1 server2
              > > > (web) (web)
              > > >
              > > > admin server start as Administrator server
              > > > server1 and server2 start as managed server. and all in mycluster. web
              > has
              > > > depoloyed to server1 and server2, but not deployed to admin server
              > > >
              > > > when I start admin server. it always say "web dot found". Why?
              > >
              

  • Cookie bug using Administrative Server as part of the Cluster

    All using Weblogic 6.0:
              Administrative Server running on Windows 2000 Professional
              Managed Server running on Windows 2000 Server
              Both machines running in the same cluster.
              Requests being proxied by the Windows 2000 Professional machine running IIS
              Ok, now that you know our test environment, here's a little about our bug.
              If we begin an http session with requests being fulfilled by the
              administrative server (through the proxy), and shut down and bring the
              managed server back up, everything is fine. (No big surprise.)
              However, if requests are being fulfilled by the managed server and the
              administrator goes down and then comes back up, we get a
              "ReplicationManager: object 722399223287670702 not found" error, where the
              number seems to refer to value stored in the cookie after the last OR
              symbol as shown below.
              When the session is created, the cookie contains the following value:
              session id =
              OnIXh5A6DxUWgBrA2qCLIDN0Co1dewmjdV1ze1isn9Wur2CHl2k2|60563422118895
              84610/-1062731365/7001/7002|4648941459387506517/-1062731381/7001/7002|722399
              223287670702
              When the administrative server goes down, the cookie contains the following
              value:
              session id =
              OnIXh5A6DxUWgBrA2qCLIDN0Co1dewmjdV1ze1isn9Wur2CHl2k2|60563422118895
              84610/-1062731365/7001/7002|NONE|722399223287670702
              When the administrative server comes back up, the cookie contains the
              following value:
              session id =
              OnIXh5A6DxUWgBrA2qCLIDN0Co1dewmjdV1ze1isn9Wur2CHl2k2|60563422118895
              84610/-1062731365/7001/7002|4563245475623454445/-1062731381/7001/7002|722399
              223287670702
              Its pretty obvious how the cookie id breaks down, information before the
              first OR is client info specific to each client, between the first and
              second OR is information regarding the first server from the cluster to
              fulfill the requests. The info between the second and third is the
              identification of the backup server containing the replicated version of the
              session. And the last bit of information seems to be an ID referring to the
              session object as stored in memory. As you can see, the value that the error
              is referring to never changes. SO WHY DOES THE OBJECT GET LOST?
              This is a big problem for us, as our resources are limited (as I assume
              everyone else's is). Is this just a bug? If so, is there a service pack
              already available? If its not a bug, it should be as resolving the bug
              allows the administrative server to be part of the cluster saving everyone
              the money for an extra machine and (here's the killer) the money for an
              extra weblogic license to run on a administrative server separate from the
              cluster (in which case it works fine, just costs a whole lot more).
              Well, I hope this is clear enough. If not please ask whatever you need to
              know. We are looking for any information anyone can provide.
              Thank you,
              Chad Griffith
              Software Engineer
              VisionTEK Inc.
              [email protected]
              

    To answer your question, fail over works fine, i.e. if a session is
              maintained on the managed server, we can shut it down and the session is
              transferred to the administrative sever.
              The only problem we are having is when the session is on the MANAGED server,
              and the ADMIN server goes down and back up WITHOUT any session transfer.
              As for shutting down an admin server, you can bring it back up while managed
              servers are running by using the -Dweblogic.management.discover=TRUE
              setting.
              I hope this clarifies everything.
              Thanks again,
              Chad
              "Sioux France" <[email protected]> wrote in message
              news:[email protected]...
              > Is this an admin server problem though? Can you try the opposite? i.e. IS
              it
              > possible to connect to the Managed server for your http requests (through
              > the proxy)? If so, then shut down and bring back the managed server. I'd
              > expect that to go wrong in the same way? Likewise if you shutdown and
              bring
              > back the admin server in that configuration you would not have a problem?
              > "Chad Griffith" <[email protected]> wrote in message
              > news:[email protected]...
              > > All using Weblogic 6.0:
              > > Administrative Server running on Windows 2000 Professional
              > > Managed Server running on Windows 2000 Server
              > > Both machines running in the same cluster.
              > > Requests being proxied by the Windows 2000 Professional machine running
              > IIS
              > >
              > > Ok, now that you know our test environment, here's a little about our
              bug.
              > > If we begin an http session with requests being fulfilled by the
              > > administrative server (through the proxy), and shut down and bring the
              > > managed server back up, everything is fine. (No big surprise.)
              > >
              > > However, if requests are being fulfilled by the managed server and the
              > > administrator goes down and then comes back up, we get a
              > > "ReplicationManager: object 722399223287670702 not found" error, where
              the
              > > number seems to refer to value stored in the cookie after the last OR
              > > symbol as shown below.
              > >
              > > When the session is created, the cookie contains the following value:
              > > session id =
              > > OnIXh5A6DxUWgBrA2qCLIDN0Co1dewmjdV1ze1isn9Wur2CHl2k2|60563422118895
              > >
              >
              84610/-1062731365/7001/7002|4648941459387506517/-1062731381/7001/7002|722399
              > > 223287670702
              > >
              > > When the administrative server goes down, the cookie contains the
              > following
              > > value:
              > > session id =
              > > OnIXh5A6DxUWgBrA2qCLIDN0Co1dewmjdV1ze1isn9Wur2CHl2k2|60563422118895
              > > 84610/-1062731365/7001/7002|NONE|722399223287670702
              > >
              > > When the administrative server comes back up, the cookie contains the
              > > following value:
              > > session id =
              > > OnIXh5A6DxUWgBrA2qCLIDN0Co1dewmjdV1ze1isn9Wur2CHl2k2|60563422118895
              > >
              >
              84610/-1062731365/7001/7002|4563245475623454445/-1062731381/7001/7002|722399
              > > 223287670702
              > >
              > > Its pretty obvious how the cookie id breaks down, information before the
              > > first OR is client info specific to each client, between the first and
              > > second OR is information regarding the first server from the cluster to
              > > fulfill the requests. The info between the second and third is the
              > > identification of the backup server containing the replicated version of
              > the
              > > session. And the last bit of information seems to be an ID referring to
              > the
              > > session object as stored in memory. As you can see, the value that the
              > error
              > > is referring to never changes. SO WHY DOES THE OBJECT GET LOST?
              > >
              > > This is a big problem for us, as our resources are limited (as I assume
              > > everyone else's is). Is this just a bug? If so, is there a service pack
              > > already available? If its not a bug, it should be as resolving the bug
              > > allows the administrative server to be part of the cluster saving
              everyone
              > > the money for an extra machine and (here's the killer) the money for an
              > > extra weblogic license to run on a administrative server separate from
              the
              > > cluster (in which case it works fine, just costs a whole lot more).
              > >
              > > Well, I hope this is clear enough. If not please ask whatever you need
              to
              > > know. We are looking for any information anyone can provide.
              > >
              > > Thank you,
              > > Chad Griffith
              > > Software Engineer
              > > VisionTEK Inc.
              > > [email protected]
              > >
              > >
              >
              >
              

  • Problem starting managed server in cluster (The name of the managed server is same as admin server)

              We have the following setup.
              CLLUSTER1 and CLUSTER2 are the servers to be in the cluster. CLUSTER3 is the cluster
              administrator. We start CLUSTER3 as a self-managed server and then try and start
              CLUSTER1 and CLUSTER3 as a managed server pointing at CLUSTER3. When we start
              1 and 2 we get the following:
              D:\bea\wlserver6.1\config\CLUSTER1>startmanagedweblogic CLUSTER3 http://10.0.1.1
              03:7001
              D:\bea\wlserver6.1>set PATH=.\bin;C:\WINNT\System32;d:\jdk1.3.1\bin
              D:\bea\wlserver6.1>set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
              D:\bea\wlserver6.1>echo off
              * To start WebLogic Server, use the password *
              * assigned to the system user. The system *
              * username and password must also be used to *
              * access the WebLogic Server console from a web *
              * browser. *
              D:\bea\wlserver6.1>"d:\bea\jdk131\bin\java" -hotspot -ms64m -mx64m -classpath
              ;.\lib\weblogic_sp.jar;.\lib\weblogic.jar" -Dweblogic.Domain=CLUSTER1 -Dbea.home
              ="d:\bea" -Dweblogic.management.password= -Dweblogic.ProductionModeEnabled=true
              -Dweblogic.Name="CLUSTER3" -Dweblogic.management.server="http://10.0.1.103:7001"
              "-Djava.security.policy==d:\bea\wlserver6.1/lib/weblogic.policy" weblogic.Serve
              r
              <20/11/2001 12:05:10> <Info> <Security> <Getting boot password from user.>
              Enter password to boot WebLogic server:
              Starting WebLogic Server ....
              Connecting to http://10.0.1.103:7001...
              The WebLogic Server did not start up properly.
              Exception raised: weblogic.management.configuration.ConfigurationException: The
              name of the managed server is same as admin server. The managed server will not
              be allowed to start up.
              weblogic.management.configuration.ConfigurationException: The name of the manage
              d server is same as admin server. The managed server will not be allowed to star
              t up.
              at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:998)
              at weblogic.management.Admin.initialize(Admin.java:320)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
              at weblogic.Server.main(Server.java:35)
              Reason: Fatal initialization exception
              D:\bea\wlserver6.1>goto finish
              D:\bea\wlserver6.1>cd config\CLUSTER1
              D:\bea\wlserver6.1\config\CLUSTER1>ENDLOCAL
              D:\bea\wlserver6.1\config\CLUSTER1>
              Many thanks in advance,
              Alex Burton
              http://www.e-plus.com.au/
              

    Don't start the admin server as managed. Removing
              -Dweblogic.management.server...
              from the command line should help.
              Alex Burton wrote:
              > We have the following setup.
              > CLLUSTER1 and CLUSTER2 are the servers to be in the cluster. CLUSTER3 is the cluster
              > administrator. We start CLUSTER3 as a self-managed server and then try and start
              > CLUSTER1 and CLUSTER3 as a managed server pointing at CLUSTER3. When we start
              > 1 and 2 we get the following:
              >
              > D:\bea\wlserver6.1\config\CLUSTER1>startmanagedweblogic CLUSTER3 http://10.0.1.1
              > 03:7001
              >
              > D:\bea\wlserver6.1>set PATH=.\bin;C:\WINNT\System32;d:\jdk1.3.1\bin
              >
              > D:\bea\wlserver6.1>set CLASSPATH=.;.\lib\weblogic_sp.jar;.\lib\weblogic.jar
              >
              > D:\bea\wlserver6.1>echo off
              >
              > ***************************************************
              > * To start WebLogic Server, use the password *
              > * assigned to the system user. The system *
              > * username and password must also be used to *
              > * access the WebLogic Server console from a web *
              > * browser. *
              > ***************************************************
              >
              > D:\bea\wlserver6.1>"d:\bea\jdk131\bin\java" -hotspot -ms64m -mx64m -classpath
              > ".
              > ;.\lib\weblogic_sp.jar;.\lib\weblogic.jar" -Dweblogic.Domain=CLUSTER1 -Dbea.home
              > ="d:\bea" -Dweblogic.management.password= -Dweblogic.ProductionModeEnabled=true
              > -Dweblogic.Name="CLUSTER3" -Dweblogic.management.server="http://10.0.1.103:7001"
              > "-Djava.security.policy==d:\bea\wlserver6.1/lib/weblogic.policy" weblogic.Serve
              > r
              > <20/11/2001 12:05:10> <Info> <Security> <Getting boot password from user.>
              > Enter password to boot WebLogic server:
              > Starting WebLogic Server ....
              > Connecting to http://10.0.1.103:7001...
              > ***************************************************************************
              > The WebLogic Server did not start up properly.
              > Exception raised: weblogic.management.configuration.ConfigurationException: The
              > name of the managed server is same as admin server. The managed server will not
              > be allowed to start up.
              > weblogic.management.configuration.ConfigurationException: The name of the manage
              > d server is same as admin server. The managed server will not be allowed to star
              > t up.
              > at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:998)
              > at weblogic.management.Admin.initialize(Admin.java:320)
              > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
              > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
              > at weblogic.Server.main(Server.java:35)
              > Reason: Fatal initialization exception
              > ***************************************************************************
              >
              > D:\bea\wlserver6.1>goto finish
              >
              > D:\bea\wlserver6.1>cd config\CLUSTER1
              >
              > D:\bea\wlserver6.1\config\CLUSTER1>ENDLOCAL
              >
              > D:\bea\wlserver6.1\config\CLUSTER1>
              >
              > Many thanks in advance,
              > Alex Burton
              > http://www.e-plus.com.au/
              

  • Starting weblogic cluster and admin server on Win 2000 platform

    Hi! Here's my problem scenario:
    I'm running my WLS 8.1 application as WLS cluster on Win 2000 platform. I have
    3 replicated WLS servers in my cluster and of course one WLS server as admin server
    (4 WLS servers all together). I'm starting my WLS application using Win services
    which behind a scene call win 2000 comand interpreter batch-file to start the
    servers. Currently I have 4 different win 2000 services each calling different
    batch-files to start a WLS server (4 all together). Here's my question:
    Is there any way to start my cluster (3 managed WLS servers) and WLS admin server
    from single win 2000 command file (using single win 2000 service). Using win 2000
    AT-command interpreter command I can start executables and command(s) and command-files
    at background at specific date and time, but I want to start my WLS application
    on every win 2000 platform boot, is there any way to achieve this ???
    Best Regards!
    Jami

    hi,
    Thanks for stepping up!
    But I wasn't using any clustering or loadbalancing.
    Just a simple Admin server, Managed server set up.
    256 Meg, Pentium box running Win 2000 premium edition.
    I tried tweeking around the heap size too.... coz' the operations were slogging
    like anything...
    Bal
    "Raja Mukherjee" <[email protected]> wrote:
    It seems like network issue....do you have Windows Clustering/Load Balancing
    service turned on by any chance? I would also use netmon to see the traffic
    between the ips....
    ..raja
    "Bala" <[email protected]> wrote in message
    news:3b3a6c00$[email protected]..
    hi,
    I am looking at a strange behaviour with WLS6.0SP1 installed on WINDOWS2000 Premium.
    I brought up the Admin server and a Managed server. After a while theAdmin Server
    is compeletely
    losing the control of the managed server (for no reason).
    when I tried monitoring the managed server from the console, I couldnot
    access
    the manager server
    and the status down (red ball). I tried restarting the Admin Server
    in the discover mode - NO LUCK.
    But when I restart the Managed server and go to the Web Based Admin
    Console and refresh, it worked. But I dont think we should be doingthat
    in a
    production environment.
    Did anybody come across such a problem before ???
    Is this a problem with Win 2000 ???
    coz' it never happened with NT workstation
    thanks in advance

  • Weblogic admin server cluster

    Hi,
    I'm setting up WebLogic cluster (horizontal with 2 managed servers spanning across 2 machines).I would want to have admin server on each machine and only one admin server will be active whiel the second admin server will remain shutdown
    .Can anyone please explain how I can set this up with 2 adminsitration servers and how do I make it active-passive mode for admin server and how i can bring it up in case of 1st admin server going down
    Any documents would be really helpful
    thanks

    There can be only 1 Admin per WebLogic Domain....not more than one.
    Please refer to Know more about *"What is Administration Server?"* http://weblogic-wonders.com/weblogic/2010/06/18/weblogic-initials/
    If you are talking about *" Whole Server Migration "* then please refer to: http://download.oracle.com/docs/cd/E11035_01/wls100/cluster/migration.html
    Note:      Server migration is only supported when you use the SSH version of Node Manager. Server migration is not supported on Windows.
    When a migratable server becomes unavailable for any reason, for example, if it hangs, loses network connectivity, or its host machine fails—migration is automatic. Upon failure, a migratable server is automatically restarted on the same machine if possible. If the migratable server cannot be restarted on the machine where it failed, it is migrated to another machine. In addition, an administrator can manually initiate migration of a server instance.
    Thanks
    Jay SenSharma
    http://weblogic-wonders.com/weblogic (WebLogic Wonders Are here)

  • Weblogic admin server in the cluster !!!!

    Hi,
    I am working on weblogic setup already done by my ex-colleague. I observed that, the admin server is also participating in the cluster and hence it is also one of the targets for EJB components, datasource and connection pool. Is there any performance issue in this setup ?
    thanks for your time.

    Thank you for your reply.
    I forgot to tell you that the admin server is not an individual machine. It is setup in one of the weblogic App. servers. Therefore, I feel it is better we do not add this admin server in the cluster.
    You can give me your advice. ---- topic 1
    By the way, I had posted one question about targeting a datasource to the individual servers rather than to a cluster. In the existing setup, the datasource is targeted to individual servers rather
    than to the cluster. The setup is running without any error.
    But as per the BEA manual, we have to target the datasource to the cluster if we use cluster. So, in my current setup, is there any performance issue or may I face any problem in future by not targeting the datasource to the cluster? I appreciate if you can
    try this question. ---- topic 2
    Thanks in advance.

  • Admin Server Funcationality in a WebLogic Cluster

    Is this a correct statement of how the Admin Server is handled in WebLogic Cluster:
    "If you have a two node WebLogic 10.3 Cluster then you will have the Admin Server for the domain running on node1. The managed server within the domain will run on both node1 and node2. The managed server services your application(s).
    If node1 fails then the managed server running on node2 will continue to operate, thus meeting your high availability requirement.
    If you need to administer your WebLogic installation you will first have to restore node1 to an operational state so that you can access the Admin Server."
    Thank you

    Answers :-
    Q>"If you have a two node WebLogic 10.3 Cluster then you will have the Admin Server for the domain running on node1. The managed server within the domain will run on both node1 and node2. The managed server services your application(s).
    A>Admin server can be running on any node(Physical machine). One Managed server(say MS1) can run only on one node. Two nodes can host two different managed servers. Yes, managed servers services your applications.
    Q>If node1 fails then the managed server running on node2 will continue to operate, thus meeting your high availability requirement.
    A> Yes, that is the reason of using clustering : Load balancing and failover.
    Q>If you need to administer your WebLogic installation you will first have to restore node1 to an operational state so that you can access the Admin Server."
    Yes, if admin server was running on node1, then it needs to be up and running to administer the domain.

  • Cannot expand IDM cluster due to unable to connect to Admin Server

    Hi everyone.
    When I was configuring HA on IDM node2 for ODS managed server and ASinstance, I met the strange situation:
    - I choose expand cluster on IDM configuration wizard windows (oim_11.1.1.7.0)
    - I entered the admin server address, port, username, password, all of them is correct because I tested them on all nodes and from my remote laptop
    - when I hit the Next button, that error occured:
    INST-07242 Unable to connect to Oracle Weblogic Middleware Administration Server
    Make sure Oracle Administration Server is up and hostname, port, user name and administration password are correct.
    I don't know what the reason of that error. On the Metalink I watch the doc ID:1324425.1 but the solutions mentioned to earlier verions than mine. So that I cannot apply that solutions.
    Have you got any idea ?
    Thank in advance.
    Cuong Pham

    Hi,
    Post again to the Identity forum at Identity Manager

  • 6.0 cluster startup without the admin server...

    Is it possible to start a WL6.0 cluster without the admin server being up
              and running? If not, are there any workarounds that eliminate the admin
              server as a single point of failure?
              

              I have same questions.
              1.The admin server's primary task is up the cluster?And if admin server is down
              that can't affect the cluster running.
              2.Is it right when the cluster is working,the useful ip is admin server's ip?For
              example,admin 10.10.10.1,cluster1 10.10.10.2,cluster2 10.10.10.3,the only useful
              ip is 10.10.10.1 in the cluster.
              3.Is it correct that because the only useful ip is 10.10.10.1,therefor my client
              access the cluster from 10.10.10.1?
              When my admin server is down,then my system will be down.
              4.which is the dispatch in the cluster system ?
              my step of configuration of th cluster:
              1.add two managed servers to admin server and edit startweblogic.cmd;
              2.config cluster.(admin server address 10.10.10.1:8168,cluster address 10.10.10.2:7001,10.10.10.3:7001),multicast(237.0.0.1)
              please help explain these questions!thanks a lot!
              2.
              Kumar Allamraju <[email protected]> wrote:
              >Sorry if i wasn't clear, what i mean to say is
              >
              >When you first start the managed server's you have to have admin server
              >up &
              >running.
              >Admin server can go down when cluster is running, but then you can't
              >add servers
              >to cluster
              >and I think its ok to have it that way from administration point of view.
              >
              >Yes, there's no facility to achieve single point of failure for admin
              >servers.
              >
              >--
              >Kumar
              >
              >
              >
              >William Wallace wrote:
              >
              >> I may be misreading that page, but it doesn't really tell me how to
              >> successfully start to start a managed server is the admin server is
              >down. If
              >> you run the managed server script you get an "cannot connect to admin
              >> server" exception if the admin server is not running. Now, I imagine
              >that I
              >> could script something up to restart the admin server if it's down,
              >but that
              >> doesn't protect me from hardware failure.
              >>
              >> "Kumar Allamraju" <[email protected]> wrote in message
              >> news:[email protected]...
              >> > http://e-docs.bea.com/wls/docs60/adminguide/startstop.html#1035064
              >> >
              >> > --
              >> > Kumar
              >> >
              >> >
              >> > William Wallace wrote:
              >> >
              >> > > Is it possible to start a WL6.0 cluster without the admin server
              >being
              >> up
              >> > > and running? If not, are there any workarounds that eliminate the
              >admin
              >> > > server as a single point of failure?
              >> >
              >
              

  • Cluster member caches a copy of DefaultWebApp from admin server

    Hi,
              It seems that when a cluster member starts up, it fetches a copy of
              DefaultWebApp web application from admin server, and keeps it under a
              directory of $BEA_HOME/wlserver6.1/config/mydomain/applications/.wlnotdelete_$SERVER_NAME,
              and it doesn't look into its local copy of DefaultWebApp even being
              modified.
              How does this happen? How can it be disabled?
              Thanks in advance,
              William
              

    Hi,
              this does probably occur due a change in WLS 6.1 which was done in order to assure the server
              to function properly even when the customer deletes the defaultWebApp. If this is the case
              this
              cannot switched off.
              Do you observe other symptoms, which lets you think you have a problem with your server ?
              Regards,
              Christian Buchegger
              Developer Relations Engineer
              BEA Support
              William Li schrieb:
              > Hi,
              >
              > It seems that when a cluster member starts up, it fetches a copy of
              > DefaultWebApp web application from admin server, and keeps it under a
              > directory of $BEA_HOME/wlserver6.1/config/mydomain/applications/.wlnotdelete_$SERVER_NAME,
              > and it doesn't look into its local copy of DefaultWebApp even being
              > modified.
              >
              > How does this happen? How can it be disabled?
              >
              > Thanks in advance,
              >
              > William
              

  • Newbie cluster question: where does the admin server live?

    Hello, I'm looking at clustering for our application where I work, and so I'm reading through the cluster-related documentation for 11g. I have a sort of an architecture question: where should the admin server be started? Hypothetically speaking, if you have two nodes for your cluster, would the AdminServer run on a 3rd box which sort of stood in front of the two nodes?
    Thanks much -

    The ideal situation would be for your admin server to be separate from the machines hosting your managed server. This allows you to control access to the admin server, eliminate the performance impact if you have the admin + managed on the same host, and limits impact if youir #1 host fails, etc.
    But companies may be unwilling to invest in a distinct (3rd) host just for the admin server, especially if you have multiple environments ( prod, testing, dev, etc. ).
    So usually the admin winds up sharing the host with a managed server.

  • Strange WLS6.sp2 Oracle DB Reconnect issue in a Cluster but ONLY on the Admin server

    Any Ideas? ->
    I am having a issue when our oracle db server goes down and when we try
    to reconnect the Pool via weblogic I am getting this error. This only
    happens on the Admin server for the cluster, none of the managed servers get
    this and they all seem to be ok. Any ideas?
    -Pete
    **** Below is the stack trace:
    java.sql.SQLException: Io exception: Broken pipe
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:114)
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:156)
    at oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:269)
    at
    oracle.jdbc.driver.OracleStatement.executeNonQuery(OracleStatement.java:1329
    at
    oracle.jdbc.driver.OracleStatement.doExecuteOther(OracleStatement.java:1232)
    at
    oracle.jdbc.driver.OracleStatement.doExecuteWithBatch(OracleStatement.java:1
    353)
    at
    oracle.jdbc.driver.OracleStatement.doExecute(OracleStatement.java:1760)
    at
    oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java
    :1805)
    at
    oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedState
    ment.java:322)
    at
    oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.j
    ava:366)
    at
    weblogic.jdbc.pool.PreparedStatement.execute(PreparedStatement.java:45)
    at
    weblogic.jdbc.rmi.internal.PreparedStatementImpl.execute(PreparedStatementIm
    pl.java:289)
    at
    weblogic.jdbc.rmi.SerialPreparedStatement.execute(SerialPreparedStatement.ja
    va:398)

    Hi,
    As i understand is OS is clustered not the db. Better is to manually shutdown the db clean and then start it.
    TO start login through sqlplus sys as sysdba
    1. startup
    2. Once its done, start the listener
    3. Start the application
    Anand

Maybe you are looking for

  • Mc.9 as background job

    Hi Experts, I have to schedule the MC.9 report for Material Stock Analysis in the background. The MC.9 transaction if run in the foreground is running successfully for short period of 1 month. But if i try to run the transaction for more than 3 month

  • Moving Datafiles from one drive to another

    What is the procedure to move datafiles from one drive to another ? Thanks

  • Creating GUI + EventQueue.invokeAndWait problem

    Hi, Currently I am creating GUI to my application ,thanks to NetBeans Graphic Editor ,I created simple grame with one buton.Now i am trying to add action to this button listener.Generally i want to make that if this button is pressed,new frame with g

  • Document not reported for approval

    I have an urgent issue related to workflow, it is like a lot of document that should report for approval, has not been reported since many days. Now when i am checking the log of the documents it is showing a SWW_WI_ERROR_MESSAGE_SEND_S in technical

  • Slideshow for Plasma Display

    I'm throwing some pictures together to be shown on a plasma display and was wondering what the best crop and display settings would be to look best on it. The display is a 480p 16X9 Panasonic. The technical page shows that its resolution is 852X480.