axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thilina Gunarathne" <cset...@gmail.com>
Subject Re: Out Of Memory issue in axis2 1.4
Date Tue, 12 Aug 2008 02:49:25 GMT
Glad to know it's working.. You can go to
https://issues.apache.org/jira/browse/AXIS2 and create a new issues... You
might need to create account...

Also keep in mind that u'r service side logic may be vulnerable to fail when
presented with a large attachment.

thanks,
Thilina

On Mon, Aug 11, 2008 at 4:58 PM, Shehan Simen <ssimen@itree.com.au> wrote:

>  Hi Thilina,
>
> Yes it is working if I use xsd:base64Binary rather than a simple type. So
> this is an issue to fix. Sorry, I am not sure how to log it in JIRA.
>
> If it is easy, could you please log it or let me know how to do it.
>
>
>
> Thank you for your help so far. Otherwise I will be stuck here forever.
>
>
>
> Regards,
>
> simen
>
>
>
> *From:* Thilina Gunarathne [mailto:csethil@gmail.com]
> *Sent:* Monday, 11 August 2008 5:56 PM
>
> *To:* axis-user@ws.apache.org
> *Subject:* Re: Out Of Memory issue in axis2 1.4
>
>
>
> Hi,
> I'm not sure whether ADB will work for simple type restriction on ADB. Can
> you change it to simply a xsd:base64Binary element and see whether it'll
> work. You can have a look at the wsdl given in  Axis2 MTOM guide to get an
> idea.
>
> If that works, please log a JIRA for the simple type restriction issue.
>
> thanks,
> Thilina
>
> On Sun, Aug 10, 2008 at 10:52 PM, Shehan Simen <ssimen@itree.com.au>
> wrote:
>
> Hi Thilina,
>
> I am using ADB. The client and server are generated using wsdl2java eclipse
> plugin. Both using ADB.
>
> This is the part related to my wsdl.
>
>
>
> *-* <http://scania.itree.com.au:8080/axis2/services/SchemesService?wsdl>
> <<xs:simpleType name="*FileRawDataType*">
>
> *-* <http://scania.itree.com.au:8080/axis2/services/SchemesService?wsdl> <
>   <xs:restriction base="*xs:base64Binary*">
>
> * * <        <xs:maxLength value="*5242880*" />
>
> * *   </xs:restriction>
>
> * *</xs:simpleType>
>
>
>
>   Can you figure out the issue?
>
>
>
>    Thanks.
>
>    Regards,
>
>     ssimen
>
>
>
>
>
> *From:* Thilina Gunarathne [mailto:csethil@gmail.com]
> *Sent:* Monday, 11 August 2008 3:35 PM
>
>
> *To:* axis-user@ws.apache.org
> *Subject:* Re: Out Of Memory issue in axis2 1.4
>
>
>
> Hi,
> Can u explain a bit about ur client side... Which data binding framework r
> u using?.. Does ur WSDL have any xsd:base64Binary elements.
>
> thanks,
> ~Thilina
>
> On Sun, Aug 10, 2008 at 10:22 PM, Shehan Simen <ssimen@itree.com.au>
> wrote:
>
> Hi Thilina,
>
> I looked the tcpmon and confirm that it is inside the body. But still I
> Can't understand why it is sending the attachment inside the soap body.
>
> I followed the http://wso2.org/library/264 to send attachments using MTOM
>
>
>
> Reading to the OMElement can be overcome by increasing the heap memory size
> of the tomcat server. But the fundamental question still remains, that is
> why the attachment is going inside the soap body? I tried almost everything
> to send it as an mtom attachment.
>
> Much appreciate your help.
>
>
>
> Thank you.
>
>
>
> Regards,
>
> ssimen
>
>
>
>
>
> *From:* Thilina Gunarathne [mailto:csethil@gmail.com]
> *Sent:* Monday, 11 August 2008 3:14 PM
>
>
> *To:* axis-user@ws.apache.org
> *Subject:* Re: Out Of Memory issue in axis2 1.4
>
>
>
> Hi,
>
>  Yes, it is sending inside the soap body rather than an attachment. Why it
> is going inside the soap body? I changed all the required changes to send it
> as separate attachment.
>
> (stub._getServiceClient().getOptions().setProperty(
>
>                               Constants.Configuration.*ENABLE_MTOM*,
> Constants.*VALUE_TRUE*);)
>
>
>
> Next question is, eventhough it is sending inside the soap bosy, what the
> problem of it? Is there any size limitation to the soap message?
>
>  It's the JVM heap size... The message get's loaded in to the memory with
> added base64 overhead.  Did you check the message using TCPMON or are you
> referring to the message you see in the database..
>
>  I am reading the whole request to the OMElement to save it in the
> database.
>
> Is that the problem?
>
> How can I fix it? Please help me.
>
>  You can fix it by sending the binary data as an attachment.. But even the
> cached attachment will get loaded to the memory if you are reading the whole
> request to an OMElement and writing it to the database. You will need to
> specially handle the cached binary data file..
>
> thanks,
> Thilina
>
>
>
> Thank you.
>
> Regards,
>
> Simen
>
>
>
> *From:* Thilina Gunarathne [mailto:csethil@gmail.com]
> *Sent:* Monday, 11 August 2008 2:01 PM
> *To:* axis-user@ws.apache.org
> *Subject:* Re: Out Of Memory issue in axis2 1.4
>
>
>
>  Can anyone please help me? Whats wrong with axis2?
>
>  It can be two things...
> 1. Attachment may be going inline with base64 encoding, rather than as an
> attachment. Check the message using tcpmon.(
> http://ws.apache.org/commons/tcpmon)
> 2. Your service implementation might be loading the whole cached binary
> data to the memory..
>
> thanks,
> Thilina
>
>
>
>   Thank you.
>
>
>
> Regards
>
>
>
>
>
>
> --
> Thilina Gunarathne - http://thilinag.blogspot.com
>
>
>
>
> --
> Thilina Gunarathne - http://thilinag.blogspot.com
>
>
>
>
> --
> Thilina Gunarathne - http://thilinag.blogspot.com
>
>
>
>
> --
> Thilina Gunarathne - http://thilinag.blogspot.com
>



-- 
Thilina Gunarathne - http://thilinag.blogspot.com

Mime
View raw message