Home > Default > Shutdown(block='false') only works via Admin Server, not managed servers

Shutdown(block='false') only works via Admin Server, not managed servers

November 30Hits:0
Advertisement
Hello,
We want to shut down all 10 managed servers in our domain gracefully, and in parallel. 5 of those managed servers are on the same OS/host as the AdminServer, the other 5 are on a separate OS/host (i.e. we have 5 x 2-node clusters).
I'm writing scripts to gracefully shut down all of our servers upon an OS reboot command. On the OS with the AdminServer (and 5 managed servers), I can simply do this:
connect(user, pwd, http://localhost:7001)
shutdown('myserver1', 'Server', block='false')
shutdown('myserver3', 'Server', block='false')
shutdown('myserver5', 'Server', block='false')
shutdown('myserver7', 'Server', block='false')
shutdown('myserver9', 'Server', block='false')
All 5 servers will be shutting down at the same time. If they each took 2 minutes to shut down, the whole shutdown process would take 2 minutes.
However, on the OS running the other managed servers, I cannot assume that the AdminServer [on the other OS] will be online. Hence, I would like to gracefully shut down each server locally like this:
connect(user, pwd, url='t3://localhost:8001')
shutdown(block='false')
disconnect()
connect(user, pwd, url='t3://localhost:9001')
shutdown(block='false')
disconnect()
connect(user, pwd, url='t3://localhost:10001')
shutdown(block='false')
disconnect()
connect(user, pwd, url='t3://localhost:11001')
shutdown(block='false')
disconnect()
connect(user, pwd, url='t3://localhost:12001')
shutdown(block='false')
disconnect()
NOTE that the ports are different (i.e. I connect via WLST to the managed servers themselves rather than to the AdminServer).
Unfortunately, in this scenario, the block='false' does not work. WLST waits until the managed server is shut down before proceeding to the next connect() command. So if each server took 2 minutes to shut down, the whole shutdown process now takes 10 minutes.
We don't want to use the nmKill() command on the local Node Manager because we want a graceful shutdown.
What options do we have to issue a graceful shutdown command either to a local Node Manager or to the managed servers themselves (since we can't expect the AdminServer to be online when our script runs)?
Best regards,
Michael

Answers

Hi Mike,
WLST will create it temp directory with /var/tmp/wlstTemp which is shared by all users. Since we cannot differentiated by different users which cause block on particular user at that time.
One solution is to grant write access to all users to the directory where the WLST temporary directory is created (e.g. on Solaris /var/tmp; you can verify the default on your system by executing java utils.getProperty and search for java.io.tmpdir).
If for whatever reason you cannot grant these access modes on the temporary directory, then you can create a directory somewhere on the file system where every user has the correct permissions.
Start the scripting tool with one the following options to redirect the cache files to the specified directory. Dependent on your environment one or the other will apply.
java -Djava.io.tmpdir=<path-to-tmpDir> weblogic.WLST
or
java -Dpython.cachedir=<path-to-tmpDir> weblogic.WLST
This will be useful to make shutdown of servers without any problem.
Note: block=false will always works it should not be the problem.
Regards,
Kal

Read other 7 answers

Tags:

Related Articles

  • Shutdown(block='false') only works via Admin Server, not managed serversNovember 30

    Hello, We want to shut down all 10 managed servers in our domain gracefully, and in parallel. 5 of those managed servers are on the same OS/host as the AdminServer, the other 5 are on a separate OS/host (i.e. we have 5 x 2-node clusters). I'm writing

  • Creating Weblogic domain with Admin Server and managed servers on differentNovember 30

    I am trying to create Weblogic domain where Admin Server and managed servers on different machines. However I am unable to find any steps which would allow me to do so. The config.sh script always creates an Admin Server. Please help.Whilst the metho

  • Admin server looses managed serversNovember 30

    we hava 2 clusters of 2 wls 6.1 sp2 instances each on 2 hpux 11 boxes. The wls console shows all the instances when booted up. But suddenly, after a period( and this random without a pattern), the admin seems to loose some of the managed servers. The

  • Admin Server and Managed server startup problemNovember 30

    Hi, My weblogic server version is 11g and OS is Linux. When i am trying to start the admin server a frer i created the domain i am getting following exceptions in the server log and server is shutting down. FPR6 4008000000000000 (f: 0.000000, d: 3.00

  • Different service packs in admin server and managed serverNovember 30

    Hi, Has anybody successfully used a WebLogic 6.1 SP1 managed server that connects to a WebLogic 6.1 SP 2 admin server? BEA's docs claim: "The Administration Server must be running the same version of WebLogic Server as the Managed Servers in its doma

  • Problem creating a domain w/ one Admin Server and Managed ServerNovember 30

    I went through the config wizard (Weblogic 10.2) and set up a domain w/ 1 Admin Server and Managed Server. When I start the Admin server I get the following error: ####<Jul 30, 2008 6:05:28 PM PDT> <Error> <Store> <BLUDAF222452> &l

  • Communication protocol between Admin Server and Managed ServerNovember 30

    Hello - I am hoping someone can help me here to understand the communication protocols used in my setup. Here is my understanding of the protocol that are used between each component. End User <--->HTTPS<--->LoadBalancer Device<--->HTTPS

  • How to access JNDI tree of Admin Server from Managed ServerNovember 30

    Hello, I created Managed and Admin Server for Domain. On Managed Server I use: InitialContext con = new InitialContext() It points to Managed Server local JNDI tree and Managed Server can't find JNDI tree of Admin Server. Looks like Managed Server is

  • Use Admin Server to Manage multiple managed servers through NodemanagerNovember 30

    hi guys, Iam trying to simulate the production environment for a Weblogic based application. I want to use one Admin Server(adminServer) to control 2 managed servers(weblogic,Bizarro). adminServer & weblogic sit on windows machine (prod1) and Bizarro

  • Keep weblogic admin server and managed server running after exiting PUTTYNovember 30

    How do i keep my managed servers and admin servers running on SOLARIS (unix) boxes even after exiting putty and starting them? Do i need to create like a cron job or something?*(after running nohup ./startWebLogic.sh i get Sending output to nohup.out

Copyright (C) 2019 wisumpire.com, All Rights Reserved. webmaster#wisumpire.com 14 q. 0.616 s.