Stopping an Instance - Complex Event Processing

I'm using CEP 11.1 on Linux and get the following error when I use the stopwlevs.sh script to shutdown a running server.
[oracle#victor-one defaultserver]$ ./stopwlevs.sh
wlevs.Admin is is a command-line utility for managing WebLogic Event Server. Try:
wlevs.Admin help ENCRYPT Working with WebLogic Event Server Encryption
wlevs.Admin help RULES Working with WebLogic Event Server Rules
wlevs.Admin help RECPLAY Working with WebLogic Event Server Record Playback
wlevs.Admin help MONITOR Working with WebLogic Event Server Monitoring
wlevs.Admin help MBEAN Working with WebLogic Event Server MBeans
wlevs.Admin help ALL Help for all commands
Usage: java wlevs.Admin
[-url |-protocol <protocol-name> -listenAddress <host-name> -listenPort <port>]
-username <username> -password <password>
<COMMAND> <ARGUMENTS>
More info available at: http://download.oracle.com/docs/cd/E13157_01/wlevs/docs30/config_server/admin_tool.html
[oracle#victor-one defaultserver]$ more stopwlevs.sh
#!/bin/sh
. ./setDomainEnv.sh $*
USER_CONFIG_FILE=config/security-config.xml
KEY_FILE=.msainternal.dat
"$JAVA_HOME/bin/java" -jar "${USER_INSTALL_DIR}/bin/wlevsadmin.jar" -userconfigfile $USER_C
ONFIG_FILE -userkeyfile $KEY_FILE -listenPort $* SHUTDOWN
I guess I'll just have to use ctrl-C for now, but it would be nice if there was a clean way to shutdown an active server. 

Hi,
What version of Linux are you using?
Seth 

I'm running Centos 5.3, which is the same as RHEL 5.3. 

The command expects a url for the server you are shutting down.
IIRC something like
stopwlevs.sh http://localhost:9002
but you should check the docs.

Related

weblogic.Deployer troubles (bea92)

in short, doesnt work
java -cp .;weblogic.jar weblogic.Deployer -adminurl t3://10.131.20.41:7001 -user weblogic -password weblogic -deploy c:\app.ear
weblogic.Deployer invoked with options: -adminurl t3://10.131.20.41:7001 -user weblogic -deploy c:\app.ear
Unable to connect to 't3://10.131.20.41:7001': invalid type code: 31. Ensure the url represents a running admin server and that the credenti
als are correct. If using http protocol, tunneling must be enabled on the admin server.
I have enabled the tunneling, i have also tried http so on ans so forth .. the admin console is indeed on 7001, so i dont know wtf its talking about.
If I do it manually via adminconsole it works, well it dont, but thats a configuration issue with spring (missing placeholder for some injection), but the app gets installed
oh yea, the IP is localhost, tried "localhost" too with same result .. any ideas more than welcome, this is tiresome :( 
One thing to check. Make sure you are not using JDK 1.6.x when using the commandline. There is a pretty obscure bug with this setup.
http://forum.java.sun.com/thread.jspa?threadID=5195504&tstart=60
You might have got hit by it.

stopWeblogic.sh w/ boot.properties

According to these docs:
http://e-docs.bea.com/wls/docs81/admin_ref/cli8.html#1131733
<i>$ ./stopWeblogic.sh (Solaris 8)
</i>
should pick up the boot.properties and shutdown the server. It just errors out asking for the user id.
<i>$ ./stopWebLogic.sh
ERROR: Because your domain was created as a production mode domain.
You MUST include a username parameter that can be used to shutdown Weblogic Server</i>
I've also tried adding:
-Dweblogic.system.BootIdentityFile=filename
-Dweblogic.RootDirectory=path
To the java command (w/ fully qualified pathnames), but still no joy. Any ideas?
--Kurt                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    
This is what I changed the command line in "stopWebLogic.sh".
You will note the shell script does not pass any command line arguments into this invocation of Java. Which is why the script needed editing.
${JAVA_HOME}/bin/java -Dweblogic.system.BootIdentityFile=boot.properties -Dweblogic.RootDirectory=${DOMAIN_HOME} -cp ${C
LASSPATH} weblogic.Admin FORCESHUTDOWN -url ${ADMIN_URL} ${UIDPWD} ${SERVER_NAME} 2>&1
Given that you can start up a server without a username/password (because it uses boot.properties) I can not understand why you need these details to shut it down.
All the WebLogic scripts need a complete overhaul and should be deleted and replaced with a simple one line
java -jar <Command>
and all the information currently in the scripts placed into the classpath and loaded and managed automatically by the Java classes.
The problems stem from too many ways for things to get done and no consistency.

Weblogic Shutdown problem

Hi;
I have a problem with x64 XP. I tried both Workshop and Eclips(with oepe). I could start my server but when i try to stop eclipse or workshop
could not understant server was stopped. I could see message on Console:
"C:/bea/jrockit_160_05/bin/java -classpath C:/bea/wlserver_10.3/server/lib/weblogic.jar weblogic.Admin -url t3://localhost:80 -username admin -password admin FORCESHUTDOWN AdminServer
Server "AdminServer" was force shutdown successfully ..."
so, server was stopped but eclipse did not understand this and progressbar shows :"Shutting down server (%95)" and after 1-2 minutes
it reaches timeout and cant stop server message. After this server start button becaming disabled. For starting serv i have to close and restart the eclipse.
I tried this on x32 XP but there was not any problem occured.
Any suggestion?
thanks. 
Hello,
This is Andrew. I work on the OEPE product as a QA engineer.
I know that 64 bit support has been a little more variable compared to 32 bit.
Let me try to get an answer for you in the next day.
Regards. 
Hello,
You did mention you tried a windows x32 OEPE install where you haven't experienced the shutdown issue. Are you able to continue working on x32 XP?
-Andrew 
Hello,
it's possible that the server was shutdown but the debugger process was still running. can you verify that there are no orphaned java process still running when the IDE is started the first time.
you could also try the following
create a server instance within OEPE.
open a cmd prompt and start the server
verify that the server status is updated in OEPE
open a cmd prompt and stop the server
verify that the server status is updated in OEPE
thanks
Raj 
I can't stop too.
I found when open a cmd prompt and stop the server, the server status is not updated in OEPE.
I use xp32 and weblogic10.3 
I cant understand but on eclipse ganymede problem was lost, but i am getting same problem in galileo...
I dont sure problem is about x32 or x64...
Raj, I also tried your sugestions and at the last step eclipse cant understand weblogic was stopped...
It is so boring. I see "Oracle WebLogic Server 11gR1 at localhost [Stopping,Synchronized]" in server tabs but in console
"C:/bea2/jrockit_160_05_R27.6.2-20/bin/java -classpath C:/bea2/wlserver_10.3/server/lib/weblogic.jar weblogic.Admin -url t3://localhost:7001 -username admin -password xxx FORCESHUTDOWN AdminServer
Server "AdminServer" was force shutdown successfully ..."
message says it was stopped already... and "Stopping" state does not change...
Edited by: bluex on 26.Eyl.2009 16:29

Start, shutdown and restart the Weblogic server.

Hi all,
What is the best way to start, shutdown and restart the Weblogic server?
I use this for start:
./startWebLogic.sh
Shutdown:
Don't know
Restart:
Don't know
I use Weblogic Server 11g on linux.
Thanks in advance. 
easiest way is to use the admin console to stop the managed servers and admin server and to start the managed server. For starting the admin server u can use startWebLogic.sh.
Alternatively u can use weblogic.Admin utility/ WLST to start/stop servers.
Please refer the following URLs.
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/config_scripting/index.html
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/admin_ref/index.html
Regards,
Dinesh 
for shutdown you can use
1) built-in script: ./stopWeblogic.sh <weblogic uid> <password> that script is located under bin dir under your Domain dir
2) WLST script or weblogic.Admin toll
OR
3) so you can simply kill the processes using kill -9 <PID> 
quote mrite
Diego 
Using the console is the easiest but it deplends on what you ar used to. Some people like scripts better. I prefer to use the node manager to start my managed servers. 
To runt at background:
nohup ./startWebLogic.sh &
(ofcourse, under domain\bin folder, edit startWebLogic.sh and put the username and password WLS_USER="" & WLS_PW="")
(or goto console http://<your server>:<port>/console, select the server and click Start)
Shutdown:
./stopWebLogic.sh (or goto console http://<your server>:<port>/console, select the server and click Force Shutdown Now)
Restart:
nohup ./startWebLogic.sh &

Check if defined Weblogic applications are running

Hello,
we have a Weblogic 10.3 server, and four application deployed in it (let's call them app1, app2, app3 and app4).
I need to write a script, that will periodically check (let's say every 10 minutes), if Weblogic is running and if all of the applications are running (in "Active" state).
So far, I can check the server overall state and if it responds to pings
java weblogic.Admin -url t3://HOST:7001 -username weblogic -password weblogic1 GETSTATE
# process response here
java weblogic.Admin -url t3:/HOST:7001 -username weblogic -password weblogic1 PING
# process response hereNow, I need to find out, if the applications are in "Active" state, which I don't know how. Any suggestions? Can't find much on this topic in weblogic.Admin manual. 
Hi,
You can achieve the functionality using the WLST scripting or using a JMX program.
Refer the below link for Weblogic Server State Monitoring WLST Script
http://weblogic-wonders.com/weblogic/2011/03/16/weblogic-server-state-using-wlst/
Refer the below link for Application State Monitoring WLST Script
http://weblogic-wonders.com/weblogic/2011/03/23/application-state-monitoring-using-wlst/
Hope this is helpful.
Cheers,
Anandraj
http://weblogic-wonders.com/
Edited by: Anandraj on Mar 25, 2011 5:19 PM

Categories

Resources