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

Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by 3004, 1 year ago
ConnectionPoolManager is not yet available.
javax.naming.NamingException: ConnectionPoolManager is not yet available.
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:347)
at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:333)
at javax.naming.InitialContext.lookup(InitialContext.java:350)
at undefined.Main.test(Main.java:51)
at undefined.Main.main(Main.java:35)

Users with the same issue

You are the first who have seen this exception. Write a tip to help other users and build your expert profile.

Know the solutions? Share your knowledge to help other developers to debug faster.