You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by Emanuele Benedetti <e....@stanleyint.com> on 2009/03/09 20:18:59 UTC
Message too long
Hi all,
I've written an axis2c service that have one function that get a string as the only parameter. I deployed using axis2 as an apache module.
All work well until the message is under 100K (I don't discovered the exact limit, may be 128K). But when my service receive a message 150K
long the text string parameter appears empty to axiom.
The message that arrive to my service is the following:
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<Receive xmlns="http://xxx.obscuredforprivacy.xxx/axis2/services/Begin">
<updategram>long text string</updategram>
</Receive>
</s:Body>
</s:Envelope>
If the message is long (about 150K) the <updategram> element is empty.
There is some limits to the element size? How to fix it?
Thank you for reading me.
--
Best regards,
Emanuele Benedetti
Head of IT Development
Stanley International Betting Ltd
Re[2]: Message too long
Posted by Emanuele Benedetti <e....@stanleyint.com>.
Hello Manjula,
Thank you for your response. Changing the parser to libxml2 solve the problem. I had to reconfigure axis2 with --enable-libxml2
--disable-guththila options, recompile and reinstall.
Thank you again.
Tuesday, March 10, 2009, 6:52:15 AM, you wrote:
MP> This may be due to a buffer size limit in Guththila XML parser. Please
MP> put a JIRA and send the link.
MP> Can you try this with libxml2 parser instead of guththila. ?
MP> Thanks,
MP> -Manjula.
MP> On Mon, 2009-03-09 at 20:18 +0100, Emanuele Benedetti wrote:
>> Hi all,
>>
>>
>> I've written an axis2c service that have one function that get a string as the only parameter. I deployed using axis2 as an apache module.
>> All work well until the message is under 100K (I don't discovered the exact limit, may be 128K). But when my service receive a message 150K
>> long the text string parameter appears empty to axiom.
>>
>> The message that arrive to my service is the following:
>>
>> <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
>> <s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
>> <Receive xmlns="http://xxx.obscuredforprivacy.xxx/axis2/services/Begin">
>> <updategram>long text string</updategram>
>> </Receive>
>> </s:Body>
>> </s:Envelope>
>>
>> If the message is long (about 150K) the <updategram> element is empty.
>>
>> There is some limits to the element size? How to fix it?
>>
>> Thank you for reading me.
>>
>>
--
Best regards,
Emanuele Benedetti
Head of IT Development
Stanley International Betting Ltd
Re: Message too long
Posted by Manjula Peiris <ma...@wso2.com>.
This may be due to a buffer size limit in Guththila XML parser. Please
put a JIRA and send the link.
Can you try this with libxml2 parser instead of guththila. ?
Thanks,
-Manjula.
On Mon, 2009-03-09 at 20:18 +0100, Emanuele Benedetti wrote:
> Hi all,
>
>
> I've written an axis2c service that have one function that get a string as the only parameter. I deployed using axis2 as an apache module.
> All work well until the message is under 100K (I don't discovered the exact limit, may be 128K). But when my service receive a message 150K
> long the text string parameter appears empty to axiom.
>
> The message that arrive to my service is the following:
>
> <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
> <s:Body xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
> <Receive xmlns="http://xxx.obscuredforprivacy.xxx/axis2/services/Begin">
> <updategram>long text string</updategram>
> </Receive>
> </s:Body>
> </s:Envelope>
>
> If the message is long (about 150K) the <updategram> element is empty.
>
> There is some limits to the element size? How to fix it?
>
> Thank you for reading me.
>
>