[
https://issues.apache.org/jira/browse/OWB-669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13417327#comment-13417327
]
Pavel Arnošt commented on OWB-669:
----------------------------------
Hi, no, I didn't know that I should do that. Nevertheless, after I have added:
<listener>
<listener-class>org.apache.webbeans.web.failover.FailOverBagWrapper</listener-class>
</listener>
to web.xml, situation is the same. After two redeploys, the session is lost.
Do you think the problem is in a session activation? I think the problem is in
fact that serialized beans are removed from session attribute after first
redeploy and are not passivated before second redeploy.
> Bean fail over is not in sync with specs
> ----------------------------------------
>
> Key: OWB-669
> URL: https://issues.apache.org/jira/browse/OWB-669
> Project: OpenWebBeans
> Issue Type: Bug
> Components: Context and Scopes, Simple Web Beans
> Affects Versions: 1.1.3, 1.1.4
> Environment: Tomcat 7.0.22+, Memcached Session Manager, OWB 1.1.3/4
> Reporter: Thomas Andraschko
> Assignee: Mark Struberg
> Fix For: 1.1.5
>
> Attachments: OWB-669.patch
>
>
> The current fail over logic is not in sync with the servlet specs as
> discussed with mark:
> http://mail-archives.apache.org/mod_mbox/openwebbeans-dev/201204.mbox/%[email protected]%3E
> The fail over logic should be moved from the ServletRequestListener to an
> Filter/Valve.
--
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
