Out of memory is out of memory.
You either use too much memory and have to give more memory to the JVM or there is a resource leak somewhere.


You can use a memory profiler or another debugging tool to see where the memory is used.

If you think it is a DBCP problem please provide a test case.

-- Dirk


Vivian Fonger wrote:

Hi everyone,
I ran into an outofmemory error with DBCP, can anyone give me
suggestions on how to fix this problem?? Here is the exception:
[Thread-0] ERROR 3102aused by:
org.apache.commons.dbcp.SQLNestedException: Connect failed, cause: null
at
org.apache.commons.dbcp.PoolingDriver.connect(PoolingDriver.java:175)
at java.sql.DriverManager.getConnection(DriverManager.java:512)
at java.sql.DriverManager.getConnection(DriverManager.java:193)
at
com.accucast3.database.DatabaseResource.getConnection(DatabaseResource.j
ava:2043)
... 3 more
Caused by: java.lang.OutOfMemoryError
The OutOfMemoryError is thrown when the applicatoin tries to access the
following code:
Connection conn =
DriverManager.getConnection("jdbc:apache:commons:dbcp:internal");
Thanks
Vivian Fonger
Software Engineer
Socketware
[EMAIL PROTECTED]





--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to