[
https://issues.apache.org/struts/browse/WW-1417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ted Husted updated WW-1417:
---------------------------
Fix Version/s: 2.0.0
Status: Resolved (was: Closed)
> Session replication problem using clustered servers with weblogic
> -----------------------------------------------------------------
>
> Key: WW-1417
> URL: https://issues.apache.org/struts/browse/WW-1417
> Project: Struts 2
> Issue Type: Bug
> Components: Actions, Component Management, Dispatch
> Affects Versions: 2.0.x
> Environment: HP - UX , weblogic 81 SP 5, using one cluster of 4
> servers.
> Reporter: Jorge RodrÃguez
> Fix For: 2.0.0
>
>
> Hi, I have a doubt about the way which struts update the ActionForm's
> fields when that form already exist, this, because
> I have some problems with replicated sessions in a weblogic cluster, let me
> explain in detail:
> weblogic replicates a session (update changes for example) only when there is
> a call to the setAttribute Method of
> javax.servlet.http.HttpSession, but what happens if one of the objects
> attached with that session is updated by
> reference without calling the setAttribute method .. , in this case,
> weblogic won't perform an update of the object state,
> so, if i want to complete the request in other server of my cluster, that
> information is not updated ..
> this situation, i think, happens with the ActionForms ... is there only one
> call to the setAttribute method (when that form is new) ?, so, when it
> exist, only the fields are updated (by reference), but there isn't a call
> to the setAttribute method in the processPopulate method of RequestProcesor
> .. I checked the source code, but I didn't find anything..
> have you already seen something like that?,
> Thanks for your help.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
