zoukankan      html  css  js  c++  java
  • It is likely that the remote side declared peer gone on this JVM

    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.

  • 相关阅读:
    SGU 495 Kids and Prizes 概率DP 或 数学推理
    poj 2799 IP Networks 模拟 位运算
    uva 202 Repeating Decimals 模拟
    poj 3158 Kickdown 字符串匹配?
    uva 1595 Symmetry 暴力
    uva 201 Squares 暴力
    uva 1594 Ducci Sequence 哈希
    uva 1368 DNA Consensus String 字符串
    数字、字符串、列表的常用操作
    if条件判断 流程控制
  • 原文地址:https://www.cnblogs.com/davidwang456/p/3424683.html
Copyright © 2011-2022 走看看