Although the client displays the error, the error actually occurs on the
server. You *may* be able to get around the problem by increasing the
JVM max heap size for your servlet container, but only if your payloads
are small enough to fit into that amount of memory. Of course, if the
server is able to send a larger payload, the client will also have to
have enough memory to read it and parse it into a DOM (well, it does not
need to parse into a DOM if you send the data as an attachment).
The next version of Apache SOAP will lower the memory requirement
relative to payload size and *may* even get to the point where it
streams the result without first writing it to memory.
Scott Nichol
----- Original Message -----
From: "Hongda Lin" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, December 05, 2002 12:38 PM
Subject: Please help: SOAP 2.3 out of memory error
Hi,
I am using SOAP 2.3 with Tomcat 4.0.4 (Coyote as HTTP
connector). I am using RPC calls. It normally runs ok, except it gives
me java.lang.OutOfMemoryError on the client side sometimes(probably
working with large strings). The complete error message is:
Generated fault: [Attributes={}] [faultCode=SOAP-ENV:Server]
[faultString=Exception from service object: null]
[faultActorURI]/soap/servlet/rpcrouter]
[DetailEntries=[<0>=<stackTrace>java.lang.OutOfMemoryError
&lt;&lt;no stack trace available&gt;&gt;
</stackTrace>]
] [FaultEntries = ]
Thank you in advance,
Hongda
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
