Return-Path: Delivered-To: apmail-axis-c-user-archive@www.apache.org Received: (qmail 85875 invoked from network); 1 Feb 2011 09:53:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 1 Feb 2011 09:53:50 -0000 Received: (qmail 34343 invoked by uid 500); 1 Feb 2011 09:53:50 -0000 Delivered-To: apmail-axis-c-user-archive@axis.apache.org Received: (qmail 34170 invoked by uid 500); 1 Feb 2011 09:53:47 -0000 Mailing-List: contact c-user-help@axis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache AXIS C User List" Delivered-To: mailing list c-user@axis.apache.org Received: (qmail 34157 invoked by uid 99); 1 Feb 2011 09:53:46 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Feb 2011 09:53:46 +0000 X-ASF-Spam-Status: No, hits=-2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_HI,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [194.40.127.85] (HELO C005895.axa.ch) (194.40.127.85) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Feb 2011 09:53:38 +0000 X-IronPort-AV: E=Sophos;i="4.60,409,1291590000"; d="scan'208,217";a="36803507" Received: from c005812.chres1.doleni.net ([194.40.60.24]) by C005895.ch.winterthur.com with ESMTP; 01 Feb 2011 10:43:41 +0100 Received: from c005815.chres1.doleni.net ([194.40.60.9]) by c005812.chres1.doleni.net with Microsoft SMTPSVC(6.0.3790.4675); Tue, 1 Feb 2011 10:53:17 +0100 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CBC1F5.D9B49CEF" X-MimeOLE: Produced By Microsoft Exchange V6.5 Subject: AW: AW: Is there a limit to SOAP message in Axis2c ? Namespace is getting over-written Date: Tue, 1 Feb 2011 10:53:17 +0100 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: AW: Is there a limit to SOAP message in Axis2c ? Namespace is getting over-written Thread-Index: AcvB5v+s0dK2YA4bQfeGSQCZvr5idgADK8Yw References: <817821.17543.qm@web94714.mail.in2.yahoo.com> <578621.63908.qm@web94706.mail.in2.yahoo.com> From: "Stadelmann Josef" To: "Apache AXIS C User List" X-OriginalArrivalTime: 01 Feb 2011 09:53:17.0270 (UTC) FILETIME=[D9A35760:01CBC1F5] X-Virus-Checked: Checked by ClamAV on apache.org ------_=_NextPart_001_01CBC1F5.D9B49CEF Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I was running into a similar issue de-serializing an xml string 90'000 bytes with axis2c/axiom routines. It happened only because I used the wrong size of buffer pointers. I used a 16 bit sized pointer passing my string over to the axis2c/axiom/libxml2 routine and that made axis2c/axiom/libxml2 routines fail. Changing the pointer size to a 23 bit quantity made the same axis2c/axiom/libxml2 routines work perfectly. It was real my own fault. It happened even we know that we can pass only 65536 bytes with a 16 bit pointer. But once on a day, we got from the client more data and then ... peng ... When I changed to 32 bit pointers and then I was able to de-serialize with the same axis2c/axiom/libxml2 parser routines strings longer the 90'000 bytes. =20 Also beware that WCF from MS is not made for large data sizes as well. It0's not in the advertising newspaper, but at some etches said when you run into string length and sizing problems. And WCF routines will definitely raise an exception if your server responses with data nearing the 65536 boundary length size. For that to work, MS .NET WCF speaks about using a streaming transfer mode. But I do not know the equivalent or how to do that in axis2c/axiom/libxml2. Maybe someone better known on the capabilities of an axis2c-engines can help to answer if streaming between client and server and client is supported or not. Alternatively .... MTOM .... And do not forget chunk transfer modes. =20 Now please go and check your pointers involved in passing the buffer to your axis2c/axiom/guththila or libxml2 parsers. How are they defined? =20 Josef =20 =20 =20 Von: Nandika Jayawardana [mailto:jayawark@gmail.com]=20 Gesendet: Dienstag, 1. Februar 2011 09:06 An: Apache AXIS C User List Betreff: Re: AW: Is there a limit to SOAP message in Axis2c ? Namespace is getting over-written =20 You can try out the libxml2 parser as well. If you do not encounter issues, they it has to be a guththila issue. =20 Regards Nandika On Mon, Jan 31, 2011 at 8:55 PM, ramesh Gopal wrote: Hello, I used the tcpmon to see if there was something going wrong. Looks like for POST if the Content-Length < 49324, things work fine. I tried a sample case when the xml response is more than this limit, I run into a malformed xml. can anybody explain this behaviour ? Rgds, Ramesh. --- On Mon, 31/1/11, ramesh Gopal wrote: From: ramesh Gopal Subject: Re: AW: Is there a limit to SOAP message in Axis2c ? Namespace is getting over-written To: "Apache AXIS C User List" Date: Monday, 31 January, 2011, 2:25 PM =20 Hi, I came across a link which said guththila failed to handle when input is more than 16984 bytes or so. Is it possible that a similar problem may occur when the output is more than a certain limit. When I try and print the response value from the function axis2_svc_skel_invoke method, I see that the node is proper. Is there any other layer where the possibility of data being over-written could happen. What could be the reason that the response is invalid ? Ramesh. --- On Wed, 26/1/11, Stadelmann Josef wrote: From: Stadelmann Josef Subject: AW: Is there a limit to SOAP message in Axis2c ? Namespace is getting over-written To: "Apache AXIS C User List" Date: Wednesday, 26 January, 2011, 2:59 PM And your client is one of .NET WCF or is it Axis2/Java or what is it? =20 Be warned -=20 if you have somewhere C Pointers of 16 bit length you can only handle strings with a maximal length of 65536.=20 This is true independent if your serialized data carries body and/or header and body. (especially on C for OpenVMS) =20 Using 32 bit, but better 64 bit C Pointers lifts this limit.=20 But once you i.e. return long strings back to a ASP.NET or MS WCF Client then the Client will start claiming if you approach the 65536 boundary, that it is unable to handle so much data. In this case you should think about transferring in Junks, either by axis2 or by the underlying transport system, and if this still does not help, think about a streaming transfer mode or MTOM. =20 In heterogeneous environments you will see that i.e. a .NET WCF Client is able to send much longer data sizes then 65536 to its axis2 server, but it is just not able to receive a similar long answer. =20 And yes - it will lead to the described problems. Given your response seen is just one which has the expected end dropped. We are not talking about miss formed xml middle in the string. =20 Josef =20 Von: ramesh Gopal [mailto:fatuzorin2001@yahoo.com]=20 Gesendet: Dienstag, 25. Januar 2011 10:15 An: Apache AXIS C User List Betreff: Is there a limit to SOAP message in Axis2c ? Namespace is getting over-written =20 Hello, Is there a maximum limit to SOAP message from Axis2C ? I am returning a response more than 45 K. I see that in my response the opening and closing tags are not the same. =3DA0=3DA0=3DA0 i=3D3D181 dec=3D3D182.81 can somebody explain the reason for this strange behaviour ? Even though I pass the namespace as an argument, why should it use some jun=3D k value ? Ramesh. =20 =20 =20 ------_=_NextPart_001_01CBC1F5.D9B49CEF Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

