I don't believe that the host lookup or db connection is the issue.  The page 
we are serving up is the login page.  I will create a test "hello world" jsp to 
see if the problem still occurs with that page.

-- Dave
> 
> In a situation like that, the two things I check first are:
> 
> 1) DNS lookup failing, especially a reverse lookup..do you have Tomcat 
> trying to look up a hostname for access logging, perhaps?
> 
> 2) database connection timing out
> 
> Also, I would look at garbage collection, but I doubt that's it.
> 
> John
> 
> On Fri, 11 Jul 2003 19:22:41 +0000, <[EMAIL PROTECTED]> wrote:
> 
> > Yes, these occur internally and externally.  There does not appear to be 
> > any network traffic that is causing this (according to the network 
> > people...).  We're also seeing this on two different environments on two 
> > distinct networks.
> >
> > After some more digging, there is just NOTHING happening on the machine.  
> > Dual CPU, with both cpu's sitting at about 99% idle.  1 GB of RAM, and 
> > it's not even being all used.  Tomcat is using about 327MB of RAM with 
> > maybe 40(?) threads running.
> >
> > When I submit my request to get the login page (not to process the login, 
> > just to serve the login page), I couple of the java threads will spin up 
> > and take maybe 3% of the cpu, but it still takes over 30 seconds to get 
> > the page.
> >
> > Still stuggling for ideas.
> >
> > -- Dave
> >> Are these results occurring when tested on a local
> >> area network as well?
> >>
> >> I have had an issue like that, but it turned out to be
> >> a networking issue..not tomcat.
> >>
> >>
> >> --- [EMAIL PROTECTED] wrote:
> >> > With Tomcat 4.1.x
> >> > > We've recently run into an issue where some of our
> >> > pages either
> >> > a) take a really long time to come up (20+ seconds) >  or
> >> > b) come up, but never really finish loading (the
> >> > status bar in IE shows the the > response hasn't finished).
> >> > > These are very simple pages (for example, a login
> >> > page) and our server load is > minimal (maybe 10 concurrent users).  
> >> Then,
> >> > mysteriously, the problem will go > away by itself.  It will also 
> >> return.
> >> > > Given the information above, I'm not expecting any
> >> > solutions, but I could use > some help steering me in the right 
> >> direction with
> >> > things to check.  We're > hooking up monitoring on the systems (Linux) 
> >> to
> >> > examine memory and CPU > utilization during the slowdowns.
> >> > > Any things in particular we should be examining to
> >> > try to find the problem?  > Any idea why the pages would never fully 
> >> return from
> >> > the server?
> >> > > TIA
> >> > > -- Dave
> >> > >
> >> ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail:
> >> > [EMAIL PROTECTED]
> >> > For additional commands, e-mail:
> >> > [EMAIL PROTECTED]
> >> >
> >>
> >>
> >> __________________________________
> >> Do you Yahoo!?
> >> SBC Yahoo! DSL - Now only $29.95 per month!
> >> http://sbc.yahoo.com
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
> 
> 
> 
> -- 
> Using M2, Opera's revolutionary e-mail client: http://www.opera.com/m2/
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to