You are viewing a plain text version of this content. The canonical link for it is here.

Posted to java-user@axis.apache.org by Sharmin Choksey <Sh...@Sun.COM> on 2002/09/11 03:43:34 UTC

Re: Object serialization in Axis implementation.

The current architecture implementation runs on iAS 6.5, SOAP 2.2
with multiple KJS (JVMs) load balanced in one instance.

-Sharmin. 


>Date: Tue, 10 Sep 2002 18:22:43 -0700 (PDT)
>From: Sharmin Choksey <Sh...@sun.com>
>Subject: Object serialization in Axis implementation.
>To: axis-user@xml.apache.org
>Cc: tara.raghu@sun.com, latha.krishna@sun.com, sharmin.choksey@sun.com
>MIME-Version: 1.0
>Content-MD5: N0VfMMoGv60Py+7YmeBZtQ==
>
>Hi,
>
>The question is related to using Axis to make stateful session
>calls (akin to setHTTPConnection.setMaintainSession(true)).
>
>Does the implementation of Axis allow the objects to be
>serialized across processes to make them distributable for
>failover.  This is definitely an issue with Apache SOAP 2.2
>whose implementation uses objects that cannot be serialized and
>inturn distributable for failover/load balancing.  Appears 
>to put an architectural limitation on how applications can implement
>session failover if the session information cannot be serialized to
>another process/JVM/instance of an app server.
>
>Any pointers to an alternate solution is highly appreciated.
>
>Thanks in advance,
>Sharmin.
>