[jboss-jira] [JBoss JIRA] Updated: (JBAS-3318) Secondary http sessions in a cross-context request are not replicated

Dimitris Andreadis (JIRA) jira-events at jboss.com
Tue Jul 25 11:32:11 EDT 2006


     [ http://jira.jboss.com/jira/browse/JBAS-3318?page=all ]

Dimitris Andreadis updated JBAS-3318:
-------------------------------------

    Fix Version/s: JBossAS-4.0.6.CR1
                       (was: JBossAS-4.0.5.CR1)

Brian, moving to the next release, unless you want to work on it.

> Secondary http sessions in a cross-context request are not replicated
> ---------------------------------------------------------------------
>
>                 Key: JBAS-3318
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3318
>             Project: JBoss Application Server
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Web (Tomcat) service, Clustering
>    Affects Versions: JBossAS-3.2.7 Final, JBossAS-3.2.6 Final, JBossAS-4.0.2 Final, JBossAS-4.0.3 Final, JBossAS-4.0.3 SP1, JBossAS-3.2.8 Final, JBossAS-3.2.8.SP1, JBossAS-4.0.4.GA
>            Reporter: Brian Stansberry
>         Assigned To: Brian Stansberry
>             Fix For: JBossAS-5.0.0.Beta, JBossAS-4.0.6.CR1
>
>   Original Estimate: 4 days
>  Remaining Estimate: 4 days
>
> If cross-context requests are enabled and a servlet accesses the request dispatcher and dispatches the request to a different context, no session replication is performed for the session in that second context.  This is because a dispatched request bypasses the ClusteredSessionValve, and thus replication is not triggered.
> Likely solution is to have ClusteredSessionValve create some sort of ThreadLocal replication context.  Any JBossCacheManager that accesses a session will associate itself and the session with the replication context..  Then when the request returns through the ClusteredSessionValve, all sessions in the context will be replicated.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list