You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-user@xml.apache.org by Apostolopoulos Paris <pa...@freemail.gr> on 2002/10/27 22:59:15 UTC
A question about SOAP with attachments!
Hi!
I quite new to SOAP , I want to know , from your experience is there any
limitation about the capacity of data tha can be carried out in a SOAP
envelope as an attachement.In the specs it says something like an image
or a document (MIME attachements) but is it efficient to attach lets say
a 50MB file?
For those that are going to scream with that (sorry guys and girls) but
I am just wondering if I could use SOAP with attachments in my
Server-Client application that talk using Message style SOAP , and their
main functionality actually is file transfer!
Thank you for your time
Apostolopoulos Paris
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: A question about SOAP with attachments!
Posted by Scott Nichol <sn...@scottnichol.com>.
I believe you have received excellent advice on this. Apache SOAP does
create one or more in-memory images of the entire SOAP envelope, so the
maximum heap size you've allowed your JVM (and, ultimately, the amount
of virtual memory on your machine) will limit the size of attachment you
can send. If you want to send document that are larger than half
(assuming Apache SOAP creates 2 copies) the virtual memory of your
mechine, Apache SOAP is not the SOAP implementation to prefer.
While you are considering attachments, you should be aware that there
are interoperability issues, if that is of concern to you. As a
specific example, Microsoft's SOAP Toolkit only supports DIME
attachments (not MIME), while Apache SOAP supports only MIME attachments
(not DIME).
Scott Nichol
----- Original Message -----
From: "Apostolopoulos Paris" <pa...@freemail.gr>
To: <so...@xml.apache.org>
Sent: Sunday, October 27, 2002 4:59 PM
Subject: A question about SOAP with attachments!
> Hi!
>
> I quite new to SOAP , I want to know , from your experience is there
any
> limitation about the capacity of data tha can be carried out in a SOAP
> envelope as an attachement.In the specs it says something like an
image
> or a document (MIME attachements) but is it efficient to attach lets
say
> a 50MB file?
> For those that are going to scream with that (sorry guys and girls)
but
> I am just wondering if I could use SOAP with attachments in my
> Server-Client application that talk using Message style SOAP , and
their
> main functionality actually is file transfer!
>
> Thank you for your time
> Apostolopoulos Paris
>
>
>
> --
> To unsubscribe, e-mail:
<ma...@xml.apache.org>
> For additional commands, e-mail:
<ma...@xml.apache.org>
>
>
Re: A question about SOAP with attachments!
Posted by Scott Nichol <sn...@scottnichol.com>.
I believe you have received excellent advice on this. Apache SOAP does
create one or more in-memory images of the entire SOAP envelope, so the
maximum heap size you've allowed your JVM (and, ultimately, the amount
of virtual memory on your machine) will limit the size of attachment you
can send. If you want to send document that are larger than half
(assuming Apache SOAP creates 2 copies) the virtual memory of your
mechine, Apache SOAP is not the SOAP implementation to prefer.
While you are considering attachments, you should be aware that there
are interoperability issues, if that is of concern to you. As a
specific example, Microsoft's SOAP Toolkit only supports DIME
attachments (not MIME), while Apache SOAP supports only MIME attachments
(not DIME).
Scott Nichol
----- Original Message -----
From: "Apostolopoulos Paris" <pa...@freemail.gr>
To: <so...@xml.apache.org>
Sent: Sunday, October 27, 2002 4:59 PM
Subject: A question about SOAP with attachments!
> Hi!
>
> I quite new to SOAP , I want to know , from your experience is there
any
> limitation about the capacity of data tha can be carried out in a SOAP
> envelope as an attachement.In the specs it says something like an
image
> or a document (MIME attachements) but is it efficient to attach lets
say
> a 50MB file?
> For those that are going to scream with that (sorry guys and girls)
but
> I am just wondering if I could use SOAP with attachments in my
> Server-Client application that talk using Message style SOAP , and
their
> main functionality actually is file transfer!
>
> Thank you for your time
> Apostolopoulos Paris
>
>
>
> --
> To unsubscribe, e-mail:
<ma...@xml.apache.org>
> For additional commands, e-mail:
<ma...@xml.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
RE: A question about SOAP with attachments!
Posted by Anne Thomas Manes <an...@manes.net>.
Anyone know how Axis manages attachments?
I know that WASP uses stream processing, so has no message size limit. I'm
not sure about open source solutions, though.
Anne
> -----Original Message-----
> From: Mike Kopack [mailto:mkopack@isx.com]
> Sent: Monday, October 28, 2002 1:31 PM
> To: soap-user@xml.apache.org
> Subject: Re: A question about SOAP with attachments!
>
>
> I can attest from experience that there is definately a limit in
> Apache SOAP
> in this regard. I am working on a SOAP xml-rpc based client/server
> application that needs to be able to send files between the client and the
> server. Whenever I tried to send the file along as a DataHandler or
> Inputstream, if the file was bigger than around 18 MB in size I
> would get a
> "Out of Memory Error" on the side trying to send the file.
>
> My only way to get around this problem was to write a simple
> "browser" that
> could request files from the server and another that would perform an HTTP
> Post to a JSP running on the server so I could send. While this works, it
> circumvents our desire to use SOAP for everything and is a bit of a hack.
>
> The only thing I could come up with is that when you send
> structures like an
> Inputstream, Apache SOAP stores everything in memory as it's
> building up the
> envelope prior to sending it. As a result, large items eat up the
> Java heap
> space and a memory error occures.
>
> Sorry, wish I had better news... If anyone knows of a way around this
> problem other than what I've outlined, I'd love to hear it!
>
> --Mike
>
> ----- Original Message -----
> From: "WJCarpenter" <bi...@carpenter.org>
> To: <so...@xml.apache.org>
> Sent: Monday, October 28, 2002 1:22 PM
> Subject: RE: A question about SOAP with attachments!
>
>
> > > Theoretically, there's no limit. But depending on how the SOAP runtime
> > > deals with the messages, there may be a limit imposed by your system's
> > > memory: i.e., if the SOAP runtime tries to load the message
> into memory
> > > before processing. You'll need a stream-based processor to deal with
> > > unlimited size.
> >
> > Hear, hear. In particular, if you are contemplating using Apache
> > SOAP 2.x, you should probably start looking at other solutions. Even
> > for messages, the Apache SOAP 2.x client code is quite promiscuous in
> > the number of in-memory copies it makes of the entire response payload.
> >
> >
> >
> >
> > --
> > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > For additional commands, e-mail: <ma...@xml.apache.org>
> >
> >
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
RE: A question about SOAP with attachments!
Posted by Anne Thomas Manes <an...@manes.net>.
Anyone know how Axis manages attachments?
I know that WASP uses stream processing, so has no message size limit. I'm
not sure about open source solutions, though.
Anne
> -----Original Message-----
> From: Mike Kopack [mailto:mkopack@isx.com]
> Sent: Monday, October 28, 2002 1:31 PM
> To: soap-user@xml.apache.org
> Subject: Re: A question about SOAP with attachments!
>
>
> I can attest from experience that there is definately a limit in
> Apache SOAP
> in this regard. I am working on a SOAP xml-rpc based client/server
> application that needs to be able to send files between the client and the
> server. Whenever I tried to send the file along as a DataHandler or
> Inputstream, if the file was bigger than around 18 MB in size I
> would get a
> "Out of Memory Error" on the side trying to send the file.
>
> My only way to get around this problem was to write a simple
> "browser" that
> could request files from the server and another that would perform an HTTP
> Post to a JSP running on the server so I could send. While this works, it
> circumvents our desire to use SOAP for everything and is a bit of a hack.
>
> The only thing I could come up with is that when you send
> structures like an
> Inputstream, Apache SOAP stores everything in memory as it's
> building up the
> envelope prior to sending it. As a result, large items eat up the
> Java heap
> space and a memory error occures.
>
> Sorry, wish I had better news... If anyone knows of a way around this
> problem other than what I've outlined, I'd love to hear it!
>
> --Mike
>
> ----- Original Message -----
> From: "WJCarpenter" <bi...@carpenter.org>
> To: <so...@xml.apache.org>
> Sent: Monday, October 28, 2002 1:22 PM
> Subject: RE: A question about SOAP with attachments!
>
>
> > > Theoretically, there's no limit. But depending on how the SOAP runtime
> > > deals with the messages, there may be a limit imposed by your system's
> > > memory: i.e., if the SOAP runtime tries to load the message
> into memory
> > > before processing. You'll need a stream-based processor to deal with
> > > unlimited size.
> >
> > Hear, hear. In particular, if you are contemplating using Apache
> > SOAP 2.x, you should probably start looking at other solutions. Even
> > for messages, the Apache SOAP 2.x client code is quite promiscuous in
> > the number of in-memory copies it makes of the entire response payload.
> >
> >
> >
> >
> > --
> > To unsubscribe, e-mail: <ma...@xml.apache.org>
> > For additional commands, e-mail: <ma...@xml.apache.org>
> >
> >
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
Re: A question about SOAP with attachments!
Posted by Mike Kopack <mk...@isx.com>.
I can attest from experience that there is definately a limit in Apache SOAP
in this regard. I am working on a SOAP xml-rpc based client/server
application that needs to be able to send files between the client and the
server. Whenever I tried to send the file along as a DataHandler or
Inputstream, if the file was bigger than around 18 MB in size I would get a
"Out of Memory Error" on the side trying to send the file.
My only way to get around this problem was to write a simple "browser" that
could request files from the server and another that would perform an HTTP
Post to a JSP running on the server so I could send. While this works, it
circumvents our desire to use SOAP for everything and is a bit of a hack.
The only thing I could come up with is that when you send structures like an
Inputstream, Apache SOAP stores everything in memory as it's building up the
envelope prior to sending it. As a result, large items eat up the Java heap
space and a memory error occures.
Sorry, wish I had better news... If anyone knows of a way around this
problem other than what I've outlined, I'd love to hear it!
--Mike
----- Original Message -----
From: "WJCarpenter" <bi...@carpenter.org>
To: <so...@xml.apache.org>
Sent: Monday, October 28, 2002 1:22 PM
Subject: RE: A question about SOAP with attachments!
> > Theoretically, there's no limit. But depending on how the SOAP runtime
> > deals with the messages, there may be a limit imposed by your system's
> > memory: i.e., if the SOAP runtime tries to load the message into memory
> > before processing. You'll need a stream-based processor to deal with
> > unlimited size.
>
> Hear, hear. In particular, if you are contemplating using Apache
> SOAP 2.x, you should probably start looking at other solutions. Even
> for messages, the Apache SOAP 2.x client code is quite promiscuous in
> the number of in-memory copies it makes of the entire response payload.
>
>
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
Re: A question about SOAP with attachments!
Posted by Mike Kopack <mk...@isx.com>.
I can attest from experience that there is definately a limit in Apache SOAP
in this regard. I am working on a SOAP xml-rpc based client/server
application that needs to be able to send files between the client and the
server. Whenever I tried to send the file along as a DataHandler or
Inputstream, if the file was bigger than around 18 MB in size I would get a
"Out of Memory Error" on the side trying to send the file.
My only way to get around this problem was to write a simple "browser" that
could request files from the server and another that would perform an HTTP
Post to a JSP running on the server so I could send. While this works, it
circumvents our desire to use SOAP for everything and is a bit of a hack.
The only thing I could come up with is that when you send structures like an
Inputstream, Apache SOAP stores everything in memory as it's building up the
envelope prior to sending it. As a result, large items eat up the Java heap
space and a memory error occures.
Sorry, wish I had better news... If anyone knows of a way around this
problem other than what I've outlined, I'd love to hear it!
--Mike
----- Original Message -----
From: "WJCarpenter" <bi...@carpenter.org>
To: <so...@xml.apache.org>
Sent: Monday, October 28, 2002 1:22 PM
Subject: RE: A question about SOAP with attachments!
> > Theoretically, there's no limit. But depending on how the SOAP runtime
> > deals with the messages, there may be a limit imposed by your system's
> > memory: i.e., if the SOAP runtime tries to load the message into memory
> > before processing. You'll need a stream-based processor to deal with
> > unlimited size.
>
> Hear, hear. In particular, if you are contemplating using Apache
> SOAP 2.x, you should probably start looking at other solutions. Even
> for messages, the Apache SOAP 2.x client code is quite promiscuous in
> the number of in-memory copies it makes of the entire response payload.
>
>
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
RE: A question about SOAP with attachments!
Posted by WJCarpenter <bi...@carpenter.org>.
> Theoretically, there's no limit. But depending on how the SOAP runtime
> deals with the messages, there may be a limit imposed by your system's
> memory: i.e., if the SOAP runtime tries to load the message into memory
> before processing. You'll need a stream-based processor to deal with
> unlimited size.
Hear, hear. In particular, if you are contemplating using Apache
SOAP 2.x, you should probably start looking at other solutions. Even
for messages, the Apache SOAP 2.x client code is quite promiscuous in
the number of in-memory copies it makes of the entire response payload.
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
RE: A question about SOAP with attachments!
Posted by WJCarpenter <bi...@carpenter.org>.
> Theoretically, there's no limit. But depending on how the SOAP runtime
> deals with the messages, there may be a limit imposed by your system's
> memory: i.e., if the SOAP runtime tries to load the message into memory
> before processing. You'll need a stream-based processor to deal with
> unlimited size.
Hear, hear. In particular, if you are contemplating using Apache
SOAP 2.x, you should probably start looking at other solutions. Even
for messages, the Apache SOAP 2.x client code is quite promiscuous in
the number of in-memory copies it makes of the entire response payload.
RE: A question about SOAP with attachments!
Posted by Anne Thomas Manes <an...@manes.net>.
Theoretically, there's no limit. But depending on how the SOAP runtime deals
with the messages, there may be a limit imposed by your system's memory:
i.e., if the SOAP runtime tries to load the message into memory before
processing. You'll need a stream-based processor to deal with unlimited
size.
Anne
> -----Original Message-----
> From: Apostolopoulos Paris [mailto:papo@freemail.gr]
> Sent: Sunday, October 27, 2002 4:59 PM
> To: soap-user@xml.apache.org
> Subject: A question about SOAP with attachments!
>
>
> Hi!
>
> I quite new to SOAP , I want to know , from your experience is there any
> limitation about the capacity of data tha can be carried out in a SOAP
> envelope as an attachement.In the specs it says something like an image
> or a document (MIME attachements) but is it efficient to attach lets say
> a 50MB file?
> For those that are going to scream with that (sorry guys and girls) but
> I am just wondering if I could use SOAP with attachments in my
> Server-Client application that talk using Message style SOAP , and their
> main functionality actually is file transfer!
>
> Thank you for your time
> Apostolopoulos Paris
>
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>
--
To unsubscribe, e-mail: <ma...@xml.apache.org>
For additional commands, e-mail: <ma...@xml.apache.org>
RE: A question about SOAP with attachments!
Posted by Anne Thomas Manes <an...@manes.net>.
Theoretically, there's no limit. But depending on how the SOAP runtime deals
with the messages, there may be a limit imposed by your system's memory:
i.e., if the SOAP runtime tries to load the message into memory before
processing. You'll need a stream-based processor to deal with unlimited
size.
Anne
> -----Original Message-----
> From: Apostolopoulos Paris [mailto:papo@freemail.gr]
> Sent: Sunday, October 27, 2002 4:59 PM
> To: soap-user@xml.apache.org
> Subject: A question about SOAP with attachments!
>
>
> Hi!
>
> I quite new to SOAP , I want to know , from your experience is there any
> limitation about the capacity of data tha can be carried out in a SOAP
> envelope as an attachement.In the specs it says something like an image
> or a document (MIME attachements) but is it efficient to attach lets say
> a 50MB file?
> For those that are going to scream with that (sorry guys and girls) but
> I am just wondering if I could use SOAP with attachments in my
> Server-Client application that talk using Message style SOAP , and their
> main functionality actually is file transfer!
>
> Thank you for your time
> Apostolopoulos Paris
>
>
>
> --
> To unsubscribe, e-mail: <ma...@xml.apache.org>
> For additional commands, e-mail: <ma...@xml.apache.org>
>