oracle.ons.SubscriptionException: Subscription request timed out after 30000 millseconds. Possible causes: OPMN may not be running, you may have an OPMN running in an alternate ORACLE_HOME using duplicate port values, or OPMN may be misconfigured.

Oracle Community | Marius2 | 9 years ago
tip
Your exception is missing from the Samebug knowledge base.
Here are the best solutions we found on the Internet.
Click on the to mark the helpful solution and get rewards for you help.
  1. 0

    Problems starting oc4j using RAC, ONS and connection pool

    Oracle Community | 9 years ago | Marius2
    oracle.ons.SubscriptionException: Subscription request timed out after 30000 millseconds. Possible causes: OPMN may not be running, you may have an OPMN running in an alternate ORACLE_HOME using duplicate port values, or OPMN may be misconfigured.

    Root Cause Analysis

    1. oracle.ons.SubscriptionException

      Subscription request timed out after 30000 millseconds. Possible causes: OPMN may not be running, you may have an OPMN running in an alternate ORACLE_HOME using duplicate port values, or OPMN may be misconfigured.

      at oracle.ons.SubscriptionNotification.waitForReply()
    2. oracle.ons
      Subscriber.<init>
      1. oracle.ons.SubscriptionNotification.waitForReply(SubscriptionNotification.java:83)
      2. oracle.ons.ONS.addSubscriber(ONS.java:669)
      3. oracle.ons.Subscriber.realStartup(Subscriber.java:104)
      4. oracle.ons.Subscriber.<init>(Subscriber.java:80)
      4 frames
    3. Oracle jdbc
      OracleFailoverEventHandlerThread$1.run
      1. oracle.jdbc.pool.OracleFailoverEventHandlerThread$1.run(OracleFailoverEventHandlerThread.java:69)
      1 frame
    4. Java RT
      AccessController.doPrivileged
      1. java.security.AccessController.doPrivileged(Native Method)
      1 frame
    5. Oracle jdbc
      OracleFailoverEventHandlerThread.run
      1. oracle.jdbc.pool.OracleFailoverEventHandlerThread.run(OracleFailoverEventHandlerThread.java:61)
      1 frame