You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2002/08/11 03:48:05 UTC

DO NOT REPLY [Bug 11613] New: - Page Load Problem in Stand-alone Mode

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11613>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11613

Page Load Problem in Stand-alone Mode

           Summary: Page Load Problem in Stand-alone Mode
           Product: Tomcat 4
           Version: 4.0.4 Final
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Catalina
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: cisaacson@compuflex.com


When running Tomcat in stand-alone mode, if I successively request pages in 
two different frames, the second page often does not display. I get a "Server 
not found" error in the browser. For example, to keep pages in multiple frames 
in synch I submit one frame based on the JavaScript ONLOAD event of the other, 
so the second pages is requested immediately after the first. Using the Coyote 
connector, this works fine so long as both pages are JSP. If one page is JSP 
and the other HTML, the HTML will display using Coyote, after about a 10 
second delay (with both JSPs there is no delay). Using the regular default 
connector, I almost always get the server not found error. I tried this same 
code in WebSphere 4.x, and it works fine with JSP and an HTML page without 
delay or a problem.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>