Kbase P115655: OutOfMemoryError using connection pooling for AppServer in state free with OpenClient
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/24/2006 |
|
Status: Unverified
FACT(s) (Environment):
OpenEdge 10.0B
SYMPTOM(s):
OutOfMemoryError using connection pooling for AppServer in state free with openClient
Memory leak on AppServer using state free sessions with connection pooling.
Stack trace reads : com.progress.open4gl.Open4GLException: java.lang.OutOfMemoryError:null
com.progress.open4gl.dynamicapi.Session.runProcedure
com.progress.open4gl.Open4GLException
com.progress.open4gl.dynamicapi.Session.runProcedure
com.progress.open4gl.javaproxy.ProObject.runProcedure
Application is handling a large load of requests
CAUSE:
A large portion of the heap is taken up by byte arrays allocated to handle message buffers.
Each session in the connection pool maintains one of these byte arrays
This particular memory consumption happened because we were not correctly freeing the expired session objects, and still had a reference to them, so they along with their byte arrays were not being garbage-collected.
FIX:
Upgrade to the Service Pack 5 for OpenEdge