If the problem is the message rather than the handling of it, have you considered applying ZIP/UNZIP algorithms in the serializer/deserializer for your object? TIFF is quite a compressible format.
Keith -----Original Message----- From: Praveen Peddi [mailto:[EMAIL PROTECTED]] Sent: 03 February 2003 17:04 To: [EMAIL PROTECTED] Subject: Re: AW: Out of Memory problem I would use SOAP with attachments. Encoding into Base64 format will occupy ur memory more than 2 times both on the server side and the cleint side. I did the same thing before and had memory problems, but when I used SOAP with attachments (Using DataHandler) it solved some problems. Increasing the java memory size is a good thging but not the appropriate solution. Use attachments and also increase memory. That will help you more. Praveen ----- Original Message ----- From: "Elmar Fasel" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, February 03, 2003 11:40 AM Subject: Re: AW: Out of Memory problem > Hi Markus, > > Markus Doss schrieb: > > > First I increased the memory to 128M. After increasing up to 256 the > > my soap client doesn't throw any exception. But now the out of memory > > comes from tomcat (with 256M memory, on linux). > > > > Fault Code = SOAP-ENV:Server.Exception: Fault String = > > java.lang.OutOfMemoryError > > > > Any further solutions ? > > Increase the memory allocation pool size of tomcat? > The start script "catalina.sh" looks for an environment variable called > $JAVA_OPTS. > > So: > export JAVA_OPTS=-Xmx256m > > Regards, > Elmar > >
