[jboss-jira] [JBoss JIRA] (WFLY-3502) Handle session attribute serialization incompatiblities

[Paul Ferraro (JIRA)]

    [ https://issues.jboss.org/browse/WFLY-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13032254#comment-13032254 ] 

Paul Ferraro commented on WFLY-3502:
------------------------------------

I think it is sufficient for now to invalidate sessions whose serialized form is not compatible with the current class definition.  We can always make this behavior configurable later.

> Handle session attribute serialization incompatiblities
> -------------------------------------------------------
>
>                 Key: WFLY-3502
>                 URL: https://issues.jboss.org/browse/WFLY-3502
>             Project: WildFly
>          Issue Type: Feature Request
>          Components: Clustering
>    Affects Versions: 8.1.0.Final
>            Reporter: Paul Ferraro
>            Assignee: Paul Ferraro
>
> When a new release of a web application is deployed to an existing cluster, any changes to the object placed in the web session can cause serialization incompatibilities.  To handle this cleanly, we typically recommend that users leverage isolated cluster and mod_cluster load balancing groups (or mod_jk domains) to transition users to the new version of an application.
> For simple applications, this might be overkill.  It might be acceptable/preferable to create a new session in the event of a serialization incompatibility, rather than failing the request.  We should allow developers to configure this behavior per-application.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)