Yes Andre,you are right.We do have akamai in between the client and webserver.But we afraid that there could be a performance hit when we start patching in there.We are looking for a much intuitive solution of solving this at origin or how to handle the situation better.But,do you think all the clients who uses the apapche_mod_jk setup would suffer from this problem or what would be an optimum solution that would work fine or a configuration that would have been working fine for others that you might be aware of?
Regards, Bala -----Original Message----- From: André Warnier [mailto:a...@ice-sa.com] Sent: Thursday, September 10, 2009 8:02 PM To: Tomcat Users List Subject: Re: Need Help - Mod_jk/Apache - Mutiple Content issue balakarthik.baska...@wipro.com wrote: > Yes you are right.I think I didn't mention it clearly.I am having this while > loop for writing a huge chunk of data followed by a thread that sleeps for > some time and that is where I am expecting my reply_timeout to be timed out > and the data written till the sleep of the thread is seen in the browser and > the log file. > Ok, now I do understand better, I think. There is a request. The Tomcat app starts answering (a long chunk of data), then crashes. This is simulated by your test script, which sends a long chunk of data, then sleeps (to simulate a crash). Eventually, some timeout occurs, which (may) cause another element to consider this Tomcat unresponsive, and switch the request to another one. This other one then restarts the request from the beginning. The final result being that the requesting browser first received an incomplete chunk of data from the first webapp, and now starts receiving the same data (again) from another webapp. Again intuitively, I don't know how any server-side scheme is going to solve that. When the first webapp starts answering, that Tomcat has to start sending the answer back to the client. If it then crashes, it is too late to "call it back"; the data is already on the wire to the client. It would be in my view the client's responsibility to ensure that it discards any incomplete data received. But I don't know of any browser for instance, which does that. They all start to try to display the data as soon as they have the beginning of it. I think that if you really need this, then you would have to insert some other "item" between Tomcat and the client, which acts as a proxy, and only starts sending the response to the client when it is sure that it has received and buffered a complete response from the server. But then, this "item" becomes the weak link. It could also crash.. Or else you need an applet at the client side, which does the same thing. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org Please do not print this email unless it is absolutely necessary. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
