Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id EF334200D48 for ; Wed, 29 Nov 2017 07:40:03 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id EDCC3160C16; Wed, 29 Nov 2017 06:40:03 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 3FFDD160BF6 for ; Wed, 29 Nov 2017 07:40:03 +0100 (CET) Received: (qmail 43992 invoked by uid 500); 29 Nov 2017 06:40:02 -0000 Mailing-List: contact issues-help@struts.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@struts.apache.org Delivered-To: mailing list issues@struts.apache.org Received: (qmail 43981 invoked by uid 99); 29 Nov 2017 06:40:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Nov 2017 06:40:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 9FCA8C3573 for ; Wed, 29 Nov 2017 06:40:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.011 X-Spam-Level: X-Spam-Status: No, score=-99.011 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KB_WAM_FROM_NAME_SINGLEWORD=0.2, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id AXUB8q3SwTWa for ; Wed, 29 Nov 2017 06:40:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id CD2055F21E for ; Wed, 29 Nov 2017 06:40:00 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 62645E05B7 for ; Wed, 29 Nov 2017 06:40:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 2009D2104F for ; Wed, 29 Nov 2017 06:40:00 +0000 (UTC) Date: Wed, 29 Nov 2017 06:40:00 +0000 (UTC) From: "Yasser Zamani (JIRA)" To: issues@struts.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (WW-4873) NotSerializableException - org.apache.struts2.dispatcher.StrutsRequestWrapper MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 29 Nov 2017 06:40:04 -0000 [ https://issues.apache.org/jira/browse/WW-4873?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yasser Zamani updated WW-4873: ------------------------------ Fix Version/s: (was: 2.5.x) 2.5.14.1 > 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.5.14.1 > > > 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)