Return-Path: Delivered-To: apmail-xml-axis-dev-archive@xml.apache.org Received: (qmail 1148 invoked by uid 500); 26 Sep 2002 14:38:38 -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 1138 invoked from network); 26 Sep 2002 14:38:37 -0000 Date: 26 Sep 2002 14:39:16 -0000 Message-ID: <20020926143916.10521.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-26 14:39 ------- That is it. Your last changes made the performance the same as my original simple fix with the synchronized keyword. I believe you also hit the problem at its root. One time class initialization type operations are best done in the constructor as opposed in runtime calls with synchronized guarded blocks of code. Thank you for giving this the attention it deserves. I would have hated to see Axis go to its first release with such a performance problem (it was one of the goals of the projecy after all). I wish I had more spare time to do more meaningful contributions besides testing high volume applications. Thanks again.