weblogic t3协议报错

目录

1、背景

2、报错信息

3、检测t3协议是否正常

---

1、背景

        在上次生产环境版本升级的时候遇到问题，运维人员告知升级失败，然后首先怀疑是版本问题，就仔细检查了版本信息，没发现异常，然后与运维沟通获取到报错信息如下，看了一下日志，服务器连接出现问题，怀疑是网络问题，于是就找了下负责网络的人员，网管说网络没什么问题，服务器都是通的，于是打算回退下版本试试，结果回退版本也失败，报错信息依然是这个问题，然后就围绕这个问题问了下相关专家，专家告知，可能是网络原因，导致t3协议无法连接，并告知了检测方案，后来经过验证，发现确实如此，然后就又找了下网管，网管说近期有对ip进行整合，可能出现问题，然后重新开启连接之后就正常，因此记录一下。

2、报错信息

19:33:02 /data/test.xml:58: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Unable to connect to 't3://10.10.0.110:7011': Bootstrap to: sfile.test.com/t3://10.10.0.110:7011' over: 't3' got an error or timed out. Ensure the url represents a running admin server and that the credentials are correct. If using http protocol, tunneling must be enabled on the admin server.
19:33:02   at weblogic.Deployer.run(Deployer.java:72)
19:33:02   at weblogic.Deployer.mainWithExceptions(Deployer.java:62)
19:33:02   at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
19:33:02   at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
19:33:02   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
19:33:02   at java.lang.reflect.Method.invoke(Method.java:585)
19:33:02   at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy.java:419)
19:33:02   at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.java:349)
19:33:02   at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:291)
19:33:02   at sun.reflect.GeneratedMethodAccessor4.invoke(Unknown Source)
19:33:02   at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
19:33:02   at java.lang.reflect.Method.invoke(Method.java:585)
19:33:02   at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:106)
19:33:02   at org.apache.tools.ant.Task.perform(Task.java:348)
19:33:02   at org.apache.tools.ant.Target.execute(Target.java:390)
19:33:02   at org.apache.tools.ant.Target.performTasks(Target.java:411)
19:33:02   at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1399)
19:33:02   at org.apache.tools.ant.Project.executeTarget(Project.java:1368)
19:33:02   at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
19:33:02   at org.apache.tools.ant.Project.executeTargets(Project.java:1251)
19:33:02   at org.apache.tools.ant.Main.runBuild(Main.java:809)
19:33:02   at org.apache.tools.ant.Main.startAnt(Main.java:217)
19:33:02   at org.apache.tools.ant.launch.Launcher.run(Launcher.java:280)
19:33:02   at org.apache.tools.ant.launch.Launcher.main(Launcher.java:109)
19:33:02 Caused by: weblogic.deploy.api.tools.deployer.DeployerException: Unable to connect to 't3://10.10.0.110:7011': Bootstrap to: sfile.test.com/t3://10.10.0.110:7011' over: 't3' got an error or timed out. Ensure the url represents a running admin server and that the credentials are correct. If using http protocol, tunneling must be enabled on the admin server.
19:33:02   at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:316)
19:33:02   at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:137)
19:33:02   at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)
19:33:02   at weblogic.utils.compiler.Tool.run(Tool.java:158)
19:33:02   at weblogic.utils.compiler.Tool.run(Tool.java:115)
19:33:02   at weblogic.Deployer.run(Deployer.java:70)
19:33:02   ... 23 more
19:33:02 Caused by: javax.enterprise.deploy.spi.exceptions.DeploymentManagerCreationException
19:33:02   at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.<init>(WebLogicDeploymentManagerImpl.java:121)
19:33:02   at weblogic.deploy.api.spi.factories.internal.DeploymentFactoryImpl.getDeploymentManager(DeploymentFactoryImpl.java:84)
19:33:02   at weblogic.deploy.api.tools.SessionHelper.getDeploymentManager(SessionHelper.java:432)
19:33:02   at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:304)
19:33:02   ... 28 more
19:33:02 Caused by: weblogic.deploy.api.spi.exceptions.ServerConnectionException
19:33:02   at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectionImpl.java:143)
19:33:02   at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.getNewConnection(WebLogicDeploymentManagerImpl.java:148)
19:33:02   at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.<init>(WebLogicDeploymentManagerImpl.java:118)
19:33:02   ... 31 more
...

