[WW-166] Runtime exception after starting Tomcat

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: WW 2.0-beta1
• Component/s: XML Configuration

Environment

Tomcat 4.1.24

• Assignee: Jason Carreira
• Reporter: Tracy J. Snell
• Created: 01/May/03 02:56
• Updated: 29/Sep/11 19:48
• Resolved: 02/May/03 21:13

Description

If you have deployed an application on Tomcat and run it then restart the server you get a RuntimeException. It's related so Session serialization. There are a couple of work arounds.

1. Redeploy your application after starting Tomcat.
2. Erase the SESSIONS.ser file from the application directory in Tomcats work directory.

java.lang.RuntimeException: Fallback must be an instance of DefaultConfigurationManager
at com.opensymphony.xwork.interceptor.component.DefaultComponentManager.setFallback(DefaultComponentManager.java:40)
at com.opensymphony.webwork.lifecycle.RequestLifecycleFilter.doFilter(RequestLifecycleFilter.java:49)

Issue Links

• duplicates: XW-1054 DefaultComponentManager needs to implement Serializable