java.net.ConnectException: t3://host:port: Bootstrap to host/host:port failed. It is likely that the remote side declared peer gone on this JVM]
at weblogic.jndi.internal.ExceptionTranslator.toNamingException(ExceptionTranslator.java:40)
at weblogic.jndi.WLInitialContextFactoryDelegate.toNamingException(WLInitialContextFactoryDelegate.java:783)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:367)
at weblogic.jndi.Environment.getContext(Environment.java:315)
at weblogic.jndi.Environment.getContext(Environment.java:285)
at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:117)
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
at javax.naming.InitialContext.init(InitialContext.java:223)
at javax.naming.InitialContext.<init>(InitialContext.java:197)
at QueueSend.getInitialContext(QueueSend.java:117)
at QueueSend.main(QueueSend.java:81)
Caused by: java.net.ConnectException: t3://host:port: Bootstrap to host/host:port failed. failed. It is likely
that the remote side declared peer gone on this JVM
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:203)
at weblogic.rjvm.ServerURL.findOrCreateRJVM(ServerURL.java:153)
at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:352)
... 9 more
Caused by: java.rmi.ConnectException: Bootstrap to
tt3://host:port: Bootstrap to host/host:port failed. failed. It is likely that the
remote side declared peer gone on this JVM
at weblogic.rjvm.ConnectionManager.bootstrap(ConnectionManager.java:328)
at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(RJVMManager.java:251)
at weblogic.rjvm.RJVMManager.findOrCreate(RJVMManager.java:194)
at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(RJVMFinder.java:225)
at weblogic.rjvm.RJVMFinder.findOrCreate(RJVMFinder.java:188)
... 11 more

Cause

If the Load Balancer/proxy port is not the same as the WLS port, WLS
throws an exception rejecting the connection attempt during
bootstrapping, saying that the ports don’t match (portMatches = false).
To fix this, either the WLS port has to match the Load Balancer/proxy
port or the switch -Dweblogic.rjvm.enableprotocolswitch=true needs to
be enabled. If the switch is enabled, it avoids throwing the exception
in the bootstrapping case by setting the portMatches variable to true.
Solution

Enable the switch -Dweblogic.rjvm.enableprotocolswitch=true as an
argument to the JVM on startup on all the managed servers within the
cluster.

最新文章

  1. MATLAB-RSP 随笔
  2. $(window).height()获取浏览器高度不准
  3. Fling——K
  4. hdu 4584 水题爽一发 *
  5. Gatling的进阶一
  6. jqgrid在页面出来竖型滚动条自动调整列宽
  7. C语言格式化输入输出函数
  8. 使用python爬取MedSci上的期刊信息
  9. $m$ 整除 $10^k$ 的一个充分条件
  10. 402 CSS菜鸟：transform and transition
  11. springboot based 主从数据源中间件方案
  12. 伪类target实现纯css模态框
  13. azkaban在centos下的部署安装
  14. React-router4 第二篇url-params url参数
  15. FFmpeg4.0笔记：rtsp2rtmp
  16. [转] Cacti+Nagios监控平台完美整合
  17. Angular2 表单验证相关
  18. java对象模型
  19. 安装memcached服务 和 php 安装memcache扩展
  20. PYPY_GC

热门文章

  1. 在 IIS8 中保持网站持续运行
  2. C#写文本文件，如何换行（添加换行符）
  3. 对php和java里面的static函数和static的一些理解
  4. HI-LO计数法，赌桌，与机会
  5. git提交忽略文件或文件夹
  6. [LeetCode] Minimum Number of K Consecutive Bit Flips 连续K位翻转的最小次数
  7. 【ocp新题】OCP 12c 062认证考试出现大量新题-8
  8. Python(多线程threading模块)
  9. Good Bye 2017 C. New Year and Curling
  10. （samba启动失败）smb.service: main process exited, code=exited, status=1/FAILURE