Return-Path: Delivered-To: apmail-ws-axis-user-archive@www.apache.org Received: (qmail 75551 invoked from network); 11 Aug 2004 23:39:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 11 Aug 2004 23:39:44 -0000 Received: (qmail 29526 invoked by uid 500); 11 Aug 2004 23:39:03 -0000 Delivered-To: apmail-ws-axis-user-archive@ws.apache.org Received: (qmail 29505 invoked by uid 500); 11 Aug 2004 23:39:02 -0000 Mailing-List: contact axis-user-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-user@ws.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-user@ws.apache.org Received: (qmail 29494 invoked by uid 99); 11 Aug 2004 23:39:02 -0000 X-ASF-Spam-Status: No, hits=0.3 required=10.0 tests=DNS_FROM_RFC_ABUSE,HTML_50_60,HTML_MESSAGE,MIME_HTML_NO_CHARSET X-Spam-Check-By: apache.org Received: from [140.194.245.23] (HELO dms-lcc-cpc-m4.dms.usace.army.mil) (140.194.245.23) by apache.org (qpsmtpd/0.27.1) with ESMTP; Wed, 11 Aug 2004 16:38:59 -0700 Received: by dms-lcc-cpc-m4.dms.usace.army.mil with Internet Mail Service (5.5.2657.72) id ; Wed, 11 Aug 2004 18:38:57 -0500 Message-ID: From: "Zwicky, William R ERDC-CERL-IL Contractor" To: "'axis-user@ws.apache.org'" Subject: invokeOneWay is not isolating parameter objects? Date: Wed, 11 Aug 2004 18:38:37 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C47FFC.52D994B6" X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C47FFC.52D994B6 Content-Type: text/plain I have a client that effectively calls: stub.invokeOneWay( new Object[] { "job_1" } ); stub.invokeOneWay( new Object[] { "job_2" } ); stub.invokeOneWay( new Object[] { "job_3" } ); But that's not what the server is receiving. Under Axis 1.1, the server sees: method( "job_3" ); method( "job_3" ); method( "job_3" ); In other words, all three calls have the same parameter. This seems to be time-based; if I single-step the client in the debugger, then the three messages are fine. They're only mangled when running full speed. Even worse, the latest 1.2 beta doesn't deliver all the messages, and produces strange exceptions. First run produced two copies of method("job_2") and exceptions, second run produced one message followed by "stream closed" exceptions. Any idea what's going on? -Bill // William R. Zwicky // USA-CERL (217) 352-6511 x7405 // Champaign, IL ------_=_NextPart_001_01C47FFC.52D994B6 Content-Type: text/html Content-Transfer-Encoding: quoted-printable invokeOneWay is not isolating parameter objects?

I have a client that effectively = calls:
stub.invokeOneWay( new Object[] { = "job_1" } );
stub.invokeOneWay( new Object[] { = "job_2" } );
stub.invokeOneWay( new Object[] { = "job_3" } );

But that's not what the server is = receiving.  Under Axis 1.1, the server sees:
method( "job_3" );
method( "job_3" );
method( "job_3" );

In other words, all three calls have = the same parameter.  This seems to be time-based; if I single-step = the client in the debugger, then the three messages are fine.  = They're only mangled when running full speed.

Even worse, the latest 1.2 beta = doesn't deliver all the messages, and produces strange = exceptions.  First run produced two copies of = method("job_2") and exceptions, second run produced one = message followed by "stream closed" exceptions.

Any idea what's going on?

-Bill

// William R. Zwicky
// USA-CERL  (217) = 352-6511 x7405
// Champaign, IL


------_=_NextPart_001_01C47FFC.52D994B6--