struts-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yasser Zamani (JIRA)" <>
Subject [jira] [Comment Edited] (WW-4873) NotSerializableException - org.apache.struts2.dispatcher.StrutsRequestWrapper
Date Fri, 10 Nov 2017 07:50:00 GMT


Yasser Zamani edited comment on WW-4873 at 11/10/17 7:49 AM:

[~MichaelHum], As a workaround until the resolution, I think you can {{ActionContext.getContext().getSession().remove("org.apache.struts2.util.InvocationSessionStore.invocationMap")}}
before your serialization :) or save it in a temp var, remove, serialize then put back it
from that temp var.

was (Author: yasser.zamani):
[~MichaelHum], As a workaround until the resolution, I think you can {{ActionContext.getContext().getSession().remove("org.apache.struts2.util.InvocationSessionStore.invocationMap")}}
before your serialization :)

> NotSerializableException - org.apache.struts2.dispatcher.StrutsRequestWrapper
> -----------------------------------------------------------------------------
>                 Key: WW-4873
>                 URL:
>             Project: Struts 2
>          Issue Type: Bug
>    Affects Versions: 2.5.13
>            Reporter: Michael Hum
>             Fix For: 2.5.x
> We are attempting to test session replication on our websphere servers but run into the
given error when websphere tries to serialize the session. 
> {code}
> [10/18/17 10:33:38:094 EDT] 00000335 WASSession    E MTMBuffWrapper getBytes write object
exception. e= org.apache.struts2.dispatcher.StrutsRequestWrapper
> {code}
> It appears the ActionInvocation stores the ActionContext which stores the offending property:
com.opensymphony.xwork2.dispatcher.HttpServletRequest --> StrutsRequestWrapper 
> After a little digging we narrowed it down to our use of the TokenSessionStoreInterceptor
which stores the value in the session and uses it to redirect the failed request to the original
one. Is this intended/expected? Or is there no requirement that the contents in the session
be serializable - in which case we would have to look to our own solution.

This message was sent by Atlassian JIRA

View raw message