Oracle 8.1.6 EJB: session objects == memory leak?

Hi,

I am working on a project that uses 8.1.6 and the Oracle JVM as an application server, processing requests for a number of multithreaded clients (mainly servlet containers but also a custom app that pulls data off a JMS queue and invokes an EJB)

In order for us to use the EJBs in a multithreaded environment we have made use of the service.createSubContext(":session1") API and then run each EJB request in a new session. The problem then appears to be that the server does not release the memory allocated to these session objects and eventually it runs out of memory with an ORA-04031 error.

None of the examples in the documentation show how to logout/destroy a session subcontext object, they simply allow the JVM to exit, after which all the memory is returned. In our environment, other than restarting the client services every few hours there seems little we can do to get the server to reallocate this memory.

My question (finally) does anyone know how to destroy these session subcontext objects?

TIA Damian Received on Thu Feb 15 2001 - 23:57:00 CST