[
https://issues.apache.org/jira/browse/WW-4873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Hum updated WW-4873:
----------------------------
Description:
We are attempting to test session replication on our websphere servers but run
into the given error when websphere tries to serialize the session.
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.
was:
We are attempting to test session replication on our websphere servers but run
into the given error when websphere tries to serialize the session.
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 uses the stored value 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.
> 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
>
> We are attempting to test session replication on our websphere servers but
> run into the given error when websphere tries to serialize the session.
> 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)