3、检测t3协议是否正常

t3协议2个服务器是否可以访问的验证命令
例子 10.10.10.107连接10.10.10.108  验证
1、weblogic路径下 执行环境设置脚本
 cd /data/Oracle/Middleware/wlserver/server/bin
 sh setWLSEnv.sh 
2、返回上级目录 验证是否可以访问另一台的控制台地址（控制台的账户密码） 
cd /data/Oracle/Middleware/wlserver/common/bin

sh wlst.sh 
验证：connect("test","test123", "t3://10.10.10.108:7001")

出现 Successfully connected to managed Server 'test' that belongs to domain 'base_domain'.

则表示可以正常连接

实际操作举例：
--10.10.10.107连接10.10.10.108 验证---
[weblogic@test1 bin]$ cd /data/Oracle/Middleware/wlserver/server/bin
[weblogic@test1 bin]$ sh setWLSEnv.sh 
CLASSPATH=/data/Oracle/Middleware/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/data/Oracle/Middleware/patch_ocp371/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/weblogic/JDK/jdk1.6.0_113/lib/tools.jar:/data/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/data/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.jar:/data/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.6.0.jar:/data/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/data/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/data/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar:

PATH=/data/Oracle/Middleware/wlserver/server/bin:/data/Oracle/Middleware/modules/org.apache.ant_1.7.1/bin:/home/weblogic/JDK/jdk1.6.0_113/jre/bin:/home/weblogic/JDK/jdk1.6.0_113/bin:/home/weblogic/apache-ant-1.8.2/bin:/home/weblogic/JDK/jdk1.6.0_113/bin:/usr/local/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/weblogic/.local/bin:/home/weblogic/bin

Your environment has been set.

[weblogic@test1 bin]$ cd /data/Oracle/Middleware/wlserver/common/bin
[weblogic@test1 bin]$ sh wlst.sh 

CLASSPATH=/data/Oracle/Middleware/patch_wls1036/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/data/Oracle/Middleware/patch_ocp371/profiles/default/sys_manifest_classpath/weblogic_patch.jar:/home/weblogic/JDK/jdk1.8.0_113/lib/tools.jar:/data/Oracle/Middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/data/Oracle/Middleware/wlserver/server/lib/weblogic.jar:/data/Oracle/Middleware/modules/features/weblogic.server.modules_10.3.6.0.jar:/data/Oracle/Middleware/wlserver_10.3/server/lib/webservices.jar:/data/Oracle/Middleware/modules/org.apache.ant_1.7.1/lib/ant-all.jar:/data/Oracle/Middleware/modules/net.sf.antcontrib_1.1.0.0_1-0b2/lib/ant-contrib.jar::/data/Oracle/Middleware/utils/config/10.3/config-launch.jar::/data/Oracle/Middleware/wlserver_10.3/common/derby/lib/derbynet.jar:/data/Oracle/Middleware/wlserver_10.3/common/derby/lib/derbyclient.jar:/data/Oracle/Middleware/wlserver_10.3/common/derby/lib/derbytools.jar::

Initializing WebLogic Scripting Tool (WLST) ...

Jython scans all the jar files it can find at first startup. Depending on the system, this process may take a few minutes to complete, and WLST may not return a prompt right away.

Welcome to WebLogic Server Administration Scripting Shell

Type help() for help on available commands

wls:/offline> connect("test","test123", "t3://10.10.10.108:7001")
Connecting to t3://t3://10.10.10.108:7001 with userid weblogic ...
Successfully connected to managed Server 'test108' that belongs to domain 'base_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.

wls:/base_domain/serverConfig>