javax.naming.NamingException: ConnectionPoolManager is not yet available.

Oracle Community | 3004 | 1 decade ago
tip
Do you know that we can give you better hits? Get more relevant results from Samebug’s stack trace search.
  1. 0

    javax.naming.NamingException: ConnectionPoolManager is not yet available in Attatched connector

    Oracle Community | 1 decade ago | 3004
    javax.naming.NamingException: ConnectionPoolManager is not yet available.
  2. 0

    ConnectionPoolManager is not yet available

    Oracle Community | 1 decade ago | 3004
    javax.naming.NamingException: ConnectionPoolManager is not yet available.

    Root Cause Analysis

    1. javax.naming.NamingException

      ConnectionPoolManager is not yet available.

      at weblogic.jndi.internal.WLContextImpl.lookup()
    2. weblogic.jndi.internal
      WLContextImpl.lookup
      1. weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:346)
      2. weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:332)
      2 frames
    3. Java RT
      InitialContext.lookup
      1. javax.naming.InitialContext.lookup(InitialContext.java:347)
      1 frame
    4. Unknown
      HelloWorldBean.main
      1. HelloWorldBean.execute(HelloWorldBean.java:35)
      2. HelloWorldBean.main(HelloWorldBean.java:64)
      2 frames