Tomcat JK connection problem ?
Greetings all, I have configured JK connector to bridge Apache to my Tomcat server. I am getting weird behaviour for a one particular servlet. For a random client , it seems that Apache serves some cached page.Seems it shows some kind of cached page of JSP page called 'Error.jsp'. I have placed a System.out.println(error JSP called); inside this JSP but this method does not get called. When user open the page from another browser, it serves the correct page and error moves to another client! I have placed System.out.println(POST); and System.out.println(GET); on top of doPost() and doGet() methods of the servlet ,and when this happens there's no output in the Tomcat output.(ie these methods are not called atall). When users access using 8080 port , everything works fine.Is some kind of caching involed inside JK connector ? Any tips ? My 'workers.properties' file : # Define 1 real worker using ajp13 worker.list=worker1 # Set properties for worker1 (ajp13) worker.worker1.type=ajp13 worker.worker1.host=XXX.XXX.XXX.XXX worker.worker1.port=8009 Thanks in advance. umanga - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat JK connection problem ?
2009/9/28 Ashika Umanga Umagiliya auma...@biggjapan.com Any tips ? When posting about a complex environment such as httpd + mod_jk + Tomcat, a good tip is to include version information - we're far more likely to be able to help you! - Operating system and version - Java version (and whether it's a JDK or a JRE) - Tomcat version (right down to the last digit - 6.0.20, not Tomcat 6.0) - mod_jk version - httpd version Is there anything in common between the clients that appear to be getting the cached page? All one company? All one browser? All one login to your app (if you have logins)? Regards, - Peter
Re: Tomcat JK connection problem ?
On 28.09.2009 11:08, Ashika Umanga Umagiliya wrote: Greetings all, I have configured JK connector to bridge Apache to my Tomcat server. I am getting weird behaviour for a one particular servlet. For a random client , it seems that Apache serves some cached page.Seems it shows some kind of cached page of JSP page called 'Error.jsp'. I have placed a System.out.println(error JSP called); inside this JSP but this method does not get called. When user open the page from another browser, it serves the correct page and error moves to another client! I have placed System.out.println(POST); and System.out.println(GET); on top of doPost() and doGet() methods of the servlet ,and when this happens there's no output in the Tomcat output.(ie these methods are not called atall). When users access using 8080 port , everything works fine.Is some kind of caching involed inside JK connector ? Any tips ? No, mod_jk does not do any caching. Apach eitself is able to use caching, but then you would need to activate the appropriate modules, like mod_cache, mod_mem_cache or mod_disk_cache. My 'workers.properties' file : # Define 1 real worker using ajp13 worker.list=worker1 # Set properties for worker1 (ajp13) worker.worker1.type=ajp13 worker.worker1.host=XXX.XXX.XXX.XXX worker.worker1.port=8009 I would activate the access log for Apache and for Tomcat and check, how the requests and responses move through your architecture. Regards, Rainer - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat JK connection problem ?
H Peter , Thank you for the reply. I have given in-line answers. - Operating system and version Server : Debian Lenny 64bit - Java version (and whether it's a JDK or a JRE) JDK 1.6.0_16 - Tomcat version (right down to the last digit - 6.0.20, not Tomcat 6.0) Tomcat 6 - mod_jk version 1.2.26 - httpd version Apache/2.2.9 (Debian) DAV/2 SVN/1.5.1 mod_jk/1.2.26 PHP/5.2.6-1+lenny3 with Suhosin-Patch mod_ssl/2.2.9 OpenSSL/0.9.8g Server at biggserver Port 80 Is there anything in common between the clients that appear to be getting the cached page? All one company? All one browser? All one login to your app (if you have logins)? AFAIK there's nothing common.And the application does not need to log. I am sure that this is an issue with JK ,because when accessing directly through 8080,everything works fine. Here is the link that gives the error (you have to open several browsers to get the error): http://diam-jba.jp/diam/regulationdocument Thanks in advance, umanga - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat JK connection problem ?
Sorry , full tomcat version is : Tomcat 6.0.20 **Ashika Umanga Umagiliya wrote: H Peter , Thank you for the reply. I have given in-line answers. - Operating system and version Server : Debian Lenny 64bit - Java version (and whether it's a JDK or a JRE) JDK 1.6.0_16 - Tomcat version (right down to the last digit - 6.0.20, not Tomcat 6.0) Tomcat 6 - mod_jk version 1.2.26 - httpd version Apache/2.2.9 (Debian) DAV/2 SVN/1.5.1 mod_jk/1.2.26 PHP/5.2.6-1+lenny3 with Suhosin-Patch mod_ssl/2.2.9 OpenSSL/0.9.8g Server at biggserver Port 80 Is there anything in common between the clients that appear to be getting the cached page? All one company? All one browser? All one login to your app (if you have logins)? AFAIK there's nothing common.And the application does not need to log. I am sure that this is an issue with JK ,because when accessing directly through 8080,everything works fine. Here is the link that gives the error (you have to open several browsers to get the error): http://diam-jba.jp/diam/regulationdocument Thanks in advance, umanga - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat JK connection problem ?
As far as I can see, the log file contains the same situation as when I connet to the URL with a browser. I do successfully get the main page, but the page includes two invalid references: - for style.css (should be maybe css/style.css) - and inside css/style.css which is also used in addition to the wrong style.css it has a reference to images/bg_001.png, which should likely have been a ../images/bg_001.png. Furthermore the page contains two xml headers: - !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN and later down another - !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN http://www.w3.org/TR/html4/loose.dtd; which doesn' seem right. I can't see any occurence of a caches Error.jsp, but I do see broken links which obviously send the Tomcat standard error page to the browser instead of the css file resp. the png file. Regards, Rainer On 28.09.2009 11:51, Ashika Umanga Umagiliya wrote: I managed to save the JK log file when the error occurred.Last request information in in log file contains the details for the issue. I have attached the logfile with this. Thanks in advance, umanga Rainer Jung wrote: On 28.09.2009 11:08, Ashika Umanga Umagiliya wrote: Greetings all, I have configured JK connector to bridge Apache to my Tomcat server. I am getting weird behaviour for a one particular servlet. For a random client , it seems that Apache serves some cached page.Seems it shows some kind of cached page of JSP page called 'Error.jsp'. I have placed a System.out.println(error JSP called); inside this JSP but this method does not get called. When user open the page from another browser, it serves the correct page and error moves to another client! I have placed System.out.println(POST); and System.out.println(GET); on top of doPost() and doGet() methods of the servlet ,and when this happens there's no output in the Tomcat output.(ie these methods are not called atall). When users access using 8080 port , everything works fine.Is some kind of caching involed inside JK connector ? Any tips ? No, mod_jk does not do any caching. Apach eitself is able to use caching, but then you would need to activate the appropriate modules, like mod_cache, mod_mem_cache or mod_disk_cache. My 'workers.properties' file : # Define 1 real worker using ajp13 worker.list=worker1 # Set properties for worker1 (ajp13) worker.worker1.type=ajp13 worker.worker1.host=XXX.XXX.XXX.XXX worker.worker1.port=8009 I would activate the access log for Apache and for Tomcat and check, how the requests and responses move through your architecture. Regards, Rainer - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
