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=40965>. 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=40965 Summary: Uninitialised jk_ws_service_t fields prevent AJP13 connection reuse and cause flushing Product: Tomcat 5 Version: 5.0.0 Platform: PC OS/Version: Windows XP Status: NEW Severity: critical Priority: P2 Component: Native:JK AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] Several flags have in recent times been added to ajp_common.c, with initialisation code in mod_jk: - disable_reuse - flush_headers - flush_packets These were not initialised in the IIS connector, and thus when they were checked, uninitialised memory was being accessed, with the result that they were all evaluated as being set. This results in AJP13 connections between the connector and Tomcat not being reused, and every header and packet write causing a flush. i.e. we're back in the AJP12 days. I've attached a patch to correct this, with an attempt at a check to ensure it doesn't accidentally get broken again - I'd be open to other ways of achieving this (e.g. documenting the jk_ws_service_t definition or a shared default initialiser). -- 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]
