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

http://issues.apache.org/bugzilla/show_bug.cgi?id=39290

           Summary: mod_jk 1.2.15 and out.write() strange behaviour
           Product: Tomcat 5
           Version: 5.5.16
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Connector:AJP
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: [EMAIL PROTECTED]


Suppose the following loop that to writes to a webpage indefinitely:

...
try {
        while (true)
        {
                out.println("... AAA ...");
                out.flush();

                try
                {
                        Thread.sleep(1000L);
                } catch (InterruptedException e) {  }
        }

        out.close();
}
catch (Exception e)     { e.printStackTrace() }
....

The expected behaviour is that once you click the browser stop button the loop 
break and the stack trace is printed.

It works on these configuration:
- accessing the page directly through the http11 connector
- mod_jk version 1.2.10

It doesn´t work (it loops indefinitely and the exception is never raised)
- mod_jk version 1.2.14
- mod_jk version 1.2.15

So I guess something got broken on the latest versions.

Thanks.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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

Reply via email to