Re: [jira] [Updated] (WW-4873) NotSerializableException - org.apache.struts2.dispatcher.StrutsRequestWrapper

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Re: [jira] [Updated] (WW-4873) NotSerializableException - org.apache.struts2.dispatcher.StrutsRequestWrapper

Lukasz Lenart
2.5.14.1 will be a fast release, please do not assign any other issues to it.


Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/

2017-11-29 7:42 GMT+01:00 Lukasz Lenart (JIRA) <[hidden email]>:

>
>      [ https://issues.apache.org/jira/browse/WW-4873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Lukasz Lenart updated WW-4873:
> ------------------------------
>     Fix Version/s:     (was: 2.5.14.1)
>                    2.6
>
>> NotSerializableException - org.apache.struts2.dispatcher.StrutsRequestWrapper
>> -----------------------------------------------------------------------------
>>
>>                 Key: WW-4873
>>                 URL: https://issues.apache.org/jira/browse/WW-4873
>>             Project: Struts 2
>>          Issue Type: Bug
>>    Affects Versions: 2.5.13
>>            Reporter: Michael Hum
>>            Assignee: Yasser Zamani
>>             Fix For: 2.6
>>
>>
>> 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= java.io.NotSerializableException: 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
> (v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]