[
https://issues.apache.org/jira/browse/GERONIMO-4855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755391#action_12755391
]
Shawn Jiang commented on GERONIMO-4855:
---------------------------------------
Session Sticky does not resolve the failed login info replication problem.
They are totally different problems from each other.
As Ben stated above, Tomcat native clustering support login info replication
while Geronimo can't.
> 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.
