A little late reply, The problem is narrowed down to.. If the JVM( running tomcat) memory settings are changed in the environment variables and/or the catalina.bat and/or service.bat (depending on the tomcat install), this exception is thrown by the CAS client which is misleading and confusing since the CAS client works fine if no changes are made to the JVM memory settings.
Thank You for your patience. Kavita On Fri, Jul 31, 2009 at 3:53 PM, Marvin Addison <[email protected]>wrote: > > I have tried to isolate the problem, CAS throws this error when there is > an > > error in the tomcat configuration file and /or > > insufficient memory. > > Can you repost the error again? You've cited a couple of different > problems in this thread, and I'd like to get clear on the one you > mean. > > > Is it possible for the CAS client to let OutOfMemory exceptions to be > > handled by the underlying container? > > OutOfMemoryError is an _error_, not an exception, and in almost all > cases is unrecoverable. It doesn't matter who handles it -- it's game > over and you need to kill the JVM process and restart. > > M > > -- > 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 > -- Kavita Tipnis -- 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
