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().getRecorder().clear(); > > > > If I'm not running the client is there anyway to stop the leak? > > > > Thanks > > Suzy
