Return-Path: Delivered-To: apmail-jakarta-commons-user-archive@www.apache.org Received: (qmail 45331 invoked from network); 30 Jan 2007 20:26:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 Jan 2007 20:26:56 -0000 Received: (qmail 57866 invoked by uid 500); 30 Jan 2007 20:26:53 -0000 Delivered-To: apmail-jakarta-commons-user-archive@jakarta.apache.org Received: (qmail 57808 invoked by uid 500); 30 Jan 2007 20:26:53 -0000 Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Jakarta Commons Users List" Reply-To: "Jakarta Commons Users List" Delivered-To: mailing list commons-user@jakarta.apache.org Received: (qmail 57692 invoked by uid 99); 30 Jan 2007 20:26:52 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Jan 2007 12:26:52 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of david@davidkarlsen.com designates 217.13.8.30 as permitted sender) Received: from [217.13.8.30] (HELO main.davidkarlsen.com) (217.13.8.30) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 30 Jan 2007 12:26:43 -0800 Received: from localhost (localhost [127.0.0.1]) by main.davidkarlsen.com (Postfix) with ESMTP id 77C8964270 for ; Tue, 30 Jan 2007 21:26:21 +0100 (CET) Received: from main.davidkarlsen.com ([127.0.0.1]) by localhost (sunshine [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 20596-01 for ; Tue, 30 Jan 2007 21:26:09 +0100 (CET) Received: from [127.0.0.1] (unknown [192.168.3.51]) by main.davidkarlsen.com (Postfix) with ESMTP id 32AA763B05 for ; Tue, 30 Jan 2007 21:26:09 +0100 (CET) Message-ID: <45BFA9E0.6040900@davidkarlsen.com> Date: Tue, 30 Jan 2007 21:26:08 +0100 From: "David J. M. Karlsen" User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: Jakarta Commons Users List Subject: Re: Weird serialization error with NestableDelegate References: <45B919F4.4020802@davidkarlsen.com> <31cc37360701291622y3c633b8cgaf7efe1b19890883@mail.gmail.com> In-Reply-To: <31cc37360701291622y3c633b8cgaf7efe1b19890883@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at davidkarlsen.com X-Virus-Checked: Checked by ClamAV on apache.org Henri Yandell wrote: > On 1/25/07, David J. M. Karlsen wrote: >> I'm calling an EJB on a WebSphere 5.0.2.x server from a WebSphere 6.1, >> which is throwing (serverside) an Exception which is extending >> NestableRuntimeException. >> I'm using commons-lang 2.1 on both sides. >> >> All Serializable classes involved (in my app) declare serializationUID >> constants. >> >> Still, I get this serialization error: >> >> org.omg.CORBA.MARSHAL: Unable to read value from underlying bridge : >> Mismatched serialization UIDs : Source (RepId >> RMI:org.apache.commons.lang.exception.NestableDelegate:4F998DA78EFC2530:EAEF728564560A6A) >> >> = EAEF728564560A6A whereas Target (RepId >> RMI:org.apache.commons.lang.exception.NestableDelegate:4F998DA78EFC2530:F68F1455DDEE96BB) >> >> = F68F1455DDEE96BB vmcid: IBM minor code: 89A completed: No >> at >> com.ibm.rmi.iiop.CDRInputStream.read_value(CDRInputStream.java:2105) >> >> I've checked the websphere environment - and it does not seem to include >> any of the commons-lang classes. >> >> Have anybody else experienced this? > > Just this issue a couple of days ago: > https://issues.apache.org/jira/browse/DBUTILS-36 > > "For instance, IBM JVM 1.4.1 has a different way of calculating > serialVersionUID for Serializable class that does not have > serialVersionUID defined than JVM 5.0." > > Do you have different VMs at each end? Yes - this is the underlying problem - as the computed (due to no explicit serial uid defined) serializationID on both sides differ. The solutions are: 1) Deploy the applications on the same JDK level (thus computing the same serial uid) 2) Upgrade to commons-lang 2.2 which declares serial uids (at least for these classes/what hits me - haven't checked all). I'll guess 2) will break compability with clients using commons lang < 2.2, but when the upgrade is complete the problem should disappear "for ever" (until possible changes will force a change of serial uid, which is probably not likely in the 2.x series). -- David J. M. Karlsen - +47 90 68 22 43 http://www.davidkarlsen.com http://mp3.davidkarlsen.com --------------------------------------------------------------------- To unsubscribe, e-mail: commons-user-unsubscribe@jakarta.apache.org For additional commands, e-mail: commons-user-help@jakarta.apache.org