Hello all.

We use CAS with audit logging to a database (JNDI WebSphere 6.1 datasource
used).
No special configuration of the datasource has been done.

The problem we are facing is that, when a problem occurs in the network such
as SocketTimeouts for exemple, the SQL orders don't succeed.
Even more, there might be retries. In any case, SQL statements are still
pending in memory, and their number rises quickly.
As a result, the JVM memory consumption begins to grow with theses SQL
statements and/or SQL Exceptions.
Of course it finally reaches the max, causing an Out Of Memory Exception.

Has anyone been having the same problem ?
Any suggestions ?

Thanks for helping

-- 
You are currently subscribed to [email protected] as: 
[email protected]
To unsubscribe, change settings or access archives, see 
http://www.ja-sig.org/wiki/display/JSG/cas-user

Reply via email to