Re: Memory Leap on server side

[Peter Molettiere]

Try these, in this order:
0) Use the latest axis distro
1) Use xerces 2.6.2
2) Up your heap size:  -Xmx768M -Xms128M -XX:+UseConcMarkSweepGC
Then go look at the axis mailing list and read the last few days of  
discussion about memory leaks versus severe memory use.

--Peter
On Jan 18, 2005, at 6:01 AM, Suzy Fynes wrote:
Only the one application running on tomcat but deploying would happen
every week. I was restarting axis from tomcat manager a bit last week
that was causing axis to run out memory. But the application and WS
stuff was running fine for the last few days then the out of memory
error occurred today.
-----Original Message-----
From: Paul Callahan [mailto:[EMAIL PROTECTED]
Sent: 18 January 2005 13:12
To: [EMAIL PROTECTED]
Subject: Re: Memory Leap on server side
Do you have multiple applications running on that instance of Tomcat,
and if so, are you deploying the WAR files frequently?  Like I
mentioned last week, there is a mem leak in Tomcat when deploying over
and over that will cause OutOfMemoryError's...
Otherwise, is it happening after the application is running
successfully for a while?
-pc
On Tue, 18 Jan 2005 10:53:56 -0000, Suzy Fynes
<[EMAIL PROTECTED]> wrote:

Hi,

It seems that the axis running on my server is causing a memory leak
which
causes the whole application to slow and some of it to show internal
errors.

Tomcat logs indicated

java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
java.lang.OutOfMemoryError
Internal Server Error
The server encountered an internal error or misconfiguration and was
unable
to complete your request.
Please contact the server administrator, [EMAIL PROTECTED] and inform
them of
the time the error occurred, and anything you might have done that may
have
caused the error.
More information about this error may be available in the server error
log.
Additionally, a 500 Internal Server Error error was encountered while
trying
to use an ErrorDocument to handle the request.

_______________________________________________________________________ 
_
_______________________

I've seen some posts here that help solve the problem on the client
side

In client-side stub code, look for the call object and try:


Call.getMessageContext().getRequestMessage().getSOAPEnvelope().getRecor 
d
er().clear();

If I'm not running the client is there anyway to stop the leak?

Thanks
Suzy


--
Peter Molettiere
Senior Engineer
Truereq, Inc.
http://www.truereq.com/