weblogic.jdbc.pool.Driver

Exception #2475141

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web2

  • via Unknown by faria_hassan,
  • via Unknown by 3004,
  • Stack trace

    • weblogic.jdbc.pool.Driver at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:182) at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:109) at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:771) at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:416) at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:330) at weblogic.jdbc.common.internal.JdbcInfo.initPools(JdbcInfo.java:117) at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:200) at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11) at java.lang.reflect.Method.invoke(Native Method) at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219) at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java:109) at weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java:62) at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:125) at weblogic.common.internal.ResourceAllocator.makeResources(ResourceAllocator.java:771) at weblogic.common.internal.ResourceAllocator.<init>(ResourceAllocator.java:416) at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:330) at weblogic.jdbc.common.internal.JdbcInfo.initPools(JdbcInfo.java:117) at weblogic.jdbc.common.internal.JdbcInfo.startup(JdbcInfo.java:200) at weblogic.jdbc.common.internal.JdbcStartup.main(JdbcStartup.java:11) at java.lang.reflect.Method.invoke(Native Method) at weblogic.t3.srvr.StartupThread.runMain(StartupThread.java:219) at weblogic.t3.srvr.StartupThread.doWork(StartupThread.java:109) at weblogic.t3.srvr.PropertyExecuteThread.run(PropertyExecuteThread.java:62)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    We couldn't find other users who have seen this exception.