Hi, Jared.
Your service is using rpc/encoded.
The identifying parts of the wsdl are:
http://schemas.xmlsoap.org/soap/http"/>
^
http://schemas.xmlsoap.org/soap/encoding/";
namespace="http://webservices.
hi Linus,
thanks for the link! after doing some reading, I'm still not sure
which category this service falls under. I've attached an edited
(identifying info replaced by '' and '') version of the WSDL
for this service.
For reference, I have -Xmx1024m set in the JVM.
Have you had any luc
Hi, Jared.
doc/lit wrapped is the web service "style". There are various styles:
primarily RPC-encoded, document/literal, and "wrapped" which is a
variation on document/literal. Much information available about that.
The following is probably not the best introductory information, but I
hap
hi Linus,
I can send a single request at a time of the required size, and it
will succeed. However, when I start more simultaneous requests beyond
the first one, they invariably fail with OutOfMemoryErrors. The OOM
occurs somewhere inside of Axis.
The web service works like this: it runs inside T
Of course, the moment I send off a message to a mailing list, after
having claimed I read the archives, I find a message that nearly
answers my question.
http://marc.theaimsgroup.com/?l=axis-user&m=113871304213627&w=2
This message mentions this JIRA issue:
http://issues.apache.org/jira/browse/AX
What "style" of web service are you using?
I have successfully sent attachments of > 200MB using doc/lit wrapped,
and I'm sure I could send larger ones.
The trouble I run into is when I try to parse the attachments (they are
XML,) but that is outside of Axis/SOAP.
Jared Klett wrote:
gree
greetings all,
I've taken a contract job to improve the performance of a Java Web
Service based on Axis. The service is required to handle multiple
simultaneous SOAP requests that can be anywhere from two to 100 MB in
size. So far, the service fails with an OutOfMemoryError when I submit
any more
