WLST connecting to WebLogic Admin Server failed:bootstrap to [Ip:port] failed. It is likely, the remote side declared peer gone on this JVM

Reprinted from: http://onlineappsdba.com/index.php/2014/02/18/ Wlst-connecting-to-weblogic-admin-server-failed-bootstrap-to-ipport-failed-it-is-likely-that-the-remote-side-declared-pee r-gone-on-this-jvm/

WebLogic Scripting Tool (WLST) is a command-line Scripting environment so can use to create, manage, and Mo Nitor WebLogic Server domains.

I recently encountered issue while connecting to WebLogic Server from WLST command connect (' user ', ' password ', ' Adminser Ver ')) remotely.

Issue: WLST connect from local machine (where WebLogic Server was running) is working fine where as Conne Ction from remote machine (WLST to remote machine) reported error. DumpStack () reported error Bootstrap to [Ip/[ip]:[admin Port] failed. It is likely, the remote side declared peer gone on this JVM

Command executed and error message is

____________

Wlst (or wlst.sh from Linux machine)

Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server administration Scripting Shell

Type Help () available commands
Wls:/offline>
wls:/offline> Connect (' WebLogic ', ' welcome1′, ' t3://192.168.1.12:7001′ ')
Connecting to t3://192.168.1.12:7001 with UserID WebLogic ...

Traceback (innermost last):
File "<console>", line 1, 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 t3://192.168.1.12:7001
Use DumpStack () to view the full StackTrace

Wls:/offline> dumpstack ()

This Exception occurred at Mon Feb 23:50:54 GMT 2014.
Javax.naming.CommunicationException [Root exception is Java.net.connectexception:t3://192.168.1.12:7001:bootstrap To 192.168.1.12/192.168.1.12:7001 failed. It is likely, the remote side declared peer gone on this JVM] javax.naming.CommunicationException [Root exception Is java.net.connectexception:t3://192.168.1.12:7001:bootstrap to 192.168.1.12/192.168.1.12:7001 failed. It is likely, the remote side declared peer gone on this JVM] wls:/offline>

_________________

Checks Done  

1. Ensure that remote machine can access WebLogic Server (there are no firewall): This worked for me and I am AB Le to access WebLogic Console using IP and actual Hostname Http://192.168.1.12:7001/console

Issue: In my case machine running WebLogic Server had the host names

a) Actual hostname–weblogichost.mydomain.com and
b) virtual hostname–innowave21 (WebLogic Admin Server was configured-run on Virtual Name)

Fix: Ensure (from where WLST was being run), can resolve hostname mentioned in Li Sten Address of Admin Server (innowave21 in my case)

If not then the add entry like below on the hosts file of machine from where is running WLST to connect to WebLogic Server

192.168.1.12 INNOWAVE21

Note: After adding entry in the Hosts file (or DNS server) for INNOWAVE21, I am able to connect using WLST.

WLST connecting to WebLogic Admin Server failed:bootstrap to [Ip:port] failed. It is likely, the remote side declared peer gone on this JVM