-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hassan,
On 2/23/2010 2:19 PM, Hassan Schroeder wrote:
> On Tue, Feb 23, 2010 at 11:05 AM, Christopher Schultz
> wrote:
>
>> Something like every hour or maybe every minute, you could make a
>> request to some trivial page like "/ping.jsp".
>
> Whic
On Tue, Feb 23, 2010 at 11:05 AM, Christopher Schultz
wrote:
> Something like every hour or maybe every minute, you could make a
> request to some trivial page like "/ping.jsp".
Which is exactly what a service monitor like Nagios does -- plus it
lets you know if the proper response isn't receive
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
All,
On 2/22/2010 2:14 PM, Peter Crowther wrote:
> On 22 February 2010 19:07, Caldarale, Charles R
> wrote:
>> Sounds like the OS might be paging out Tomcat, and taking a long time to get
>> all the necessary pages back in when a request is made. I
On 22 February 2010 19:07, Caldarale, Charles R
wrote:
> Sounds like the OS might be paging out Tomcat, and taking a long time to get
> all the necessary pages back in when a request is made. I'm not familiar
> with operational details of AIX, but I would suspect there are some
> system-level
> From: klin...@poczta.fm [mailto:klin...@poczta.fm]
> Subject: Webapp slow down after idle - 5.5.x
>
> The problem is that every first request after a longer idle
> (like a day) is served very slow.
Sounds like the OS might be paging out Tomcat, and taking a long time to get
al
One thing that comes to mind is virtual
memory swapping. If Tomcat is idle for a long time, all of its memory
may be swapped out to disk to make room for other programs. Then when
Tomcat needs to handle a request, it must be swapped back in from disk
which takes time.
I've observed the har
Hello,
My webservice (using axis 1.1)is deployed on tomcat 5.5.28. Tomcat runs on AIX
and IBM Java 1.5 SR9. The problem is that every first request after a longer
idle (like a day) is served very slow. There's no performance problem with next
requests. It looks quite similar to first request af
