RE: Stalled Pages

Fri, 20 Oct 2000 09:26:34 -0700

Title: Tomcat implementation classes' s documentation?
Thanks Mike, it appears to work.. We still have to do a lot of testing but it used to stall about 1 out of 7 tries and in my tests I hit the stalling page at least 100 times w/o a stall.. Weird problem!
 
Julio - Yes, it is very important to close your database connections before leaving - I noticed that as soon as I ran out of database connections a few months back :)   I also implemented a connection pool that reclaims lost connections after a specified time frame, but that will still burn you if you have high traffic!
 
Thanks for your help!
Steve
-----Original Message-----
From: Julio Serje (@Canada) [mailto:[EMAIL PROTECTED]]
Sent: Thursday, October 19, 2000 8:15 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Stalled Pages

Appart from the esoteric solution that Mike is suggesting (pls let me know if it worked!!), you also may also find useful the following: (it happened to me, with the same symptoms..):  
 
check that JDBC connections that use drivers of type 1 and 2 (for example the JDBC:ODBC bridge in NT environments) are closed before the page ends its excecution. I experienced the same problem working with the JDBC driver of  Fulcrum SearchServer (in both NT and HP-UX environments). Seems that active connections that make use of JNI can prevent the process to die...
 
Julio Serje
Calian  Technologies
Kanata, ON, Canada.
    
----- Original Message -----
Sent: Thursday, October 19, 2000 5:29 AM
Subject: RE: Stalled Pages

You're going to love this.
 
It sounds like it might be the same problem I was having, where IE5.5 has problems recognising the end of a page through SSL when the transfer method is "Chunked". Does this happen on older browsers?
 
The solution, believe it or not, is to make sure the first line of your file that's returned to the browser is not blank. I did this by changing my JSPs to have the <HTML> tag on the very first line, and then the <%page stuff.
 
Cheers... Mike
 
-----Original Message-----
From: Steve Haines [mailto:[EMAIL PROTECTED]]
Sent: 18 October 2000 18:56
To: '[EMAIL PROTECTED]'
Subject: Stalled Pages

Hi All,
 
I am experiencing a strange problem where pages served up by Tomcat are stalling while running on Solaris. I am using the released version of Tomcat 3.1 on Solaris 8 (currently testing w/o integrating it in a web server) and it occassionally stalls.. I have checked the downloaded HTML file and it is complete (and processed - the JSP worked), but for some reason Tomcat does not let the browser know that it has completed the transaction - so the HTML page's onload() method is never processed and the browser ends up giving a Timeout error.
 
I have tested this with IE 5 and Netscape 4.75 from both NT and Solaris (Netscape only) and it fails on both, so it appears to be a server side issue. What could be happening? Any ideas? Could Tomcat not be closing the socket that the browser opened to it? And most importantly, any ideas how I can fix the problem :) ?
 
Thanks in advance!
Steve

Reply via email to