DO NOT REPLY [Bug 26463] New: - loadbalancer fails on large (>8k) messages

[bu...@apache.org]

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

loadbalancer fails on large (>8k) messages

           Summary: loadbalancer fails on large (>8k) messages
           Product: Tomcat 4
           Version: 4.1.25
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Connector:JK/AJP (deprecated)
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: johnEllis@alumni.creighton.edu


We are using mod_jk-1.2.5 with apache 1.3.  We have 2 tomcat hosts both 
running 4.1.25.

We have quite large messages that we are receiving as posts.  As the 
loadbalancer is failing over, any message larger than 8k has only the last 
(Message size - 8k - 6) bytes sent to the tomcat instance.

Looking in the code, it seems that the message pointers are being incremented 
after the len of AJP13_MAX_SEND_BODY_SZ (which is 8k - 6) is reached.  When 
the failover connect gets the message, i am guessing that the pointer is now 
pointing to the wrong location in the message.  I tried making a copy of the 
service struct that is passed to the connectors, and restoring it around line 
340 in jk_lb_worker.c, but that did not seem to address the situation.

If jk/ajp is deprecated, does the new JK2 have a loadbalancing feature.  I 
could not find any docs on how to set that up.

thanks,

John

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org