I was running into a similar  issue de-serializing an xml string = 90'000 bytes with axis2c/axiom routines. It happened only because I used = the wrong size of buffer pointers. I used a 16 bit sized pointer passing = my string over to the axis2c/axiom/libxml2 routine and that made = axis2c/axiom/libxml2 routines fail. Changing the pointer size to a 23 = bit quantity made the same axis2c/axiom/libxml2 routines work perfectly. = It was real my own fault. It happened even we know that we can pass only = 65536 bytes with a 16 bit pointer.  But once on a day, we got from = the client more data and then … peng … When I changed to 32 = bit pointers and then I was able to de-serialize with the same = axis2c/axiom/libxml2 parser routines strings longer the 90'000 = bytes.

 

Also beware that WCF from MS is not made for large data sizes as = well. It0's not in the advertising newspaper, but at some etches said = when you run into string length and sizing problems. And WCF routines = will definitely raise an exception if your server responses with data = nearing the 65536 boundary length size. For that to work, MS .NET WCF = speaks about using a streaming transfer mode. But I do not know the = equivalent or how to do that in axis2c/axiom/libxml2. Maybe someone = better known on the capabilities of an axis2c-engines can help to answer = if streaming between client and server and client is supported or not. = Alternatively …. MTOM …. And do not forget chunk transfer = modes.

 

Now please go and check your pointers involved in passing the buffer = to your axis2c/axiom/guththila or libxml2 parsers. How are they = defined?

 

Josef

 

 

 

Von:<= /b> Nandika = Jayawardana [mailto:jayawark@gmail.com]
Gesendet: Dienstag, = 1. Februar 2011 09:06
An: Apache AXIS C User = List
Betreff: Re: AW: Is there a limit to SOAP message in = Axis2c ? Namespace is getting over-written

 

You can try out the = libxml2 parser as well. If you do not encounter issues, they it has to = be a guththila issue.

 

Regards

Nandika

On Mon, Jan 31, 2011 at 8:55 PM, ramesh = Gopal <fatuzorin2001@yahoo.com> = wrote:



Hello,

I used the tcpmon to see if = there was something going wrong.

Looks like for POST
if the = Content-Length < 49324, things work fine.

I tried a sample = case when the xml response is more than this limit, I run into a = malformed xml.

can anybody explain this behaviour = ?

Rgds,
Ramesh.



--- On Mon, 31/1/11, ramesh = Gopal <fatuzorin2001@yahoo.com> = wrote:


From: ramesh Gopal <fatuzorin2001@yahoo.com>
Subject: Re: AW: Is = there a limit to SOAP message in Axis2c ? Namespace is getting = over-written


To: = "Apache AXIS C User List" <c-user@axis.apache.org>

Date: Monday, 31 January, 2011, 2:25 = PM

 


Hi,

I came across a = link which said guththila failed to handle when input is more than 16984 = bytes or so.
Is it possible that a similar problem may occur when the = output is more than a certain limit.

When I try and print the = response value from the function axis2_svc_skel_invoke method, I see = that the node is proper. Is there any other layer where the possibility = of data being over-written could happen.
What could be the reason = that the response is invalid ?

Ramesh.


--- On Wed, = 26/1/11, Stadelmann Josef <josef.stadelmann@axa-winterthur.ch> = wrote:


From: Stadelmann Josef = <josef.stadelmann@axa-winterthur.ch>
Subject: = AW: Is there a limit to SOAP message in Axis2c ? Namespace is getting = over-written
To: "Apache AXIS C User List" <c-user@axis.apache.org>
Date: Wednesday, 26 = January, 2011, 2:59 PM

An= d your client is one of .NET WCF or is it Axis2/Java or what is = it?

&n= bsp;

Be= warned –

if= you have somewhere C Pointers of 16 bit length you can only handle = strings with a maximal length of  65536.

Th= is is true independent if your serialized data carries body and/or = header and body. (especially on C for OpenVMS)

&n= bsp;

Us= ing 32 bit, but better 64 bit C Pointers lifts this limit.

Bu= t once you i.e. return long strings back to a ASP.NET or MS WCF Client then the Client will = start claiming if you approach the 65536 boundary, that it is unable to = handle so much data. In this case you should think about transferring in = Junks, either by axis2 or by the underlying  transport system, and = if this still does not help, think about a streaming transfer mode or = MTOM.

&n= bsp;

In= heterogeneous environments you will see that i.e. a .NET WCF Client is = able to send much longer data sizes then 65536 to its axis2 server, but = it is just not able to receive a similar long answer.

&n= bsp;

An= d yes – it will lead to the described problems. Given your = response seen is just one which has the expected end dropped. We are not = talking about miss formed xml middle in the string.

&n= bsp;

Jo= sef

&n= bsp;

Von:<= span lang=3DEN-US = style=3D'font-size:10.0pt;font-family:"inherit","serif"'> ramesh Gopal = [mailto:fatuzorin2001@yahoo.com]
Gesendet: = Dienstag, 25. Januar 2011 10:15
An: Apache AXIS C User = List
Betreff:<= span lang=3DDE style=3D'font-size:10.0pt;font-family:"inherit","serif"'> = Is there a limit to SOAP message in Axis2c ? Namespace is getting = over-written

 


Hello,

Is there a maximum limit to SOAP = message from Axis2C ?

I am returning a response more than 45 = K.

I see that in my response the opening and closing tags are not = the = same.

<tns:int_arr_retrec1_char_value>
=3DA0=3DA0=3DA0 = i=3D3D181 = dec=3D3D182.81
</_in:int_arr_retrec1_char_value>

can = somebody explain the reason for this strange behaviour ?

Even = though I pass the namespace as an argument, why should it use some = jun=3D
k value ?

Ramesh.

 

 

 

------_=_NextPart_001_01CBC1F5.D9B49CEF--