You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2018/04/30 08:12:00 UTC

[jira] [Closed] (FELIX-5814) Unstable service id should not be used for session attribute names

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

Carsten Ziegeler closed FELIX-5814.
-----------------------------------

> Unstable service id should not be used for session attribute names
> ------------------------------------------------------------------
>
>                 Key: FELIX-5814
>                 URL: https://issues.apache.org/jira/browse/FELIX-5814
>             Project: Felix
>          Issue Type: Bug
>          Components: HTTP Service
>    Affects Versions: http.base-3.0.18, http.jetty-3.4.8, http.bridge-3.0.18
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>            Priority: Major
>             Fix For: http.base-4.0.0, http.jetty-4.0.0, http.bridge-4.0.0
>
>
> To support mulitple inner servlet contexts within the context provided by the container and separate sesssion for each of these contexts, currently the service id of the registered servlet context (ServletContextHelper) is used as part of the key to form the session attribute name.
> If running in a clustered setup with some kind of session replication, the other nodes in the cluster might have different service ids for the same context. Therefore such an approach fails in this setup.
> We should use the context name which is stable.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)