[
https://issues.apache.org/jira/browse/OWB-646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13243596#comment-13243596
]
Mark Struberg commented on OWB-646:
-----------------------------------
oki, false positive I fear. It seems that all the OWB SessionContext
information gets correctly put into the HttpSession, but the serialisation nor
Externalisation doesn't get called. I fear there is something different in
tomcat7. Restoring the Session seems ok, but saving the Session to the
memcached now happens way before OWB gets the requestDestroyed callback. This
is different in tomcat6 though...
> 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
