You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by "Mark Struberg (Resolved) (JIRA)" <ji...@apache.org> on 2012/04/04 00:14:25 UTC

[jira] [Resolved] (OWB-646) Failover does not work (again)

     [ https://issues.apache.org/jira/browse/OWB-646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Struberg resolved OWB-646.
-------------------------------

    Resolution: Fixed

There is one remaining issue with tomcat7 but this is not related to OWB. 
In tomcat6 and up to tomcat 7.0.21 the StandartEngineValve was being called before SessionTrackerValve. 
With tc-7.0.22 they changed that around thus the contextDestroyed is being called AFTER the session tracker! In OWB or msm we could only provide a workaround with either an own Valve or a ServletFilter. The cleanest way would of course to fix this in tomcat.
                
> 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