Issue with Apache 1.3 + Tomcat 5.5 + Mod JK 1.2.10
Hi All, We have a production server with 2 Apache in Front-End and one Tomcat as Application server setup with sticky sessions and a firewall in between. Apache communicates with Tomcat over 8009 port. My application is using JDK 1.4.2_01 and its a struts based application. We have been using 4.0.6 for the past 2 years and this was working perfectly fine. Last week we upgraded the Tomcat version to 5.5 and we are running into problems. Users are experiencing "A page cannot be displayed message" quite often and there is no change in whatsoever except for Tomcat Upgradation. Any help or thought process would be highly appreciated. ..Raj Worker Properties worker.list=worker1 worker.worker1.port=8009 worker.worker1.host=10.10.20.10 worker.worker1.type=ajp13 worker.worker1.lbfactor=1 worker.worker1.socket_keepalive=1 worker.worker1.socket_timeout=15 worker.worker1.recycle_timeout=60 worker.worker1.retries=3 ** Tomcat AJP connector properties **
Re: RE: Issue with Apache 1.3 + Tomcat 5.5 + Mod JK 1.2.10
I quickly looked at my Tomcat 4.0.6 settings. It was also having AJP 1.3 connector only. Please have a look at this: - *** Tomcat 4.0.6 *** Please let me know if I am missing anything. Thanks & Regards, ..Raj On Wed, 07 Dec 2005 Duan,Nick wrote : >Well, the problem seems to be that you were using AJP 1.2 on the apache >site whereas tomcat was configured with AJP 1.3 (default for 5.5). > >Interim solution: reconfigure tomcat to use AJP 1.2. >Best solution: Upgrade Apache to version 2 and AJP to 1.3. > >ND > >-Original Message- > From: Raja Neravati [mailto:[EMAIL PROTECTED] >Sent: Wednesday, December 07, 2005 1:04 PM >To: users@tomcat.apache.org >Subject: Issue with Apache 1.3 + Tomcat 5.5 + Mod JK 1.2.10 > >Hi All, > >We have a production server with 2 Apache in Front-End and one Tomcat as >Application server > >setup with sticky sessions and a firewall in between. Apache >communicates with Tomcat over > >8009 port. My application is using JDK 1.4.2_01 and its a struts based >application. > >We have been using 4.0.6 for the past 2 years and this was working >perfectly fine. Last week > >we upgraded the Tomcat version to 5.5 and we are running into problems. >Users are > >experiencing "A page cannot be displayed message" quite often and there >is no change in whatsoever except for Tomcat Upgradation. > >Any help or thought process would be highly appreciated. > >..Raj > > >Worker Properties > >worker.list=worker1 >worker.worker1.port=8009 >worker.worker1.host=10.10.20.10 >worker.worker1.type=ajp13 >worker.worker1.lbfactor=1 >worker.worker1.socket_keepalive=1 >worker.worker1.socket_timeout=15 >worker.worker1.recycle_timeout=60 >worker.worker1.retries=3 > >** >Tomcat AJP connector properties >** > >minSpareThreads="100" maxThreads="300" maxSpareThreads="80" >acceptCount="60" >debug="0" connectionTimeout="-1" /> > >- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] >
Re: Re: Issue with Apache 1.3 + Tomcat 5.5 + Mod JK 1.2.10
I can try tuning this on the servers. But as I told in my first email, this wierd problem started happening only after migrating to Tomcat 5.5. So if these were to create a problem, I should have faced it in 4.0.6 also - Right. ..Raj On Thu, 08 Dec 2005 Mladen Turk wrote : >Raja Neravati wrote: >>worker.worker1.recycle_timeout=60 > >Remove this directive. > >>worker.worker1.retries=3 >> >> >>>minSpareThreads="100" maxThreads="300" maxSpareThreads="80" acceptCount="60" >>debug="0" connectionTimeout="-1" /> > >maxThreads should be equal to MaxClients in httpd.conf. If it's smaller >then set connectionTimeout="6" and add: > >worker.worker1.connect_timeout=6 >worker.worker1.prepost_timeout=6 > >The later would be recomended if you have firewall between mod_jk >and Tomcat. > >And of course, use the latest stable mod_jk (1.2.15) >If you look at the: >http://tomcat.apache.org/connectors-doc/changelog.html >You will see that couple of things were fixed since 1.2.10 :) > >Regards, >Mladen. > >- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] >
Re: Which is better Option
You cannot define by these parameters which should be the best, because you need to consider lot of other factors as well. But with the given information by you this is what my opinion would be: - 1. Using a servlet would be a request/response mechanism and you make user wait for response. As you are saying that this is a bulk data process, I am not sure if your end user wants to wait for response. 2. Using JMS would provide you a asynchronous mechanism of decoupling your transaction processing. So you should provide user a status id of the transaction where he can come back and browse for the status. Hope this helps you in making a better judgement. RS On Mon, 19 Dec 2005 Karthik wrote : >Hi Form > > Please somebody specify > > Which Option [ advantages /limitations ] is Better ? > >1) Using a Servlet to created a seperate Thread for processing a Bulk DB >Task [ Off the limits of session time] >2) Using JMS to handle the Bulk DB Task. > >with regards >Karthik > > >- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] >
Re: RE: Which is better Option
Karthik, I sent a reply yesterday on this. Did you not receive it ? RS On Tue, 20 Dec 2005 Karthik wrote : > > >Hi Form > > > *Which Option [ advantages /limitations ] is Better ?* > > Certenly yes ,but need more clarifications [ assuming running on same >JVM ] > > > > with regards >Karthik > >-Original Message- > From: Tim Funk [mailto:[EMAIL PROTECTED] >Sent: Monday, December 19, 2005 7:18 PM >To: Tomcat Users List >Subject: Re: Which is better Option > > >jms - JMS can live in the same JVM or be moved to a new JVM without changing >any servlet code. (Only some config changes) > > >-Tim > >Karthik wrote: > > > Hi Form > > > > Please somebody specify > > > > Which Option [ advantages /limitations ] is Better ? > > > >1) Using a Servlet to created a seperate Thread for processing a Bulk >DB > > Task [ Off the limits of session time] > >2) Using JMS to handle the Bulk DB Task. > > >- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > >-- >No virus found in this incoming message. >Checked by AVG Free Edition. >Version: 7.1.371 / Virus Database: 267.14.1/206 - Release Date: 12/16/2005 > > > >- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > >- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] >
