[jboss-jira] [JBoss JIRA] (WFLY-3502) Create pluggable strategy for dealing with serialization incompatiblities

[Radoslav Husar (JIRA)]

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

Radoslav Husar commented on WFLY-3502:
--------------------------------------

Good approach. However, we need to ensure, that developers do not accidentally overlook their wrong implementation of deserialization of their session objects in case we were to silently proceed. A per-session warning log with session ID seems good to me. Possibly using the pattern of logging the accompanying stack trace (which is quite useful in this case to see which objects and fields failed) to the debug log.

> Create pluggable strategy for dealing with serialization incompatiblities
> -------------------------------------------------------------------------
>
>                 Key: WFLY-3502
>                 URL: https://issues.jboss.org/browse/WFLY-3502
>             Project: WildFly
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          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.2.6#6264)