[
https://issues.apache.org/jira/browse/WW-166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13117568#comment-13117568
]
Maurizio Cucchiara commented on WW-166:
---------------------------------------
Please ask this kind of question on the [user
ML|http://struts.apache.org/mail.html]
> Runtime exception after starting Tomcat
> ---------------------------------------
>
> Key: WW-166
> URL: https://issues.apache.org/jira/browse/WW-166
> Project: Struts 2
> Issue Type: Bug
> Components: XML Configuration
> Affects Versions: WW 2.0-beta1
> Environment: Tomcat 4.1.24
> Reporter: Tracy Snell
> Assignee: Jason Carreira
>
> 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)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
