配置管理器不应该为空错误
我们有一个 WAR，其中包含 S2 代码，并且该 WAR 部署在 Glassfish 上。当我们部署代码并尝试使用应用程序（在浏览器中）时，我们注意到配置管理器不应为空错误。部署后重新启动应用服务器就不会出现该错误。
日志：
[#|2009-12-04T12:55:47.215-0500|SEVERE|sun-appserver2.1|org.apache.catalina.core.ApplicationFilterConfig|_ThreadID=48;_ThreadName=RMI TCP Connection(5846)-127.0.0.1;_RequestID=d8d812b6-c1e1-4b56-a707-68e071ffb9e9;|ApplicationFilterConfig.doAsPrivilege
java.lang.IllegalStateException: The configuration manager shouldn't be null
at org.apache.struts2.dispatcher.Dispatcher.getContainer(Dispatcher.java:849)
at org.apache.struts2.dispatcher.Dispatcher.cleanup(Dispatcher.java:256)
at org.apache.struts2.dispatcher.FilterDispatcher.destroy(FilterDispatcher.java:221)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
我对这个问题进行了一些研究，发现这是一个错误S2。尽管如此，错误已修复（最后评论），但修复对我们不起作用。也许是因为票证中没有提到 glassfish 服务器。
有没有人遇到过类似的问题？...或者有解决办法吗？
we have a WAR that has S2 code in it and the WAR is deployed on Glassfish. We are noticing the configuration manager shouldn't be null error when we deploy the code and try to bring use the application (in browser). The error does not happen when the Application server is restarted after the deployment.
Log:
[#|2009-12-04T12:55:47.215-0500|SEVERE|sun-appserver2.1|org.apache.catalina.core.ApplicationFilterConfig|_ThreadID=48;_ThreadName=RMI TCP Connection(5846)-127.0.0.1;_RequestID=d8d812b6-c1e1-4b56-a707-68e071ffb9e9;|ApplicationFilterConfig.doAsPrivilege
java.lang.IllegalStateException: The configuration manager shouldn't be null
at org.apache.struts2.dispatcher.Dispatcher.getContainer(Dispatcher.java:849)
at org.apache.struts2.dispatcher.Dispatcher.cleanup(Dispatcher.java:256)
at org.apache.struts2.dispatcher.FilterDispatcher.destroy(FilterDispatcher.java:221)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
I researched this issue a bit and found that this is an error with S2. Even though, bug is fixed (last comment) that fix does not work for us. Maybe because glassfish server is not mentioned in the ticket.
Has anyone faced similar issues?...or has a fix?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果 ActionContextCleanup< 则此问题已修复/a> 过滤器已添加到 web.xml。它适用于我的 GlassFish V2。 FilterDispatcher 是应该清理操作，但该调度程序似乎在 GlassFish V2 上存在一些问题。因此 ActionContextCleanup Filter 应该与与您的 struts 页面匹配的 url 模式一起使用。
This is fixed if ActionContextCleanup Filter is added to web.xml. It worked for my on GlassFish V2. FilterDispatcher is suppose to clean up actions but this dispatcher seems to have some issues on GlassFish V2. So ActionContextCleanup Filter should be used with url pattern that matches your struts pages.