You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by "Pavel Arnošt (JIRA)" <ji...@apache.org> on 2012/07/18 09:54:34 UTC
[jira] [Commented] (OWB-669) Bean fail over is not in sync with
specs
[ https://issues.apache.org/jira/browse/OWB-669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13416929#comment-13416929 ]
Pavel Arnošt commented on OWB-669:
----------------------------------
Hi,
I'm using FailOverFilter from Thomas's patch and session passivation works quite well on Tomcat 7.0.29. But in DefaultOwbFailOverService.restoreBeans method I found "session.removeAttribute(getFailOverAttributeName());" call after beans are restored - what's the purpose of that? Because now, when sessions are passivated in Filter, when I reload/restart Tomcat two times, I lost all sessions if I don't "refresh" (passivate) them with HTTP requests.
Regards,
Pavel
> 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/%3C1335357714.89803.YahooMailNeo@web171502.mail.ir2.yahoo.com%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