You both are having classloader issues. See this
http://www.jboss.org/wiki/Wiki.jsp?page=JBossClassLoadingUseCases
You can work around this by disabling the "UseJBossWebLoader" in the
jbossweb-tomcat50.sar/META-INF/jboss-service.xml file.
Best to read up on the JBoss UCL to get a handle on why
Ben,
After I read your response I thought about the issues (as I understood them)
for quite awhile.
My first instinct was to extend JVMRouteFilter to wrap the request on the way
in and replace the old jvmRoute with the current servicing node's jvmRoute much
like you do for cookies.
Unfortunat
Hello All,
I recently moved a cluster from JBoss 3.0.7 to JBoss 3.2.7 and was surprised to
see that the HTTP Session replication appears to have been completely
overhauled.
I have everything working, but am seeing the occaisional message from clients
that have cookies disabled.
Example:
200
