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=12346>.
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=12346

Constant Refreshes crash Web Applications in TOMCAT

           Summary: Constant Refreshes crash Web Applications in TOMCAT
           Product: Tomcat 4
           Version: 4.1.7
          Platform: PC
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Blocker
          Priority: Other
         Component: Connector:Coyote JK 2
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


Seems to be an issue with requests coming in to fast for the filter and it 
cannot draw the frames properly or send the right information to the correct 
frame. 

We found the same issue in TC 4.1.7 and 4.1.9
We were also using JRE 1.4.0_01

Here is what I did to recreate/test the issue.  
 
1. Found an example from Jakarta that uses frames.
2. Decided on the admin pages (the admin site). 
3. Tested running on port 8080 without IIS

--* Remember to add a user entry in the tomcat-users.xml file with the "admin"
    role. Like the following:
   <user username="admin" password="admin" roles="admin,manager"/>

4. Login to http://localhost:8080/admin 
   (using the user you added in tomcat-users.xml).


5. on the index.jsp page press F5 rapidly to refresh the screen without 
allowing the page to complete refresh.  

Everything works fine. Issue does not appear when accessing a "Framed" 
application on TC using port 8080.
Then...
 
6. Setup Tomcat and IIS to use the ISAPI filter (isapi_redirector2.dll/coyote)
--* Add an entry for the Tomcat Administrator App (For an example  
    application) in workers2.properties

7. Login to http://localhost/admin 
   

8. on the index.jsp page press F5 rapidly to refresh the screen without 
allowing the page to complete refresh.  Within a few hit the FRAMES will be 
removed and you will get a single instance of 1 of the pages (never the same 
page)...  

9: Go back to port 8080 and everything is fine.  Something breaks between the 
ISAPI filter and TOMCAT

The only error in the logs, that we see is:
Found in jk2.log

admin/login.jsp;jsessionid=80D23B3999E9936ECEC2A7F72B5154C3 lb:lb
[Thu Sep 05 16:43:19 2002] (debug ) [jk_isapi_plugin.c (325)]  HttpFilterProc 
[/admin/login.jsp;jsessionid=80D23B3999E9936ECEC2A7F72B5154C3] is a servlet 
url - should redirect to lb:lb
[Thu Sep 05 16:43:19 2002] (debug ) [jk_isapi_plugin.c (392)]  HttpFilterProc 
check if [/admin/login.jsp;jsessionid=80D23B3999E9936ECEC2A7F72B5154C3] is 
pointing to the web-inf directory
[Thu Sep 05 16:43:19 2002] (debug ) [jk_isapi_plugin.c (461)]  
HttpExtensionProc started
[Thu Sep 05 16:43:19 2002] (debug ) [jk_isapi_plugin.c (467)]  
HttpExtensionProc got a worker for name lb:lb
[Thu Sep 05 16:43:19 2002] (error ) [jk_worker_ajp13.c (339)]  ajp13.service() 
error sending, reconnect channel.socket:localhost:8009 -1 0 No error



Almost looks like a threading issue.  Could it be that the ISAPI filter does 
not know that the request is a FRAME and is sending back the request as soon as 
it gets one of the pages back? 

This issue CANNOT be recreated in a non-Framed site


If more information is needed, please contact me at [EMAIL PROTECTED]

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

Reply via email to