Btw, I know that this is not an isolated case. I've heard of this several
times but haven't had any time to devote to figuring out why exactly it
happens. Seems that when SOAP is run non-stop for a period of time it
just starts to get mucked up and slows way down. I've taken to simply
restarting the worker automatically everyday on my test box just to take
care of this. I've heard of this from quite a few people.
- James M Snell/Fresno/IBM
Web services architecture and strategy
Internet Emerging Technologies, IBM
544.9035 TIE line
559.587.1233 Office
919.486.0077 Voice Mail
[EMAIL PROTECTED]
=================================================================
Have I not commanded you? Be strong and courageous. Do not be terrified,
do not be discouraged, for the Lord your God will be with you wherever you
go.
- Joshua 1:9
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Re: Slowing down
Ryan Winkler wrote:
> I've encountered a curious problem with our SOAP server. After a period
of
> time (a matter of days), the amount of time it takes for our JSPs that
use
> the SOAP calls to display in a browser has gone from a few seconds to
over
> half a minute. Other, non-SOAP JSPs on the same server (different
Tomcat
> workers) have no performance loss. Restarting the Tomcat worker returns
the
> display times for the JSPs using SOAP to a few seconds. Any
> ideas/suggestions?
that is very interesting - was there any difference in memory or cpu usage
between old and newly
retsrted process? you may also try different JDK versions and different
OS...
alek
