Hi Paul,
Thanks for helping me through this.
I am not caching the message ... I have 2 GB of RAM. Do I really have to use
AXIOM OMElement? How can I ensure that MTOM is truely enabled ? I am able to
upload small data but with large data, this is what I see now at the client end
after tweaking the code some more :
[java] Exception in thread "main" org.apache.axis2.AxisFault: unknown
[java] at
org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:434)
[java] at
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:373)
[java] at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:294)
[java] at
sample.mtom.service.MTOMSampleMTOMSampleSOAP11Port_httpStub.attachment(Unknown
Source)
[java] at sample.mtom.client.Client.main(Unknown Source)
[java] Java Result: 1
Thanks tons
Chris
Paul Fremantle <[EMAIL PROTECTED]> wrote:
Chris
Are you following the code for caching the message? If you are pulling
it into a byte[] then it will still use 200Mb of memory.
Paul
On 6/14/07, Chris Shah wrote:
> I can see the following on my client :
>
> Exception in thread "main" java.lang.OutOfMemoryError: Java heap space
>
> Does this mean that MTOM is really not enabled ? Otherwise why would client
> run out of space ?
>
> Thanks for your help
>
> Chris
>
> Chris Shah wrote:
>
>
> I tried returning a response object consisting of an "xsd:string" and
> "xmime:base64Binary".
> basically just switched the request and response object types in the sample.
> Then I implemented the client and service code accordingly, and set
> enableMTOM in axis2.xml t true.
>
> I can download small files using the client. Large files give me the error
> below.
>
> Is it necessary to return an OMElement or a byte[]? Why will a base64Binary
> object not work? Why does it work then while uploading to the service and
> not while downloading ?
>
> Thanks for your help
> Chris
>
>
>
> Exception in thread "HttpConnection-8080-1" java.lang.IllegalStateException:
> Response already committed
> at
> org.apache.axis2.transport.http.server.AxisHttpResponseImpl.assertNotCommitted(AxisHttpResponseImpl.
> at
> org.apache.axis2.transport.http.server.AxisHttpResponseImpl.sendError(AxisHttpResponseImpl.java:120)
> at
> org.apache.axis2.transport.http.server.AxisHttpService.doService(AxisHttpService.java:297)
> at
> org.apache.axis2.transport.http.server.AxisHttpService.handleRequest(AxisHttpService.java:184)
> at
> org.apache.axis2.transport.http.server.HttpServiceProcessor.run(HttpServiceProcessor.java:74)
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.
> at
> edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java
> at java.lang.Thread.run(Thread.java:595)
>
>
>
> Paul Fremantle
wrote:
> Chris
>
> Simply define a service that returns an OMElement (like the sample) or a
> byte[]
> It works in exactly the same way.
>
> Paul
>
> On 6/14/07, Chris Shah wrote:
> > I could successfully run the sample MTOM code in AXIS 2 installation to
> > upload large file ~ 200 MB.
> > What should I do to be able to download it from the service. Is there a
> > sample wsdl I cna look at somewhere ?
> >
> > Any pointers ?
> >
> > thx
> > Chris
> >
> > Paul Fremantle wrote:
> > Chris
> >
> > You should use the MTOM capability of Axis2. AFAIK Axis1 cannot cope
> > with 200Mb files.
> >
> > The Axis2 design allows streaming of large files.
> > See this guide:
> > http://ws.apache.org/axis2/1_2/mtom-guide.html
> >
> > Paul
> >
> > On 6/13/07, Chris Shah wrote:
> > > Hello,
> > >
> > > I am writing a WS specification for my service . What is the best way to
> > > expose zipped text files of size around 200 MB ( not more ) through this
> > > service ?
> > >
> > > Thanks
> > > Chris
> > >
> > > ________________________________
> > > Boardwalk for $500? In 2007? Ha!
> > > Play Monopoly Here and Now (it's updated for today's economy) at Yahoo!
> > > Games.
> > >
> > >
> >
> >
> > --
> > Paul Fremantle
> > Co-Founder and VP of Technical Sales, WSO2
> > OASIS WS-RX TC Co-chair
> >
> > blog: http://pzf.fremantle.org
> > [EMAIL PROTECTED]
> >
> > "Oxygenating the Web Service Platform", www.wso2.com
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> >
> >
> > ________________________________
> > Don't get soaked. Take a quick peak at the forecast
> > with theYahoo! Search weather shortcut.
> >
> >
>
>
> --
> Paul Fremantle
> Co-Founder and VP of Technical Sales, WSO2
> OASIS WS-RX TC Co-chair
>
> blog: http://pzf.fremantle.org
> [EMAIL PROTECTED]
>
> "Oxygenating the Web Service Platform", www.wso2.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
> ________________________________
> Finding fabulous fares is fun.
> Let Yahoo! FareChase search your favorite travel sites to find flight and
> hotel bargains.
>
>
> ________________________________
> We won't tell. Get more on shows you hate to love
> (and love to hate): Yahoo! TV's Guilty Pleasures list.
>
>
--
Paul Fremantle
Co-Founder and VP of Technical Sales, WSO2
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
[EMAIL PROTECTED]
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------
Park yourself in front of a world of choices in alternative vehicles.
Visit the Yahoo! Auto Green Center.
