tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 41330] - jk 1.2 Connection handling causes unexpected results.
Date Tue, 09 Jan 2007 22:40:30 GMT
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=41330>.
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=41330





------- Additional Comments From rainer.jung@kippdata.de  2007-01-09 14:40 -------
Can you reproduce the behaviour?
In mod_jk 1.2.16 there was another bit added to recovery_options (Bit value 4)
to close backend connections when Browser read or write errors occured. Based on
the code of mod_jk 1.2.20 we had a discussion, that this flag is not needed any
more, because mod_jk closes backend connections whenever client read/write
errors occur:

http://marc.theaimsgroup.com/?l=tomcat-dev&m=116436503125947&w=2

I'm not exactly sure at the moment, if this also holds true for 1.2.19.

So: Can you reproduce? Also for 1.2.20?


-- 
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: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message