[
https://issues.apache.org/jira/browse/GERONIMO-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755336#action_12755336
]
viola.lu commented on GERONIMO-4855:
------------------------------------
First, pls add <distributable> element to your app web.xml
Second:modify Engine setting in you server.xml under $G_Dir/var/catalina/ with
below:
<Engine name="Catalina" defaultHost="${ServerHostname}" jvmRoute="NODE01">
Make sure your mod_jk or mod_proxy server node name same as jvmRoute
definition, which is used to enable sticky session.
After that, your login page will sticky to one server, no 404 error.Login
Verification is a built-in process, not relation with Servlet or JSP.
> Clustering can not work when the application needs login information
> --------------------------------------------------------------------
>
> Key: GERONIMO-4855
> URL: https://issues.apache.org/jira/browse/GERONIMO-4855
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: Clustering
> Affects Versions: 2.2
> Environment: windows sp2
> jdk1.6
> Reporter: liangkun
> Attachments: demo-realm.xml, file-realm-demo-2.1.1.2.war
>
>
> When I using WADI clustering and tomcat native clustering there are the same
> problem:
> If the application on the different node needs the security information to
> access some page then firefox gives the following error information:
> HTTP Status 404 - /demo/protect/j_security_check
> type Status report
> message /demo/protect/j_security_check
> description The requested resource (/demo/protect/j_security_check) is not
> available.
> so it is likely clustering can not access any resource which need security
> check.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
