iwui errors in the log.

sivaramiyer

All,

I found the below errors in the iwui log file. I remember the same happening almost 6-7 weeks ago also. Has anyone ever seen this before? what could be causing this?

Restart of the iw server fixes this issue.

Thanks,
Sivaram

ApplicationDispatcher[/iw-cc] Servlet.service() for servlet base.ui.error_jsp threw exception
java.lang.ClassCastException: java.lang.OutOfMemoryError

ApplicationDispatcher[/iw-cc] Servlet.service() for servlet ccpro.filesys.area_navigation.lists.list_directory_jsp threw exception
java.lang.ClassCastException: java.lang.OutOfMemoryError

StandardWrapperValve[CommandServlet]: Servlet.service() for servlet CommandServlet threw exception
java.lang.ClassCastException: java.lang.OutOfMemoryError

JspFactoryImpl: Exception initializing page context
java.lang.IllegalStateException: Cannot create a session after the response has been committed

Adam Stoller

All, I found the below errors in the iwui log file. I remember the same happening almost 6-7 weeks ago also. Has anyone ever seen this before? what could be causing this? Restart of the iw server fixes this issue. Thanks, Sivaram ApplicationDispatcher[/iw-cc] Servlet.service() for servlet base.ui.error_jsp threw exception java.lang.ClassCastException: java.lang.OutOfMemoryError ApplicationDispatcher[/iw-cc] Servlet.service() for servlet ccpro.filesys.area_navigation.lists.list_directory_jsp threw exception java.lang.ClassCastException: java.lang.OutOfMemoryError StandardWrapperValve[CommandServlet]: Servlet.service() for servlet CommandServlet threw exception java.lang.ClassCastException: java.lang.OutOfMemoryError JspFactoryImpl: Exception initializing page context java.lang.IllegalStateException: Cannot create a session after the response has been committed

Looks like either you have insufficient memory on your server, TS has a memory leak somewhere, or some other application running on that server has a memory leak somewhere.

I'd suggest writing a script to periodically do a ps on the PID for the various TS services into a log file and see if you notice some unusual growth in any of those applications the next time you get these errors.

If the growth isn't there - then it's probably somewhere else...