This content has been marked as final. Show 6 replies
Thanks for the reply. I am running this in a single linux machine. what could be the network problem?
my hosts file:
# cat /etc/hosts
# HEADER: This file was autogenerated at Mon Sep 17 10:10:50 +0000 2012
# HEADER: by puppet. While it can still be managed manually, it
# HEADER: is definitely not recommended.
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain loghost
10.111.11.111 abc03xxx.us.comp.com abc03xxx
For more info, Please find the complete scripts steps below.
Your environment has been set.
Going to create domain [test_domain:3088] on admin_server, please wait...
Attempting to connect to server.....Connected to server!
Now apply customer settings to the new domain...
Creating TEST server...
Configurating TEST server listening port...
Initializing WebLogic Scripting Tool (WLST) ...
Welcome to WebLogic Server Administration Scripting Shell
Type help() for help on available commands
Creating JDBC Datasource...MYDSONE
Creating JDBC Datasource...MYDSTWO
Connecting Admin Server at t3://10.111.11.111:3088...
Connecting to t3://10.111.11.111:3088 with userid weblogic ...
Successfully connected to Admin Server 'admin_server' that belongs to domain 'test_domain'.
Warning: An insecure protocol was used to connect to the
server. To ensure on-the-wire security, the SSL port or
Admin port should be used instead.
Stopping Admin Server at t3://10.111.11.111:3088...
Shutting down the server admin_server with force=false while connected to admin_server ...
WLST lost connection to the WebLogic Server that you were
connected to, this may happen if the server was shutdown or
partitioned. You will have to re-connect to the server once the
server is available.
Disconnected from weblogic server: admin_server
Disconnected from weblogic server:
Starting weblogic server ...
WLST-WLS-1348045187214: <Sep 19, 2012 1:59:47 AM PDT> <Info> <Security> ......
WLST-WLS-1348045187214: <Sep 19, 2012 1:59:54 AM PDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
Server started successfully.
Disconnected from weblogic server:
Exiting WebLogic Scripting Tool.
Creating TEST machine...
Failed to connect to t3://10.111.11.111:3088: Bootstrap to abc03xxx.us.comp.com/10.111.11.111:3088 failed. It is likely that the remote side declared peer gone on this JVM
Please let me know what can I check.
thanks in advance
Thanks for the reply kalyan.
Where should I add this? I am calling .py file from .sh file
echo "Configurating datasources"
java weblogic.WLST /aaa/test/Test_Home/files/py/WLS_setDataSources.py /aaa/test/Test_Home test_domain test_server jdbc:oracle:thin:@localhost:1521:TEST null test_user .......
# Create Machine
echo "Creating machine..."
# create datasource ...
#Strat Admin Server
connect(uname, pwd, servurl)
startServer(server_name, domain_name, server_url, uname, pwd, domain_home)
print 'Admin Server not start'
Add the following parameter -Dweblogic.rjvm.enableprotocolswitch=true under your startup script like setDomainEnv.sh file under java options.
set this setDomainEnv.sh file under classpath by running
. ./setDomainEnv.sh file and then start your wlst command to execute your .py file.
this will help you to resolve the problem.
If I apply -Dweblogic.rjvm.enableprotocolswitch=true also I am getting the error.
BUT what I observed is after starting the server using WLST
I am not able to access admin console.
java weblogic.Admin -url t3://localhost:3081 -username weblogic -password Weblogic1 PING
is not pinging. So some some network setting is not allowing t3 protocol I guess.
So I took another machine and tested the same (startServer using wlst) there it is pinging properly. So I moved the entire setup to the other machine and it is working fine there.
But not able to find the issue with my first machine..is it weblogic or linux level restriction. I am not sure.
thanks in advance.