Custom response header not working because of Content Length

2009-08-10 Thread Anantha Padmanabha
I'm using tomcat 6.0.18. I added a filter that adds a custom response header by doing setIntHeader/addIntHeader, but it didnt work. I debugged,looked at source and figured out that the place where its not working. Before adding headers, there is a check like this: public boolean isAppCommitted()

Re: Custom response header not working because of Content Length

2009-08-10 Thread Anantha Padmanabha
(...) } Expect failure to occur. (unless you are sending less than 8k in the response) -Tim Anantha Padmanabha wrote: I'm using tomcat 6.0.18. I added a filter that adds a custom response header by doing setIntHeader/addIntHeader, but it didnt work. I debugged,looked at source and figured

Re: Custom response header not working because of Content Length

2009-08-10 Thread Anantha Padmanabha
, On 8/10/2009 11:45 AM, Anantha Padmanabha wrote: I'm using struts2 application. I want to add some latencies [say mysql, our components and tomcat itself] to header, so that I can print this in Apache logs. Then looking at single apache log file, I would then be able to see what took

Re: what exactly happens when timeouts are set and tomcat has outofmemory errors.

2009-08-05 Thread Anantha Padmanabha
Madhuri, Its better to use max_reply_timeouts also in config so that LB does not mark a worker as 'down' once in a while. We dont use socket_connect_timeout and similar config you are mentioning had worked fine while we did OutOfMemory testing as far as I remember. If someone is not looking at