Return-Path: Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org Received: (qmail 35438 invoked by uid 500); 25 Sep 2002 18:52:51 -0000 Mailing-List: contact axis-dev-help@xml.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@xml.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@xml.apache.org Received: (qmail 35425 invoked from network); 25 Sep 2002 18:52:51 -0000 Date: 25 Sep 2002 18:53:16 -0000 Message-ID: <20020925185316.10687.qmail@nagoya.betaversion.org> From: bugzilla@apache.org To: axis-dev@xml.apache.org Cc: Subject: DO NOT REPLY [Bug 12741] - Multithreaded Axis client causes serialization exceptions in Axis service X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12741 Multithreaded Axis client causes serialization exceptions in Axis service ------- Additional Comments From avolanis@rsasecurity.com 2002-09-25 18:53 ------- I got latest as of noon today and the result is still 5 rounds per second. I replaced the BaseSerializerFactory.java and BaseDeserializerFactory.java with the copies from 9/17/2002 with the synchronized keyword added to getSerializerAs/getDeserializerAs and the performance goes to 15 rounds per second. All other parameters of the test have remained the same. I think this is a serious performance degradation.