Mailing-List: contact axis-c-user-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Apache AXIS C User List" <axis-c-user@ws.apache.org>
In-Reply-To: <000101c452e9$740e7a60$0a65a8c0@SusanthaNB>
Subject: RE: Large return message causes Call::UnInitialize to fail
To: "Apache AXIS C User List" <axis-c-user@ws.apache.org>
Message-ID: 
 <OF7F79D4D9.B040A3CA-ON80256EB4.0053B6AB-80256EB4.0053AC9A@uk.ibm.com>
From: Andrew Perry2 <PERRYAN@uk.ibm.com>
Date: Tue, 15 Jun 2004 16:15:29 +0100
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII


The Xerces parser xerces-c_2_2_0.dll

Regards

Andrew Perry


             "Susantha Kumara"                                             
             <susantha@opensou                                             
             rce.lk>                                                    To 
                                       "'Apache AXIS C User List'"         
             15/06/2004 16:00          <axis-c-user@ws.apache.org>         
                                                                        cc 
                                                                           
             Please respond to                                     Subject 
              "Apache AXIS C           RE: Large return message causes     
                User List"             Call::UnInitialize to fail          
                                                                           
                                                                           
What parser do you use ?. Xerces or Expat ?

Susantha
---
> -----Original Message-----
> From: Andrew Perry2 [mailto:PERRYAN@uk.ibm.com]
> Sent: Wednesday, June 09, 2004 5:45 PM
> To: axis-c-user@ws.apache.org
> Subject: Large return message causes Call::UnInitialize to fail
>
>
>
>
> I've got a simple C++ test program which calls a Java web service and
gets
> returned a java String of the specified size. This works for all
messages
> upto a size of 48715 bytes, but anything over this size causes the
"int
> Call::UnInitialize()" routine to fail when it tries to perform a
"delete
> m_pAxisEngine;". The data is received by the client stub and the
> "m_pCall->GetElementAsString" succeeds, but because the
> "Call::UnInitialize()" fails the data does not get returned from the
stub
> to the client. The visual C++ debugger seems to indicate that
> "m_pAxisEngine->UnInitialize();" is not freeing all the m_pAxisEngine
> linked lists correctly.
>
> Is there a fix for this?
>
> Regards
>
> Andrew Perry