That's very good advice. Another good thing to do is unplug the cable to your network card during development to see what your application does under those circumstances.
We use licensed database in our office, and I found all kinds of great bugs by installing a single user license on the development environment. Sometimes they pop up when you'd least expect. Fault tolerance. Fun stuff. Anthony -- Got a blog? Post it: http://www.martin-studio.com/weblog-index/ On 1/6/04 7:36 PM, in article [EMAIL PROTECTED], "Andrew Hill" <[EMAIL PROTECTED]> wrote: > Ive found that limiting your connection pool to a single connection during > development can help pick such bugs up a lot quicker. > > -----Original Message----- > From: Anthony Martin [mailto:[EMAIL PROTECTED] > Sent: Wednesday, 7 January 2004 06:11 > To: [EMAIL PROTECTED] > Subject: Re: server hangs after finite number of requests > > > I've had something like that happen when I call > getDataSource(request).getConnection() and forget to close them. After a > finite number of requests, the server appears to hang. Actually, depending > on the settings, it will timeout. But how you handle the exception could > prevent it from being properly reported. > > > On 1/6/04 11:38 AM, in article > [EMAIL PROTECTED], "Heather Marie > Buch" <[EMAIL PROTECTED]> wrote: > >> >> Manfred Wolff wrote: >> >>> Heather. >>> >>> Have you studied the tomcat logs? >> >> Yes, I have. This is the only thing that is remotely interesting. >> In localhost_log.2004-01-06.txt I get this: >> >> 2004-01-06 03:38:41 action: null >> 2004-01-06 03:40:08 action: null >> 2004-01-06 03:40:12 action: null >> 2004-01-06 03:40:14 action: null >> 2004-01-06 03:40:16 action: null >> 2004-01-06 03:40:18 action: null >> 2004-01-06 03:40:21 action: null >> 2004-01-06 03:40:23 action: null >> >> (corresponding to the 8 times I try to log in). I don't really know where > it >> is >> coming from. I would like to know what is generating the above, so I could > to >> in and modify the logging >> statements to produce a bit more detail! >> >> I also have log4j statements in my own code and have been testing this. > But I >> can't generate any error or anything beyond the normal output, 8 times. >> >> What is interesting is that it always fails on the 9th try. I don't think > it >> is >> a matter of seconds either. I have tested over a longer period (10 > minutes), >> but >> it still gives me 8 requests before it hangs. >> >> And Geeta Ramani - thanks. I will take another look at the jdbc stuff! >> >> Best, >> >> Heather Buch >> >> >> >>> >>> Manfred Wolff >>> >>> Heather Marie Buch wrote: >>> >>>> Hi all, >>>> >>>> If I submit the same page more than 8 times, my server dies and I have > to >>>> restart. For example, the first 8 times I enter the wrong password, > struts >>>> will simply return me to my original form with an error message. > However, >>>> the 9th time - the server hangs. >>>> >>>> This also occurs if I enter the correct password, then press the >>>> "back" button and return to the original login screen and submit again. > I >>>> can only repeat this 8 times. The server hangs on the 9th try. >>>> >>>> I am using: >>>> >>>> tomcat 4.1.12 >>>> httpd 2.0.43 >>>> mysql 3.23.53 >>>> struts 1.1 >>>> >>>> I am not even sure if this is a struts problem. I suspect it is because > I >>>> tried that back button trick with a plain old servlet, and I was able > to >>>> do it more than 9 times. >>>> >>>> Any help would be greatly appreciated! My boss wants users to be able to >>>> try passwords more than 9 times! >>>> >>>> Thanks, >>>> >>>> Heather Buch > > > > --------------------------------------------------------------------- > 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]
