Gracefully shuts down managed server methods with WebLogic script

WebLogic middleware needs to be built recently. There are some problems with columns, such as how to shut down the WebLogic service gracefully between shutting down the server. An abnormal shutdown of the WebLogic service caused the trouble, I think it should be for the first WebLogic friends to write something. Although there are a variety of weblogic information on the Internet, there is less information involved in closing WebLogic services. Language organization ability is poor, please light spray!

The usual way to close WebLogic is to use WebLogic's own stopmanagedweblogic.sh script, which is not detailed here. But often encounter management failure, prompt as follows:

[email protected] bin]# sh stopmanagedweblogic.sh twls08 http://10.60.7.2:7001

Stopping Weblogic Server ...

Initializing WebLogic Scripting Tool (WLST) ...

Welcome to WebLogic Server administration Scripting Shell

Type Help () available commands

Connecting to http://10.60.7.2:7001 with UserID WebLogic ...

This Exception occurred at Sat OCT to 20:15:20 CST 2015.

Javax.naming.CommunicationException [Root exception is java.net.connectexception:http://10.60.7.2:7001:destination unreachable; Nested exception is:

java.net.ProtocolException:Tunneling result Unspecified -is the HTTP server at host: ' 10.60.7.2 ' and port: ' 700 1 ' a WebLogic Server?; No available router to destination]

Problem invoking Wlst-traceback (innermost last):

File "/oracle/middleware/weblogic/user_projects/domains/lb_domain/shutdown.py", line 3, in?

File "<iostream>", line A, in Connect

File "<iostream>", line 648, in Raisewlstexception

Wlstexception:error occured while performing connect:error getting the initial context. There is no server running at http://10.60.7.2:7001

Use DumpStack () to view the full StackTrace

Done

Stopping Derby Server ...

[[Email protected] bin]# PS aux|grep start

The failure of the normal shutdown WebLogic service is as follows, the data source is not working properly, and the workaround is to delete the original data source and create a new data source. The author believes that the cause of this failure is abnormal shutdown caused the data source related configuration and state information changes, resulting in the inability to use the data source.

650) this.width=650; "style=" Float:none; "title=" 1.png "src=" http://s3.51cto.com/wyfs02/M02/75/4C/ Wkiom1y0xxvyom9aaafze4mgqf0736.jpg "alt=" Wkiom1y0xxvyom9aaafze4mgqf0736.jpg "/>

Workaround:

Method 1. Enable Tunneling Protocol shutdown

If the wrong red part is reported, no tunnel is specified. Once enabled, the weblogic server needs to be restarted before it can be used.

Start the tunnel mode as

650) this.width=650; "style=" Float:none; "title=" 2.png "src=" http://s3.51cto.com/wyfs02/M02/75/4A/ Wkiol1y0x1wjb3-waal4d_iykri327.jpg "alt=" Wkiol1y0x1wjb3-waal4d_iykri327.jpg "/>

Method 2. Use WebLogic T3 Protocol shutdown Service

How to use 1 close weblogic t3 protocol closed. What is t3 protocol, T3 also known as rich sockets, is bea

T3 is a multi-work bidirectional and asynchronous protocol that is highly optimized to use only one socket and one thread. With this approach, Java -based clients can use multiple RMI objects based on server-side requirements , but still use a socket and a thread.

Default Usage http protocol shutdown: sh stopmanagedweblogic.sh twls08 http://10.60.7.2:7001

Use T3 protocol Shutdown Method: sh stopmanagedweblogic.sh twls08 t3://10.60.7.2:7001

is so simple, if the vast number of netizens have a better way, please leave a message, thank you!

This article is from the "Mr. Koala" blog, please make sure to keep this source http://koala003.blog.51cto.com/9996246/1708425

Gracefully shuts down managed server methods with WebLogic script