WLST connecting to WebLogic Admin Server failed : Bootstrap to [IP:Port] failed. It is likely that the remote side declared peer gone on this JVM

WebLogic Scripting Tool (WLST) is a command-line scripting environment that you can use to create, manage, and monitor WebLogic Server domains .

I recently encountered issue while connecting to WebLogic Server from WLST command connect(‘user’,’password’,’adminserver’)) remotely.

Issue: WLST connect from local machine (where WebLogic Server is running) is working fine where as connection from remote machine (WLST on remote machine) reported error. dumpStack() reported error Bootstrap to [IP/[IP]:[Admin Port] failed. It is likely that 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() for help on 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 22, 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 17 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 that 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 that the remote side declared peer gone on this JVM] wls:/offline>

_________________

 

Checks done 

1. Ensure that remote machine can access WebLogic Server (there is no firewall) : This worked for me and I was able 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 two host names

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

 

 

 

Fix: Ensure that client machine (from where WLST is being run), can resolve hostname mentioned in Listen Address of Admin Server (innowave21 in my case)

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

192.168.1.12   innowave21

 

Note: After adding entry in hosts file (or DNS server) for innowave21, I was able to connect using WLST.

 

Learn Oracle Weblogic Server Administration

 

Get 100 USD OFF + 100% Money Back Guarantee

Click here to get Early Bird Discounts

About the Author Atul Kumar

Oracle ACE, Author, Speaker and Founder of K21 Technologies & K21 Academy : Oracle Gold Partner specialising in Design, Implement, and Trainings.

follow me on:

Leave a Comment:

1 comments
Aftab says January 19, 2015

Hi Atul,

The blog postings are very useful and in fact helped me resolving one of my critical issues in production recently. Thanks A lot.

Just thought of taking your advice on going ahead with
SSL offloading at LBR.

We are using JD Edwards Enterprise one and configured our web server as follows.

USER – LBR – OHS1 – WLS1
OHS2 – WLS2

Weblogic servers are clustered.

if i want to offload SSL at LBR, what changes i might requires at OHS and WLS layers?

Any Suggestions/Advice.

Best Regards,
Aftab

Reply
Add Your Reply