[jboss-user] [Tomcat Integration] - PersistentManager for sessions is broken in 5.1.0GA
Tomcat provides a way to store web sessions data that is resilient to server reboots using
the org.apache.catalina.session.PersistentManager as described in
http://tomcat.apache.org/tomcat-6.0-doc/config/manager.html but in jboss 5.1.0GA that
support is broken:
Using the following context.xml
| <Context cookies="true" crossContext="true">
| <Manager className="org.apache.catalina.session.PersistentManager"
maxIdleSwap="1200" saveOnRestart="true">
| <Store checkInterval="60"
className="org.apache.catalina.session.JDBCStore"
connectionURL="jdbc:mysql://localhost:3306/bligoo?user=bligoo&password=bligoo"
driverName="com.mysql.jdbc.Driver" sessionAppCol="app_name"
sessionDataCol="session_data" sessionIdCol="session_id"
sessionLastAccessedCol="last_access"
sessionMaxInactiveCol="max_inactive" sessionTable="tomcat_sessions"
sessionValidCol="valid_session"/>
| </Manager>
|
<InstanceListener>org.jboss.web.tomcat.security.RunAsListener</InstanceListener>
| </Context>
|
It refuses to start with the following exception:
| 2009-11-02 23:11:54,292 INFO
[org.jboss.web.tomcat.service.deployers.TomcatDeployment] (main) deploy, ctxPath=/
| 2009-11-02 23:11:55,619 ERROR
[org.jboss.web.tomcat.service.deployers.JBossContextConfig] (main) XML error parsing:
context.xml
| org.jboss.xb.binding.JBossXBException: Failed to parse source: Store not found as a
child of Manager in unordered_sequence: attributes?
| at
org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:203)
| at
org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:183)
| at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java:133)
| at
org.jboss.web.tomcat.service.deployers.JBossContextConfig.processContextConfig(JBossContextConfig.java:573)
| at
org.jboss.web.tomcat.service.deployers.JBossContextConfig.init(JBossContextConfig.java:536)
| at
org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:279)
| at
org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
| at org.apache.catalina.core.StandardContext.init(StandardContext.java:5436)
| at org.apache.catalina.core.StandardContext.start(StandardContext.java:4148)
| at
org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeployInternal(TomcatDeployment.java:310)
| at
org.jboss.web.tomcat.service.deployers.TomcatDeployment.performDeploy(TomcatDeployment.java:142)
| at
org.jboss.web.deployers.AbstractWarDeployment.start(AbstractWarDeployment.java:461)
| at org.jboss.web.deployers.WebModule.startModule(WebModule.java:118)
| at org.jboss.web.deployers.WebModule.start(WebModule.java:97)
| at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
| at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
| at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
| at java.lang.reflect.Method.invoke(Method.java:597)
| at
org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
| at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
| at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
| at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
| at org.jboss.system.microcontainer.ServiceProxy.invoke(ServiceProxy.java:206)
| at $Proxy38.start(Unknown Source)
|
Is there a work arround? This bug is preventing us from upgrading from jboss4 to 5
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4264029#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...