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
failed to make pool eng23567: javax.naming.NameAlreadyBoundException; remaining name 'weblogic.jdbc.connection Pool.eng23567'
via Oracle Community by 3004, 1 year ago
failed to make pool eng23567: javax.naming.NameAlreadyBoundException; remaining name 'weblogic.jdbc.connection Pool.eng23567'
via Google Groups by Murray Bodor, 7 months ago
Connection pool com.xxx.jdbc.pool already exists
via Oracle Community by 3004, 1 year ago
Connection pool com.xxx.jdbc.pool already exists
weblogic.common.ResourceException: failed to make pool eng23567:
javax.naming.NameAlreadyBoundException; remaining name 'weblogic.jdbc.connection
Pool.eng23567'	at weblogic.jdbc.common.internal.ConnectionPool.startup(ConnectionPool.java:330)	at weblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.java:386)	at weblogic.jdbc.common.internal.ConnectionPool.createPool(ConnectionPool.java:368)	at com.connect.TableBean.getTMDetails(TableBean.java:75)	at com.connect.TableBeanEOImpl.getTMDetails(TableBeanEOImpl.java:56)