Return-Path: X-Original-To: apmail-ignite-user-archive@minotaur.apache.org Delivered-To: apmail-ignite-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 51ADD1861B for ; Thu, 9 Jul 2015 18:00:37 +0000 (UTC) Received: (qmail 14384 invoked by uid 500); 9 Jul 2015 18:00:37 -0000 Delivered-To: apmail-ignite-user-archive@ignite.apache.org Received: (qmail 14347 invoked by uid 500); 9 Jul 2015 18:00:37 -0000 Mailing-List: contact user-help@ignite.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@ignite.incubator.apache.org Delivered-To: mailing list user@ignite.incubator.apache.org Received: (qmail 14337 invoked by uid 99); 9 Jul 2015 18:00:37 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Jul 2015 18:00:37 +0000 X-ASF-Spam-Status: No, hits=1.0 required=5.0 tests=SPF_SOFTFAIL X-Spam-Check-By: apache.org Received-SPF: softfail (nike.apache.org: transitioning domain of iderzand@gmail.com does not designate 162.253.133.15 as permitted sender) Received: from [162.253.133.15] (HELO mbob.nabble.com) (162.253.133.15) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 09 Jul 2015 17:58:23 +0000 Received: from malf.nabble.com (unknown [162.253.133.59]) by mbob.nabble.com (Postfix) with ESMTP id C1FED10CAB28 for ; Thu, 9 Jul 2015 11:00:09 -0700 (PDT) Date: Thu, 9 Jul 2015 10:55:42 -0700 (PDT) From: zandider To: user@ignite.incubator.apache.org Message-ID: <1436464542399-626.post@n6.nabble.com> Subject: Serialization Exceptions - OptimizedMarshaller not being used MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Just recently upgraded to gridgain community fabric 1.1.4 (from 1.0.6), and now am getting exceptions that certain objects we're storing in the grid are not marked as Serializable. Investigating further, it seems that the exception is stemming from JdkMarshaller, whereas our config files have always specified OoptimizedMarshaller, with requireSerializable set to false. I've verified that our grid config files haven't changed, and that they're being used to start the grid. Has there been an issue introduced loading the OptimizedMarshaller? I can supply stack traces and files privately as needed. XML config file snippet ... .... -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Serialization-Exceptions-OptimizedMarshaller-not-being-used-tp626.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.