[
https://issues.apache.org/jira/browse/OWB-646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13256281#comment-13256281
]
Mark Struberg commented on OWB-646:
-----------------------------------
Hi!
Please just set a breakpoint in
1.) WebBeansConfigurationListener#requestDestroyed()
This (amongst others) writes the SessionContext (held in RAM due to
performance reasons) into the real servlet Session.
2.) BackupSessionService.backupSession()
and you will see exactly that they get called in the wrong order since
tomcat-7.0.22. I assume it's a bug or misbehaviour in tomcat7 since then.
What happens since 7.0.22 is that msm first backs up the session, and only
later in the request we write the SessionContext into the Session...
The two important Valves are: StandardEngineValve and SessionTrackerValve which
are in different order in tomcat < 7.0.22 and >= 7.0.22.
> Failover does not work (again)
> ------------------------------
>
> Key: OWB-646
> URL: https://issues.apache.org/jira/browse/OWB-646
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Context and Scopes
> Affects Versions: 1.1.3
> Environment: Tomcat 7.0.22, OWB 1.1.3, memcached-session-manager 1.6.1
> Should be unrelated: MyFaces 2.1.6, CODI 1.0.3, ExtVal 2.0.5, Hibernate
> 3.6.9, BVAL 0.3
> Reporter: Thomas Andraschko
> Assignee: Mark Struberg
> Labels: Cluster, Failover, Replication, Tomcat
> Fix For: 1.1.4
>
> Attachments: OWB-646.patch
>
>
> Martin (from msm) and I created an test app for this issue last year:
> https://github.com/magro/msm-sample-webapp/tree/openwebbeans and this was
> fixed within OWB-523.
> However, if i upgrade the Tomcat to 7.0.22 or newer, the bean replication
> does not work again.
> As you can see in this test app, the normal failover works (right input
> field) but the bean failover (left input field) does not work.
> I tested several Tomcat version and 7.0.21 or older works without problems,
> so the problem occured with Tomat 7.0.22.
> I don't know exactly if the problem is related to the OWB failover mechanism
> or Tomcat :)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira