You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-user@axis.apache.org by ramesh Gopal <fa...@yahoo.com> on 2011/02/01 06:55:52 UTC
Re: AW: Is there a limit to SOAP message in Axis2c ? Namespace is getting over-written
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 <fa...@yahoo.com> wrote:
From: ramesh Gopal <fa...@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-...@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 <jo...@axa-winterthur.ch> wrote:
From: Stadelmann Josef <jo...@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-...@axis.apache.org>
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? Be warned – if you have somewhere C Pointers of 16 bit length you can only handle strings with a maximal length of 65536. This is true independent if your serialized data carries body and/or header and body. (especially on C for OpenVMS) Using 32 bit, but better 64 bit C Pointers lifts this limit. 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. 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. 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. Josef Von: ramesh Gopal [mailto:fatuzorin2001@yahoo.com]
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
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>
=A0=A0=A0 i=3D181 dec=3D182.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=
k value ?
Ramesh.
AW: AW: Is there a limit to SOAP message in Axis2c ? Namespace is getting over-written
Posted by Stadelmann Josef <jo...@axa-winterthur.ch>.
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: 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 <fa...@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 <fa...@yahoo.com> wrote:
From: ramesh Gopal <fa...@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-...@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
<jo...@axa-winterthur.ch> wrote:
From: Stadelmann Josef <jo...@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-...@axis.apache.org>
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?
Be warned -
if you have somewhere C Pointers of 16 bit length you can only handle
strings with a maximal length of 65536.
This is true independent if your serialized data carries body and/or
header and body. (especially on C for OpenVMS)
Using 32 bit, but better 64 bit C Pointers lifts this limit.
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.
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.
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.
Josef
Von: ramesh Gopal [mailto:fatuzorin2001@yahoo.com]
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
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>
=A0=A0=A0 i=3D181 dec=3D182.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=
k value ?
Ramesh.
Re: AW: Is there a limit to SOAP message in Axis2c ? Namespace is getting over-written
Posted by ramesh Gopal <fa...@yahoo.com>.
Hello,
Earlier I was testing this against Axis 1.5 (when i ran into the issue with a much smaller length).
With Axis2 1.6, the scenario is much better, atleast I dont run into the issue with smaller length. But still I run into an issue beyond a size.
That opens my question again .... for a soap message (no attachments), is there a limit to the size?
Ramesh.
--- On Wed, 2/2/11, ramesh Gopal <fa...@yahoo.com> wrote:
From: ramesh Gopal <fa...@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-...@axis.apache.org>
Date: Wednesday, 2 February, 2011, 10:26 AM
Hello,
This is what I see from stack:
==1030== Invalid read of size 1
==1030== at 0x4006D00: memcpy (mc_replace_strmem.c:406)
==1030== by 0x4037231: guththila_write_token (in /work/deepa/4gl750UC5/AXIS2C/lib/libguththila.so.0.5.0)
==1030== by 0x4037D32: guththila_write_end_element (in /work/deepa/4gl750UC5/AXIS2C/lib/libguththila.so.0.5.0)
==1030==
by 0x402EC20: guththila_xml_writer_wrapper_write_end_element (in
/work/deepa/4gl750UC5/AXIS2C/lib/libaxis2_parser.so.0.5.0)
==1030== by 0x402E579: axiom_xml_writer_write_end_element (in /work/deepa/4gl750UC5/AXIS2C/lib/libaxis2_parser.so.0.5.0)
==1030== by 0x4019C5F: axiom_output_write (in /work/deepa/4gl750UC5/AXIS2C/lib/libaxis2_axiom.so.0.5.0)
==1030== by 0x4017E09: axiom_element_serialize_end_part (in /work/deepa/4gl750UC5/AXIS2C/lib/libaxis2_axiom.so.0.5.0)
==1030== by 0x401523B: axiom_node_serialize (in /work/deepa/4gl750UC5/AXIS2C/lib/libaxis2_axiom.so.0.5.0)
==1030== by 0x4021FF3: axiom_soap_envelope_serialize (in /work/deepa/4gl750UC5/AXIS2C/lib/libaxis2_axiom.so.0.5.0)
==1030== by 0x40CF9C5: axis2_http_transport_sender_invoke (in /work/deepa/4gl750UC5/AXIS2C/lib/libaxis2_http_sender.so.0.5.0)
==1030== by 0x409048D: axis2_engine_send (in
/work/deepa/4gl750UC5/AXIS2C/lib/libaxis2_engine.so.0.5.0)
==1030== by 0x409A004: axis2_msg_recv_receive_impl (in /work/deepa/4gl750UC5/AXIS2C/lib/libaxis2_engine.so.0.5.0)
==1030== Address 0x42066E4 is 4 bytes before a block of size 32,768 alloc'd
==1030== at 0x40053C0: malloc (vg_replace_malloc.c:149)
==1030== by 0x4045CC6: axutil_allocator_malloc_impl (in /work/deepa/4gl750UC5/AXIS2C/lib/libaxutil.so.0.5.0)
==1030== by 0x40373AD: guththila_write_xtoken (in /work/deepa/4gl750UC5/AXIS2C/lib/libguththila.so.0.5.0)
==1030==
by 0x4038D82: guththila_write_start_element_with_prefix_and_namespace
(in /work/deepa/4gl750UC5/AXIS2C/lib/libguththila.so.0.5.0)
==1030==
by 0x402EA36:
guththila_xml_writer_wrapper_write_start_element_with_namespace_prefix
(in /work/deepa/4gl750UC5/AXIS2C/lib/libaxis2_parser.so.0.5.0)
==1030==
by 0x402E50E:
axiom_xml_writer_write_start_element_with_namespace_prefix (in
/work/deepa/4gl750UC5/AXIS2C/lib/libaxis2_parser.so.0.5.0)
==1030== by 0x4019D26: axiom_output_write (in /work/deepa/4gl750UC5/AXIS2C/lib/libaxis2_axiom.so.0.5.0)
==1030== by 0x4017C68: axiom_element_serialize_start_part (in /work/deepa/4gl750UC5/AXIS2C/lib/libaxis2_axiom.so.0.5.0)
==1030== by 0x40151A5: axiom_node_serialize (in /work/deepa/4gl750UC5/AXIS2C/lib/libaxis2_axiom.so.0.5.0)
==1030== by 0x4021FF3: axiom_soap_envelope_serialize (in /work/deepa/4gl750UC5/AXIS2C/lib/libaxis2_axiom.so.0.5.0)
==1030== by 0x40CF9C5: axis2_http_transport_sender_invoke (in /work/deepa/4gl750UC5/AXIS2C/lib/libaxis2_http_sender.so.0.5.0)
Any more suggestions ....
Ramesh.
--- On Tue, 1/2/11, Nandika Jayawardana <ja...@gmail.com> wrote:
From: Nandika Jayawardana <ja...@gmail.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-...@axis.apache.org>
Date: Tuesday, 1 February, 2011, 1:36 PM
You can try out the libxml2 parser as well. If you do not encounter issues, they it has to be a guththila issue.
RegardsNandika
On Mon, Jan 31, 2011 at 8:55 PM, ramesh Gopal <fa...@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 <fa...@yahoo.com> wrote:
From: ramesh Gopal <fa...@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-...@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 <jo...@axa-winterthur.ch> wrote:
From: Stadelmann Josef <jo...@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-...@axis.apache.org>
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?
Be warned – if you have somewhere C Pointers of 16 bit length you can only handle strings with a maximal length of 65536.
This is true independent if your serialized data carries body and/or header and
body. (especially on C for OpenVMS) Using 32 bit, but better 64 bit C Pointers lifts this limit.
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. 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.
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.
Josef
Von: ramesh Gopal [mailto:fatuzorin2001@yahoo.com]
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
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>
=A0=A0=A0 i=3D181 dec=3D182.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=
k value ?
Ramesh.
Re: AW: Is there a limit to SOAP message in Axis2c ? Namespace is getting over-written
Posted by ramesh Gopal <fa...@yahoo.com>.
Hello,
This is what I see from stack:
==1030== Invalid read of size 1
==1030== at 0x4006D00: memcpy (mc_replace_strmem.c:406)
==1030== by 0x4037231: guththila_write_token (in /work/deepa/4gl750UC5/AXIS2C/lib/libguththila.so.0.5.0)
==1030== by 0x4037D32: guththila_write_end_element (in /work/deepa/4gl750UC5/AXIS2C/lib/libguththila.so.0.5.0)
==1030==
by 0x402EC20: guththila_xml_writer_wrapper_write_end_element (in
/work/deepa/4gl750UC5/AXIS2C/lib/libaxis2_parser.so.0.5.0)
==1030== by 0x402E579: axiom_xml_writer_write_end_element (in /work/deepa/4gl750UC5/AXIS2C/lib/libaxis2_parser.so.0.5.0)
==1030== by 0x4019C5F: axiom_output_write (in /work/deepa/4gl750UC5/AXIS2C/lib/libaxis2_axiom.so.0.5.0)
==1030== by 0x4017E09: axiom_element_serialize_end_part (in /work/deepa/4gl750UC5/AXIS2C/lib/libaxis2_axiom.so.0.5.0)
==1030== by 0x401523B: axiom_node_serialize (in /work/deepa/4gl750UC5/AXIS2C/lib/libaxis2_axiom.so.0.5.0)
==1030== by 0x4021FF3: axiom_soap_envelope_serialize (in /work/deepa/4gl750UC5/AXIS2C/lib/libaxis2_axiom.so.0.5.0)
==1030== by 0x40CF9C5: axis2_http_transport_sender_invoke (in /work/deepa/4gl750UC5/AXIS2C/lib/libaxis2_http_sender.so.0.5.0)
==1030== by 0x409048D: axis2_engine_send (in /work/deepa/4gl750UC5/AXIS2C/lib/libaxis2_engine.so.0.5.0)
==1030== by 0x409A004: axis2_msg_recv_receive_impl (in /work/deepa/4gl750UC5/AXIS2C/lib/libaxis2_engine.so.0.5.0)
==1030== Address 0x42066E4 is 4 bytes before a block of size 32,768 alloc'd
==1030== at 0x40053C0: malloc (vg_replace_malloc.c:149)
==1030== by 0x4045CC6: axutil_allocator_malloc_impl (in /work/deepa/4gl750UC5/AXIS2C/lib/libaxutil.so.0.5.0)
==1030== by 0x40373AD: guththila_write_xtoken (in /work/deepa/4gl750UC5/AXIS2C/lib/libguththila.so.0.5.0)
==1030==
by 0x4038D82: guththila_write_start_element_with_prefix_and_namespace
(in /work/deepa/4gl750UC5/AXIS2C/lib/libguththila.so.0.5.0)
==1030==
by 0x402EA36:
guththila_xml_writer_wrapper_write_start_element_with_namespace_prefix
(in /work/deepa/4gl750UC5/AXIS2C/lib/libaxis2_parser.so.0.5.0)
==1030==
by 0x402E50E:
axiom_xml_writer_write_start_element_with_namespace_prefix (in
/work/deepa/4gl750UC5/AXIS2C/lib/libaxis2_parser.so.0.5.0)
==1030== by 0x4019D26: axiom_output_write (in /work/deepa/4gl750UC5/AXIS2C/lib/libaxis2_axiom.so.0.5.0)
==1030== by 0x4017C68: axiom_element_serialize_start_part (in /work/deepa/4gl750UC5/AXIS2C/lib/libaxis2_axiom.so.0.5.0)
==1030== by 0x40151A5: axiom_node_serialize (in /work/deepa/4gl750UC5/AXIS2C/lib/libaxis2_axiom.so.0.5.0)
==1030== by 0x4021FF3: axiom_soap_envelope_serialize (in /work/deepa/4gl750UC5/AXIS2C/lib/libaxis2_axiom.so.0.5.0)
==1030== by 0x40CF9C5: axis2_http_transport_sender_invoke (in /work/deepa/4gl750UC5/AXIS2C/lib/libaxis2_http_sender.so.0.5.0)
Any more suggestions ....
Ramesh.
--- On Tue, 1/2/11, Nandika Jayawardana <ja...@gmail.com> wrote:
From: Nandika Jayawardana <ja...@gmail.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-...@axis.apache.org>
Date: Tuesday, 1 February, 2011, 1:36 PM
You can try out the libxml2 parser as well. If you do not encounter issues, they it has to be a guththila issue.
RegardsNandika
On Mon, Jan 31, 2011 at 8:55 PM, ramesh Gopal <fa...@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 <fa...@yahoo.com> wrote:
From: ramesh Gopal <fa...@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-...@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 <jo...@axa-winterthur.ch> wrote:
From: Stadelmann Josef <jo...@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-...@axis.apache.org>
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?
Be warned – if you have somewhere C Pointers of 16 bit length you can only handle strings with a maximal length of 65536.
This is true independent if your serialized data carries body and/or header and
body. (especially on C for OpenVMS) Using 32 bit, but better 64 bit C Pointers lifts this limit.
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. 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.
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.
Josef
Von: ramesh Gopal [mailto:fatuzorin2001@yahoo.com]
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
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>
=A0=A0=A0 i=3D181 dec=3D182.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=
k value ?
Ramesh.
Re: AW: Is there a limit to SOAP message in Axis2c ? Namespace is
getting over-written
Posted by Nandika Jayawardana <ja...@gmail.com>.
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 <fa...@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 <fa...@yahoo.com>* wrote:
>
>
> From: ramesh Gopal <fa...@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-...@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 <jo...@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-...@axis.apache.org>
> 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?
>
>
>
> Be warned –
>
> if you have somewhere C Pointers of 16 bit length you can only handle
> strings with a maximal length of 65536.
>
> This is true independent if your serialized data carries body and/or header
> and body. (especially on C for OpenVMS)
>
>
>
> Using 32 bit, but better 64 bit C Pointers lifts this limit.
>
> 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.
>
>
>
> 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.
>
>
>
> 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.
>
>
>
> Josef
>
>
>
> *Von:* ramesh Gopal [mailto:fatuzorin2001@yahoo.com]
> *Gesendet:* Dienstag, 25. Januar 2011 10:15
> *An:* Apache AXIS C User List
> *Betr**eff:* 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>
> =A0=A0=A0 i=3D181 dec=3D182.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=
> k value ?
>
> Ramesh.
>
>
>
>
>
>