weblogic.rmi.UnknownHostException: Could not init server [T3://120.120.120.121:7001/ProofRunMonitor120.120.120.121] - with nested exception: [javax.naming.CommunicationException [Root exception is java.net.ConnectException: No server found at T3://120.120.120.121:7001]]

Oracle Community | 3004 | 1 decade ago
  1. 0

    System in the cluster not responding

    Oracle Community | 1 decade ago | 3004
    weblogic.rmi.UnknownHostException: Could not init server [T3://120.120.120.121:7001/ProofRunMonitor120.120.120.121] - with nested exception: [javax.naming.CommunicationException [Root exception is java.net.ConnectException: No server found at T3://120.120.120.121:7001]]
  2. 0

    ystem in the cluster not responding

    Oracle Community | 1 decade ago | 3004
    weblogic.rmi.UnknownHostException: Could not init server [T3://120.120.120.121:7001/ProofRunMonitor120.120.120.121] - with nested exception: [javax.naming.CommunicationException [Root exception is java.net.ConnectException: No server found at T3://120.120.120.121:7001]]

    Root Cause Analysis

    1. weblogic.rmi.UnknownHostException

      Could not init server [T3://120.120.120.121:7001/ProofRunMonitor120.120.120.121] - with nested exception: [javax.naming.CommunicationException [Root exception is java.net.ConnectException: No server found at T3://120.120.120.121:7001]]

      at java.lang.Throwable.fillInStackTrace()
    2. Java RT
      Throwable.fillInStackTrace
      1. java.lang.Throwable.fillInStackTrace(Native Method)
      1 frame