RE: tomcat_trend.pl script is showing Unknown log entry for mod_jk
Hi Ankush, As far as I know that scripts is not really maintained any more and need a fair amount of tweaking. I might be wrong though. Regards -Original Message- From: ankush grover [mailto:[EMAIL PROTECTED] Sent: 23 September 2008 12:16 To: users@tomcat.apache.org Subject: tomcat_trend.pl script is showing Unknown log entry for mod_jk Hi friends, I am running mod_jk 1.2.26 on Centos 5.2 64-bit with Apache 2.2.3 64-bit. I am trying to generate the mod_jk statistical data through tomcat_trend.pl and tomcat_report.pl scripts but unfortunately tomcat_trend.pl script is showing Unknown log entry when I am giving the path for reading the mod_jk.log file ./tomcat_trend.pl /var/log/httpd//var/www/html/reports Output Unknown log entry: [Sun Sep 21 04:58:01 2008] worker6 webserver.example.com 0.027690 /webserver/board.jsp worker.properties JkWorkersFile /etc/httpd/conf/workers.properties JkShmSize 10M JkLogLevel info JkLogStampFormat [%a %b %d %H:%M:%S %Y] JkRequestLogFormat %w %V %T %U%q What I am able to understand is the format of the mod_jk.log differs from the script. What should be the format for mod_jk logs so that this script can read this. Regards Ankush - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
apache/modjk behaviour during shutdown
Hi I am trying to understand the behavior of our application stack during an apache shutdown. This question might not a 100% to this list but is a good place to start. I am trying to understand what the behaviour would be when I shutdown an apache that is connected via modjk to a cluster of tomcats. I was under the impression that when apache is orderly shutdown it will finish processing existing requests not excepting new ones and exit when having done so. Would the same hold true for requests that is currently being processed by the tomcat. Would apache wait for the tomcat threads send via modjk to complete before terminating them? My initial observations has been that this is not the case but I will have to do more detailed analysis to be sure whether this is true or not. Regards __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __
RE: apache/modjk behaviour during shutdown
Would the same hold true for requests that is currently being processed by the tomcat. Would apache wait for the tomcat threads send via modjk to complete before terminating them? Nope. mod_jk has no clue about Tomcat's threads. Httpd will unload (any) mod_jk module when the current request(s) is finished (even adding Connection: close to the outgoing headers). If the requests are taking too much time they are forcibly closed then, so the presumption that the current requests will be handled is only true for 'normal' requests. Regards Thanks Mladen, Is too much time a configurable parameter and what constitutes a normal request. Our application can take anything from 250ms to 2seconds to return an reply. I am guessing that requests that takes 2 seconds will probably be orphaned when the apache_httpd server is shutdown because they take to longer. Regards __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Can not fail over a web service call using mod_jk
-Original Message- From: Rainer Jung [mailto:[EMAIL PROTECTED] Sent: 09 December 2008 12:32 To: Tomcat Users List Subject: Re: Can not fail over a web service call using mod_jk Zeke schrieb: Thank you very much, Rainer! Yes. My node accept the request first, then it will return 500 if the called web service is not available ...So mod_jk can not fail over the request in this situation. Do you have some suggestion for this situation? I really hope none of the calling to my web service in my cluster will be lost. Something would need to buffer the request body. What about your web service client? Could it do a retry, when it gets an error status code? It should still have the rquest data available. The mod_jk module would put the bad worker into error state after detecting any error, so that the client retry would go to another node. Regards, Rainer From a design point of view do you feel that this is beyond the scope of mod_jk to buffer request bodies? From one point of view it does make sense to have the retry logic completely in mod_jk, but I can certainly understand the point of view to have retry logic on the client. Regards __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Can not fail over a web service call using mod_jk
-Original Message- From: Rainer Jung [mailto:[EMAIL PROTECTED] Sent: 09 December 2008 13:45 To: Tomcat Users List Subject: Re: Can not fail over a web service call using mod_jk [EMAIL PROTECTED] schrieb: From a design point of view do you feel that this is beyond the scope of mod_jk to buffer request bodies? From one point of view it does make sense to have the retry logic completely in mod_jk, but I can certainly understand the point of view to have retry logic on the client. Not completely, but it would be a serious problem to buffer the full request bodies by default. Imagine someone who does upload a DVD iso image. So it's much safer (with respect to ressource consumption) to only buffer a first chunk for the usual case, that a problem is detected early. It could be an option though, to buffer requests with a configurable limit depending on the URL. It would not be to hard to implement that, but the whole thing gets more and more complex. It might make more sense That might just be very handy. We have some network devices higher up the application stack which have request retry capabilities, it is another possible place to have retries. If retries were implemented in some form in modjk having the ability to define what a failure is would be very handy. The ability in modjk 27 to have a separate process/thread that monitors the connection pool (connection probing)makes request retry very much a boarder case in my opinion. It would probably be better to have more customization ability to exactly specify what a failure is for the connection probing watchdog thread rather than implementing request retry. Regards __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Load Balancing
Hi Dean, Still no luck, the attachement I am seeing contains the following: - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Could you define application functioning correctly what are you expecting to see and what is happening. Regards From: Dean Lonsdale [mailto:[EMAIL PROTECTED] Sent: 15 August 2007 15:29 To: Tomcat Users List Subject: Load Balancing Resend of the last mail removing signature attachments, We have built a workers.properties file to incorporate load balancing however when we use this file it would appear that it prevents the application from functioning correctly, please can anyone comment on whether the load balancing parameters are set correctly. Many thanks Unless stated otherwise above: IBM United Kingdom Limited - Registered in England and Wales with number 741598. Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __
RE: context.xml not being copied across on deployment
Hi Iain, From a previous question I asked on the list: If you use auto-deploy and you have a WAR file or directory in the webapps directory, then any path attribute you have in your Context element will be ignored (or, worse, confused and used ion some weird way). Perhaps this is a problem with your deployment. -Original Message- From: Emsley, I (Iain) [mailto:[EMAIL PROTECTED] Sent: 17 August 2007 15:21 To: users@tomcat.apache.org Subject: context.xml not being copied across on deployment Dear Tomcat users, I'm trying to get a calendaring system (which also uses Ant) to load its applications from C:\foo\apache-tomcat-5.5.17\webapps. I've set a build file at c:\docs and settings\userid\foo.build.properties which links to a foo.properties and foo.options.xml. These point to the context.xml file in catalina home\web apps\META-INF\context.xml (I've posted one the lines for the tomcat context: org.bedework.app.Events.tomcat.context.xml=/META-INF/context.xml). When I start Tomcat, the WAR files in webapps are deployed but the context.xml files are ignored (they are required as I'm changing the database from Hypersonic to MySQL). When I check the xml files in \apache-tomcat-5.5.17\conf\Catalina\localhost, I'm still getting the context for Hypersonic rather than MySQL. It appears that the WAR files are being copied in whole whilst my update is being ignored. I would be grateful for some pointers as to what else I can try to solve this issue and to learn from it for the future. Many thanks, __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
recovery_options bitmask values for mod_jk
Hi Hopefully a simple answer, the documentation says recovery_options is a bitmask but what I am unsure of is do I set the value in binary or do I use integer values? 1: don't recover if Tomcat failed after getting the request 2: don't recover if Tomcat failed after sending the headers to client 4: close the connection to Tomcat, if we detect an error when writing back the answer to the client (browser) 8: always recover requests for HTTP method HEAD (even if Bits 1 or 2 are set) 16: always recover requests for HTTP method GET (even if Bits 1 or 2 are set) I understand bit mask as: 1 0001 168421 Thus the value I want to set teh recovery_options to is: 11000. Integer equivalent would be 24. Searching the emails I have received from the list since joining shows people have used normal integer values. I would be glad if someone could clear this up. Regards __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
workers.properties confusion
Hi Another easy question to answer, hopefully... I just spend a lot of time going through this page: http://tomcat.apache.org/connectors-doc/reference/workers.html to decide which parameters we need/want to implement. However I am a bit confused between the /etc/httpd/conf/workers.properties for apache and /usr/share/tomcat/conf/workers.properties Is the documentation only for the tomcat file or is it for both files? I understand apache:/workers.properties to be the place were I setup how and to how many tomcats I will be connecting from apache and tomcat:/workers.properties to be where I specify how many tomcat instances/workers I have. We are expiercing regular as clock work problems with apache getting in a W Sending Reply state for all of the child processes and the not clearing. Currently we are using default setting for mod_jk which needs some serious tuning to at least make sure that that part of the infrastructure is working properly. Another potential issue is that we are using apache prefork. From what I have googled so far it looks like apache mpm would be better for us. We typically have one apache box sitting in front of 12 tomcats. Regards __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __
apache getting in sending reply state when connecting to tomcat
Hi I'm kind of between a rock and a hard place. We have a problem in our production system that occurs quite regularly. Apache's connections all get into a Sending Reply ( W ) state and which makes the application unresponsive. We have an apache 2.0.52 fronting 12 tomcat 5.5 all on CentOS 4.5 using mod_jk with, dare is say it, default settings. :-( We have a stripped down apache installed on each Tomcat blade and what is interesting is that when we reach this stage of all connections in W state we can access the application using the local apache on the tomcat blade using port 8080 but not access it on port 8009 using the local apache on the tomcat blade. This to me points to a connector problem. I believe that the problem is related to our mod_jk settings or lack there off and also the version we are using. What makes matters a bit difficult for me is that we are unable to recreate the problems we are seeing in production on our test systems which makes it very difficult to push out changes to production. Management is quite strict in allowing production changes, which is understandable because downtime is expensive. We are using mod_jk-1.2.22-2.0.52-linux-x86_64.so httpd-2.0.52-28.ent prefork Tomcat 5.5 Questions: ~~ * Do you agree that it is mod_jk settings? * What more information do I need or should look at to determine problems.( The developers regularly scrutinize thread dumps we make) * mod_jk docs says: mod_jk-1.2.25-httpd-2.0.59.so is for Apache 2.0.x and works with Apache 2.0.59 and later, will using httpd-2.0.52-28.ent be a problem? Settings ~~ httpd.conf ~~ IfModule prefork.c StartServers 8 MinSpareServers8 MaxSpareServers 300 ServerLimit 575 MaxClients 575 MaxRequestsPerChild 4000 workers.properties ~~ # Worker list worker.list=xml-gta,jkstatus # Worker definitions worker.xml-gta.type=lb worker.xml-gta.method=Busyness worker.xml-gta.balanced_workers= lonstct01agx,lonstct01bgx,lonstct01cgx,,lonstct01dgx,lonstct01egx,lonstc t01fgx,lonstct01ggx,lonstct01hgx,lonstct01igx,lonstct01jgx,lonstct01kgx, lonstct01lgx worker.jkstatus.type=status # Balance workers worker.lonstct01agx.port=8009 worker.lonstct01agx.host=xx.xx.xx.xx worker.lonstct01agx.type=ajp13 worker.lonstct01agx.lbfactor=1 ... worker.lonstct01lgx.port=8009 worker.lonstct01lgx.host=xx.xx.xx.xx worker.lonstct01lgx.type=ajp13 worker.lonstct01lgx.lbfactor=1 server.xml ~~ Connector port=8009 enableLookups=false redirectPort=8443 protocol=AJP/1.3 / Suggested Changes I want to make (but still need approval for) Upgrade to mod_jk .25 Change workers.properties to: workers.properties ~~ # Worker list worker.list=xml-oct-gta,jkstatus # Worker definitions worker.xml-oct-gta.type=lb worker.xml-oct-gta.method=Busyness worker.xml-oct-gta.balance_workers=longtct02c,longtct02d worker.xml-oct-gta.lock=Pessimistic worker.xml-oct-gta.max_reply_timeouts=10 worker.jkstatus.type=status # Worker Template worker.reference.port=8009 worker.reference.type=ajp13 worker.reference.lbfactor=1 worker.reference.socket_timeout=60 worker.reference.socket_keepalive=true worker.reference.connect_timeout=500 worker.reference.prepost_timeout=500 worker.reference.reply_timeout=32000 worker.reference.recovery_options=27 # 16 8 2 1 worker.reference.retries=12 # # Balance workers worker.longtct02c.reference=worker.reference worker.longtct02c.host=xx.xx.xx.xx ... (there are 10 other servers not listed here for space saving purposes) worker.longtct02d.reference=worker.reference worker.longtct02d.host=xx.xx.xx.xx Regards __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: apache getting in sending reply state when connecting to tomcat
Hi I forgot to add, that our solution at the moment is to restart apache which 9 out of 10 times solves the problems. We see connections reach almost 250 (248,249) per tomcat server on the apache box. After restart this drops down We also only see the problem when we are experiencing heavy load and it happens very quickly when it does. Regards -Original Message- From: Gerhardus Geldenhuis (GTA-LON) Sent: 29 August 2007 11:47 To: users@tomcat.apache.org Subject: apache getting in sending reply state when connecting to tomcat Hi I'm kind of between a rock and a hard place. We have a problem in our production system that occurs quite regularly. Apache's connections all get into a Sending Reply ( W ) state and which makes the application unresponsive. We have an apache 2.0.52 fronting 12 tomcat 5.5 all on CentOS 4.5 using mod_jk with, dare is say it, default settings. :-( We have a stripped down apache installed on each Tomcat blade and what is interesting is that when we reach this stage of all connections in W state we can access the application using the local apache on the tomcat blade using port 8080 but not access it on port 8009 using the local apache on the tomcat blade. This to me points to a connector problem. I believe that the problem is related to our mod_jk settings or lack there off and also the version we are using. What makes matters a bit difficult for me is that we are unable to recreate the problems we are seeing in production on our test systems which makes it very difficult to push out changes to production. Management is quite strict in allowing production changes, which is understandable because downtime is expensive. We are using mod_jk-1.2.22-2.0.52-linux-x86_64.so httpd-2.0.52-28.ent prefork Tomcat 5.5 Questions: ~~ * Do you agree that it is mod_jk settings? * What more information do I need or should look at to determine problems.( The developers regularly scrutinize thread dumps we make) * mod_jk docs says: mod_jk-1.2.25-httpd-2.0.59.so is for Apache 2.0.x and works with Apache 2.0.59 and later, will using httpd-2.0.52-28.ent be a problem? Settings ~~ httpd.conf ~~ IfModule prefork.c StartServers 8 MinSpareServers8 MaxSpareServers 300 ServerLimit 575 MaxClients 575 MaxRequestsPerChild 4000 workers.properties ~~ # Worker list worker.list=xml-gta,jkstatus # Worker definitions worker.xml-gta.type=lb worker.xml-gta.method=Busyness worker.xml-gta.balanced_workers= lonstct01agx,lonstct01bgx,lonstct01cgx,,lonstct01dgx,lonstct01 egx,lonstc t01fgx,lonstct01ggx,lonstct01hgx,lonstct01igx,lonstct01jgx,lon stct01kgx, lonstct01lgx worker.jkstatus.type=status # Balance workers worker.lonstct01agx.port=8009 worker.lonstct01agx.host=xx.xx.xx.xx worker.lonstct01agx.type=ajp13 worker.lonstct01agx.lbfactor=1 ... worker.lonstct01lgx.port=8009 worker.lonstct01lgx.host=xx.xx.xx.xx worker.lonstct01lgx.type=ajp13 worker.lonstct01lgx.lbfactor=1 server.xml ~~ Connector port=8009 enableLookups=false redirectPort=8443 protocol=AJP/1.3 / Suggested Changes I want to make (but still need approval for) Upgrade to mod_jk .25 Change workers.properties to: workers.properties ~~ # Worker list worker.list=xml-oct-gta,jkstatus # Worker definitions worker.xml-oct-gta.type=lb worker.xml-oct-gta.method=Busyness worker.xml-oct-gta.balance_workers=longtct02c,longtct02d worker.xml-oct-gta.lock=Pessimistic worker.xml-oct-gta.max_reply_timeouts=10 worker.jkstatus.type=status # Worker Template worker.reference.port=8009 worker.reference.type=ajp13 worker.reference.lbfactor=1 worker.reference.socket_timeout=60 worker.reference.socket_keepalive=true worker.reference.connect_timeout=500 worker.reference.prepost_timeout=500 worker.reference.reply_timeout=32000 worker.reference.recovery_options=27 # 16 8 2 1 worker.reference.retries=12 # # Balance workers worker.longtct02c.reference=worker.reference worker.longtct02c.host=xx.xx.xx.xx ... (there are 10 other servers not listed here for space saving purposes) worker.longtct02d.reference=worker.reference worker.longtct02d.host=xx.xx.xx.xx Regards __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ This email has been scanned by the
RE: apache getting in sending reply state when connecting to tomcat
Charles, when I say apache I mean httpd service. There is 3 different servers mentioned. * The httpd server that fronts the tomcat servers * The tomcat servers that serves the application * The httpd server, scaled down on the same physical machine as the tomcat server which we use for basic monitoring and testing. I hope that clears up any confusion. Regards -Original Message- From: Caldarale, Charles R [mailto:[EMAIL PROTECTED] Sent: 29 August 2007 14:18 To: Tomcat Users List Subject: RE: apache getting in sending reply state when connecting to tomcat From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Subject: RE: apache getting in sending reply state when connecting to tomcat I forgot to add, that our solution at the moment is to restart apache which 9 out of 10 times solves the problems. Please clarify your use of the term apache, which is a software organization with numerous products, among them httpd and Tomcat. In some instances, you seem to be referring to httpd, but in others you clearly mean Tomcat (e.g., using the local apache on the tomcat blade using port 8080). When you say you restart apache, which component are you really referring to? - Chuck THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY MATERIAL and is thus for use only by the intended recipient. If you received this in error, please contact the sender and delete the e-mail and its attachments from all computers. - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: apache getting in sending reply state when connecting to tomcat
Hi
This part is still sligtly confusing to me:
We have 575 potential connections that we can except on the httpd
server, according to my understanding mod_jk will load balance these
connections to the tomcat servers. Thus typically 48 connections per
tomcat. This does seem obviously wrong ...
We are seeing avarage amount of connections of about 245 per tomcat
server on the apache box when we reach a state were all servers are in
W state. That is about 3000 connections in total over the 12 tomcats.
This does not tally up with the default maximum of 200. Any ideas where
this additional connections comes from??
We feel confident that we don't have stale connections. Connections on
the httpd side and connections on the tomcat side tally up. lsof on the
tomcat box is also exactly the same as the netstat result.
Commands used:
[EMAIL PROTECTED] ~]# lsof|grep -i 8009 |grep -i established |grep -vi
localhost -c
75
[EMAIL PROTECTED] ~]# netstat -ant|grep 8009 |awk '{print $5}'|awk -F:
'{print $4}'|sort|uniq -c
8
1 *
75 10.100.11.225
8 127.0.0.1
Regards
-Original Message-
From: Rainer Jung [mailto:[EMAIL PROTECTED]
Sent: 29 August 2007 21:29
To: Tomcat Users List
Subject: Re: apache getting in sending reply state when
connecting to tomcat
Hi Gerhardus,
you allow 575 parallel requests with Apache. If something
gets slow and you get more and more W states, this
parallelism will really get used.
Each parallel requests needs a connection to your Tomcat
(unless it gets served directly by Apache), and each
connection to Tomcat needs a thread to handle the request.
You didn't configure the number of threads for Tomcats AJP connector.
The default is something like 200 threads. So you allow much
more incoming parallelism on Apache, than you configured on
you backend. Once you get above the 200 parallel requests,
you should see messages like all threads are busy in your
Tomcat log files.
But: This doesn't really explain, why you get into a
situation, where that many requests need to be run in
parallel. If your requests start to queue up (more W than
normally), you should do Java Thread Dumps for Tomcat
(sending kill -QUIT) which will go to catalina.out. Those
will tell you/us/your webapp developers, which parts of the
code Tomcat or more likely your webapp is getting slow in.
Java thread dumps only give a snapshot information, so it is
good to do a couple (3-5) of them a few seconds apart from each other.
Regards,
Rainer
__
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
__
-
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: apache getting in sending reply state when connecting to tomcat
Thanks for your patience, things are starting to make more sense now. Tomcat associates one thread with each incoming connection (at least the default connector) independant of it's idleness, i.e. even if there is no request coming in. The connectionTimeout parameter in the connector tells tomcat, howe long it should wait for a request, before shutting down the connection and putting back the thread into the pool of idle threads. That's the reason, why you need to adjust the parameters between httpd and Tomcat. The reason, why you have so many connections will be in some part of the webapp being to slow. This you will be able to analyze by using a Java thread dump. If no value is specified then the maximum connectors is default 200. I assumed that Tomcat would not allow more connections than 200 to be made to port 8009. Why then do we see more than 200 connections on port 8009 on the httpd and tomcat side. Is this additional connections in some kind of waiting pool that gets establised by the OS but not honoured by Tomcat? I am in the process of upgrading our production enviroment to mod_jk .25 and setting relevant time out values which will hopefully improve things or at least rule out one less potential problem. Regards __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: apache getting in sending reply state when connecting to tomcat
Hi I'm going to be a real pain, but it make no sense now... The email has been a team effort in our offices. We have included some diagrams to help illustrate our understanding or lack off. Using a simple example: 1/ Assume I have one httpd server (prefork) that can spawn a maximum of 200 children (through httpd Maxclients directive). 2/ Assume I have 1 tomcat servers that can handle 200 threads each. If I connect the apache to tomcat with mod_jk (lb) I can, in theory handle 200 concurrent connections. Now, if I change the figures 1/ Assume I have one httpd server (prefork) that can spawn a maximum of 200 children (through httpd Maxclients directive). 2/ Assume I have 4 tomcat servers that can handle 200 threads each. In this case each apache child opens a connection to each tomcat server so I have reached the maximum amount of connections each tomcat can handle. What I cannot understand is that by increasing the tomcats to 4 I now have 800 possible connections but with the above config I can only access 200 of them. If I set apache to 800 (through httpd Maxclients directive) I will open more connection to each tomcat than they can handle. Is the above senario correct? and if it is then we are not getting more throughput by adding more tomcats and it would be better to access the tomcats directly. So using a ridiculous example, if you have 100 tomcat boxes connecting to one httpd server. The the limit for amount of spawned children would still only by 200. Even though you should be able to handle 100x200 concurrent connections. Even if you take into account that for each request per second received the request will take 4 seconds to process it still does not seem effective use of the tomcat resources. A few other resulting questions: If child1, child2, child3 etc each have a connection to each tomcat, does each child also do its own load balancing or do all the children share information to do loadbalancing? Regards I don't know exactly, if that parameter changed is some versions, I simply checked one version of Tomcat. I would give it a 85% chance, that 200 is the default also for your version. Sorry I should have bee more specific I did explicitely check this limit so in our case it is definitely 200. You can: learn about the jmxproxy functionality inside the Tomcat manager webapp to look up the actual values used during runtime http://tomcat.apache.org/tomcat-5.5-doc/manager-howto.html use qry=*:* to get a dump of all MBeans, and then search for 8009 and you will find the right value. You can also use netstat -an in a more fine grained way, by not dropping the last column (connection state) to find out, if all connections are actually established, or maybe in SYN_SENT etc. I am in the process of upgrading our production enviroment to mod_jk .25 and setting relevant time out values which will hopefully improve things or at least rule out one less potential problem. Regards Yes timeouts and increased thread numbers inside Tomcat will be good. To find out, why there are so many requests in progress you (resp. your webapp developers) really need to take a look at some Java thread dumps of your Tomcat processes. Regards, Rainer __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Differentiate Tomcat 6.x with Tomcat 5.x
Hi This webpage should answer most of your questions, http://tomcat.apache.org/whichversion.html Regards -Original Message- From: MOHD SUFIAN BIN ZAKARIAH ZAKARIAH [mailto:[EMAIL PROTECTED] Sent: 03 September 2007 10:09 To: users@tomcat.apache.org Subject: Differentiate Tomcat 6.x with Tomcat 5.x Hello I have something question about Tomcat version. I want to know that Tomcat 6.x have difference with Tomcat 5.x and other. Can give explaination about function both of Tomcat. Thank you for all cooperation. - - Bosan dengan spam? Mel Yahoo! memiliki perlindungan spam yang terbaik http://my.mail.yahoo.com/ __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Understanding jvmRoute usage
Hi I am going through all of the potential settings I can set for mod_jk and am not sure how the route property in mod_jk might be used. I understand that this help to differentiate different servers in a load balanced cluster to prevent sessions getting mixed up and to do session stickyness. If however this defaults to machine name this would only be used when running two instances of tomcat on the same physical box. It then seems to me that the only time you would really use jvmroute is when you have multiple instances of tomcat running on the same box. Does anyone know of other scenarios when this might be usefull or imaginative ways of using this. Regards __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __
Logformat for mod_jk logs
Hi Does anyone know if the script tomcat_trend.pl requires a specific JkRequestLogFormat string. Doing a search through the list archives on my local machine I found the following two settings being used: JkRequestLogFormat %b %w %V %T %r JkRequestLogFormat %w %V %T But I am not sure what this script that comes with mod_jk actually requires. Regards __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __
RE: Understanding jvmRoute usage
Thanks, So do you assign a different jvmroute to each webapp? That would potentially be a better way to run multiple versions of the same app rather than running different Tomcats. That would be a nice way to switch quickly between different versions. Currently we have quite a painfull method for switching applications. Regards -Original Message- From: Peter Stavrinides [mailto:[EMAIL PROTECTED] Sent: 12 September 2007 10:41 To: Tomcat Users List Subject: Re: Understanding jvmRoute usage I use this parameter because I needed to integrate multiple web apps on the same backend server using mod_proxy and mod_rewrite into the same namespace(of the apache front end). We point to the server and configure a sticky session so we don't have to run everything in the root context, magic !! __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Logformat for mod_jk logs
Hi Using the format: JkRequestLogFormat %w %V %U %s %T %B %H %m I still only get empty graphs. Granted I have only run it for one day. I am currently running it on a demo system with fairly high load and will do some analysis after the weekend. It is just frustrating to not know what format the script is expecting and trying to debug over days. Unfortunatel my perl knowledge is low otherwise I would have tried to seem from the code. The author of the scripts has not put his contact details in the header... Regards -Original Message- From: fredk2 [mailto:[EMAIL PROTECTED] Sent: 11 September 2007 15:58 To: users@tomcat.apache.org Subject: Re: Logformat for mod_jk logs hi I have not used it in long while but i think it required: JkRequestLogFormat %w %V %U %s %T %B %H %m Rgds - Fred Gerhardus.Geldenhuis wrote: Hi Does anyone know if the script tomcat_trend.pl requires a specific JkRequestLogFormat string. Doing a search through the list archives on my local machine I found the following two settings being used: JkRequestLogFormat %b %w %V %T %r JkRequestLogFormat %w %V %T But I am not sure what this script that comes with mod_jk actually requires. Regards __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: 2 Tomcat instances
Hi Andrew, I would suggest increasing log level for Tomcat, mod_jk and apache. Have a look at catalina.out to see if it logged why your application crashed. It would also help if you could define crash a bit more clearly, state the exact behaviour. If the tomcat/java have not completely died you can issue a kill -3 for the tomcat process to dump your applications status. Regards -Original Message- From: Andrew Hole [mailto:[EMAIL PROTECTED] Sent: 17 September 2007 14:54 To: Tomcat Users List Subject: 2 Tomcat instances Hello! I've two tomcat instantes and an apache web server with mod_jk. Mod_jk balance request to each tomcat. Think on following situation; - TomcatA and TomcatB up - I make a request to Apache that redirects to TomcatA. I'm editing text on JSP (lot of input texts). In this moment TomcatA craches. What's happen when I click on submit button? What you suggest to solve this situation? Thanks a lot __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat shudown does not kill java process
Hi Probably not your problem but worth mentioning. If you options like: JAVA_OPTS=$JAVA_OPTS -Dcom.sun.management.jmxremote.port=5001 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false that is CATALINA specific you should change it to CATALINA_OPTS=-Dcom.sun.management.jmxremote.port=5001 -Dcom.sun.management.jmxremote.ssl=false -Dcom.sun.management.jmxremote.authenticate=false Otherwise the shutdown script that needs to shutdown your server never gets started because there is a port conflict. Regards -Original Message- From: raj kumar [mailto:bprajkumar...@gmail.com] Sent: 17 November 2009 10:01 To: users@tomcat.apache.org Subject: Tomcat shudown does not kill java process Hi friends, I am currently using Tomcat( jakarta-tomcat-5.0.28). When i shutdown the tomcat server from my unix platform using ./shutdown.sh the java process is not getting closed.I need to close the process explicitly. Please help me in this regard. Thanks, Phani. __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: How to get java process id of a user running tomcat
Hi Have a look at the Redhat/Centos startup scripts to see how they do that. If you are running a other linux os then use ps and look for java processes. Normally the java process will have a catalina param somewhere so that is usefull to grep for. Regards -Original Message- From: raj kumar [mailto:bprajkumar...@gmail.com] Sent: 02 December 2009 06:30 To: users@tomcat.apache.org Subject: How to get java process id of a user running tomcat Hi friends, When i ran tomcat and shut it down my java process is not closing along with shutdown.i need to kill it explicitly. So I would like to know how to identify the java process of the logged in user who started the server. so that i can kill the process id from the shutdown.sh script itself. Please help me. Tomcat: jakarta-tomcat-5.0.28 Java : j2sdk1.4.2 OS: SunOS Thanks, Phani. __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: How to get java process id of a user running tomcat
Hi Me being the one who made the ridiculous suggestion of using ps, am now enlightened and will be using jps -mlv and spreading the word... That being said is there any opinions about the soundness of using the Redhat/Centos startup/shutdown script for Tomcat? Regards -Original Message- From: Christopher Schultz [mailto:ch...@christopherschultz.net] Sent: 02 December 2009 20:40 To: Tomcat Users List Subject: Re: How to get java process id of a user running tomcat -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Phani, On 12/2/2009 1:30 AM, raj kumar wrote: When i ran tomcat and shut it down my java process is not closing along with shutdown. See others' responses for why you should have to do this. Otherwise... i need to kill it explicitly. So I would like to know how to identify the java process of the logged in user who started the server. so that i can kill the process id from the shutdown.sh script itself. You won't be using the shutdown.sh script to kill Tomcat unless you hack it up to do that. I'd recommend against that. What I would recommend is using the CATALINA_PID environment variable helpfully documented in bin/catalina.sh: # Environment Variable Prequisites [...] # CATALINA_PID(Optional) Path of the file which should contains # the pid of catalina startup java process, when # start (fork) is used Try setting this environment variable to something like /var/run/tomcat.pid and you should get a file in that location containing the pid of the Java process started by Tomcat. Then, you can do something like: $ kill -9 `cat /var/run/tomcat.pid` Forget all these ridiculous suggestions of running 'ps' and grepping the output for all kinds of crazy strings. That may or may not work at all. The above strategy was intended by the Tomcat developers to be used to capture the PID of the Java process, so go ahead and use that. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksW0KwACgkQ9CaO5/Lv0PA7uQCgxBiy3snTbF49e8FXPp/+qARn qncAoI4/CLEItiHOiZxCioRfpHcCiGZ5 =AP2a -END PGP SIGNATURE- __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __
RE: How to get java process id of a user running tomcat
Thanks for the reply, Out of interest the man page for jps states: NOTE: This utility is unsupported and may not be available in future versions of the JDK. It is not currently available on Windows 98 and Windows ME platforms. This might just be a entry that has not been removed... and the utility is supported... and available in future versions. -Original Message- From: Pid [mailto:p...@pidster.com] Sent: 03 December 2009 17:37 To: users@tomcat.apache.org Subject: Re: How to get java process id of a user running tomcat On 03/12/2009 17:09, gerhardus.geldenh...@gta-travel.com wrote: Hi Me being the one who made the ridiculous suggestion of using ps, am now enlightened and will be using jps -mlv and spreading the word... That being said is there any opinions about the soundness of using the Redhat/Centos startup/shutdown script for Tomcat? No idea how it works, but presumably it was written to shutdown the server, ergo it should be reasonable to use it as intended. If Tomcat doesn't stop, find out why. p __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __
server.xml formatting guide
Hi Just wondering if there is any standard or recommendation for the formatting of server.xml config file for tomcat. Configuring properties for mysql jdbc driver is a good case in point: Resource auth=Container description=MySQL Datasource name=jdbc/MySqlDataSource type=javax.sql.DataSource driverClassName=com.mysql.jdbc.Driver url=jdbc:mysql://10.10.10.10,20.20.20.20:3306/database1?failOverReadOnl y=falseamp;autoCommit=trueamp;secondsBeforeRetryMaster=30 username=user password=password initialSize=40 You have the standard properties that can be set as above but then the mysql specific properties requires to be appended to the connection string as above or in the following format: ResourceParams name=jdbc/gtaMySqlDataSource parameter nameuseUsageAdvisor/name valuetrue/value /parameter /ResourceParams The above format is in a lot less readable in my opinion but I prefer it over appending values to a connection string. The following format also seems to be quite readable: Connector port=8080 maxHttpHeaderSize=8192 maxThreads=1000 minSpareThreads=25 maxSpareThreads=75 enableLookups=false redirectPort=8443 acceptCount=100 connectionTimeout=2 disableUploadTimeout=true / Regards __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __
Strange characters seen in RR and Cd columns on jkserver-status page after upgrading modjk to .28
Hi We have upgraded our modjk from .26 to .28 using mod_jk-1.2.28-httpd-2.2.X.so obtained from http://../tomcat-connectors/jk/binaries/linux/jk-1.2.28/x86_64/ We are running Server version: Apache/2.2.3 Server built: Nov 12 2008 10:40:14 CentOS release 5.2 (Final) After upgrading we are seeing random characters in the RR an Cd columns on the jkserver-status page. eg o%2B o+ Upgrade were done by stopping httpd. Copying new modjk to /etc/httpd/modules/ Editing /etc/httpd/conf.d/modjk.conf to reflect new version. Requests are being served but the strange characters and there origin a bit troubling. Our workers.properties looks as follows: ( There is actually 12 workers but I have removed most to simplify config) # Worker list worker.list=xml-gta,jkstatus # Worker definitions # main loadbalancer worker worker.xml-gta.type=lb worker.xml-gta.max_reply_timeouts=10 #worker.xml-gta.sticky_session=false worker.xml-gta.retries=6 worker.xml-gta.method=Busyness worker.xml-gta.balance_workers=worker1, worker2 # status page worker worker.jkstatus.type=status # Worker Reference worker.reference.port=8009 worker.reference.type=ajp13 worker.reference.lbfactor=1 worker.reference.socket_timeout=0 worker.reference.socket_keepalive=true worker.reference.connect_timeout=5000 worker.reference.prepost_timeout=0 worker.reference.reply_timeout=0 worker.reference.retries=6 worker.reference.recovery_options=27 worker.reference.connection_pool_timeout=600 worker.reference.connection_pool_size=2 worker.reference.ping_mode=A worker.reference.ping_timeout=5000 worker.reference.retry_interval=60 # Balance workers worker.worker1.reference=worker.reference worker.worker1.host=10.10.10.10 worker.worker2.reference=worker.reference worker.worker2.host=10.10.10.11 Regards __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __
RE: Strange characters seen in RR and Cd columns on jkserver-status page after upgrading modjk to .28
-Original Message- From: André Warnier [mailto:a...@ice-sa.com] Sent: 11 December 2009 17:43 To: Tomcat Users List Subject: Re: Strange characters seen in RR and Cd columns on jkserver-status page after upgrading modjk to .28 gerhardus.geldenh...@gta-travel.com wrote: Hi We have upgraded our modjk from .26 to .28 using mod_jk-1.2.28-httpd-2.2.X.so obtained from http://../tomcat-connectors/jk/binaries/linux/jk-1.2.28/x86_64/ We are running Server version: Apache/2.2.3 Server built: Nov 12 2008 10:40:14 CentOS release 5.2 (Final) After upgrading we are seeing random characters in the RR an Cd columns on the jkserver-status page. eg o%2B o+ That kind of thing triggers an immediate suspicion regarding a mismatched character set/encoding somewhere. I am not familiar at all with JSP pages, but could it be that during the update, you also customized some JSP pages, with an editor ? Are they really random characters (e.g. noise), or would-be real characters being replaced by the cabalistic signs above ? It does seem to be random... i have seen a lot of different characters appearing in these fields which change occasionaly as I refresh th jkserver-status page. I am going to hunt down character encodings on Monday. It baffles me because modjk is the only change that has happend. Maybe the .28 is just better at pointing out mistakes thats been there in the past. Best Regards __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __
RE: Strange characters seen in RR and Cd columns on jkserver-status page after upgrading modjk to .28
-Original Message- From: Rainer Jung [mailto:rainer.j...@kippdata.de] Sent: 12 December 2009 15:51 To: Tomcat Users List Cc: Gerhardus Geldenhuis (GTA-LON) Subject: Re: Strange characters seen in RR and Cd columns on jkserver- status page after upgrading modjk to .28 On 11.12.2009 18:32, gerhardus.geldenh...@gta-travel.com wrote: Hi We have upgraded our modjk from .26 to .28 using mod_jk-1.2.28-httpd-2.2.X.so obtained from http://../tomcat-connectors/jk/binaries/linux/jk-1.2.28/x86_64/ We are running Server version: Apache/2.2.3 Server built: Nov 12 2008 10:40:14 CentOS release 5.2 (Final) After upgrading we are seeing random characters in the RR an Cd columns on the jkserver-status page. eg o%2B o+ Upgrade were done by stopping httpd. Copying new modjk to /etc/httpd/modules/ Editing /etc/httpd/conf.d/modjk.conf to reflect new version. Requests are being served but the strange characters and there origin a bit troubling. Our workers.properties looks as follows: ( There is actually 12 workers but I have removed most to simplify config) # Worker list worker.list=xml-gta,jkstatus # Worker definitions # main loadbalancer worker worker.xml-gta.type=lb worker.xml-gta.max_reply_timeouts=10 #worker.xml-gta.sticky_session=false worker.xml-gta.retries=6 worker.xml-gta.method=Busyness worker.xml-gta.balance_workers=worker1, worker2 # status page worker worker.jkstatus.type=status # Worker Reference worker.reference.port=8009 worker.reference.type=ajp13 worker.reference.lbfactor=1 worker.reference.socket_timeout=0 worker.reference.socket_keepalive=true worker.reference.connect_timeout=5000 worker.reference.prepost_timeout=0 worker.reference.reply_timeout=0 worker.reference.retries=6 worker.reference.recovery_options=27 worker.reference.connection_pool_timeout=600 worker.reference.connection_pool_size=2 worker.reference.ping_mode=A worker.reference.ping_timeout=5000 worker.reference.retry_interval=60 # Balance workers worker.worker1.reference=worker.reference worker.worker1.host=10.10.10.10 worker.worker2.reference=worker.reference worker.worker2.host=10.10.10.11 Regards It's a known problem. There's an open Bugzilla for that issue. It seems you need at least around 8 worker for it to happen and I suspect it has to do with webserver restarts (apachectl graceful or apachectl restart). Unfortunately I don't yet fully understand the reasons, but noone has reported an operational problem resulting our of it, like stickyness or load balancing being broken. Of course we need to fix it ... Can you confirm it happens only after restarting? And yes, it would be nice if your could build from the sources yourself and double check the problem is still there. Regards, Rainer Thank you for all the replies. I upgraded the httpd server to the latest CentOS version which is: Name : httpd Arch : x86_64 Version: 2.2.3 Release: 31.el5.centos.2 I also did a custom compile of modjk. The problem persist despite these changes and is not related to only restarts but persists even if the httpd service is completely stopped and then started again. We do not see the problem on a similar configured httpd server with only 5 workers which seems to corroborate the 8 worker threshold. If there is any debugging scripts or log files that I can attach to the bugzilla then please let me know and I will happily do so. Regards __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __
RE: Load balancing questions
Hi Ghassan, It looks like you might be using a default/old version of modjk. I would recommend as a start to either download the latest binary release or compile a custom version for your distribution. It is really straightforward to do the compile and everything you need to know is in the documentation and readme files. You can download the latest version here: http://tomcat.apache.org/download-connectors.cgi Regards -Original Message- From: assan alhamoud [mailto:hamoudas...@gmail.com] Sent: 29 December 2009 16:18 To: Tomcat Users List Subject: Re: Load balancing questions Hello Mark , we are using apache Server version: Apache/2.2.11 (Unix) we use mod_jk.so module jboss-3.2.5 Tomcat5 and jrockit-jdk1.4.2_19 at your disposal if you need more information Regards, Ghassan __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Isolating slow and fast connections using apache/modjk
Hi We have an apache server that load balances two types of applications across different stacks of tomcats. We have a tomcat stack for requests that processes very quickly, lets call this stack A and a tomcat stack for slower running request(different type of application) named stack B. We limit connections on the apache to protect the underlying layers eg: ServerLimit 5 ThreadLimit 10 StartServers 5 ThreadsPerChild 10 MinSpareThreads 10 MaxClients 50 MaxSpareThreads 50 However if stack A or B misbehave and eat up all of the available apache connections it can cause a denial of service for the other stack that is on the same apache. My question really is where I should be doing the isolation. I am not sure whether I can achieve this in modjk or whether I should rather be running separate apache instances for tomcat stack A and B. I considered using virtual hosts but I believe they would still share the overall amount of threads as defined above. After writing this I think the question is probably more relevant on an apache list but because we are using modjk and tomcat I thought I would ask anyway. Regards __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
disable behaviour for a worker in modjk
Hi We are interested to know what the exact behaviour of modjk is with regards to current running requests when you disable a worker in the web interface. Does it drop all requests currently being processed by that worker or would it wait for requests to be finalized? The worker is part of a load balancer group of servers. We believe that to disable a worker in modjk (part of a loadbalancer group) before undeploying/deploying an application in tomcat is a cleaner method than relying on modjk to pickup unavailability of the application. Regards __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: mod_jk - load balancing
Hi Andrew, It will mark a worker as down and only send requests to working workers. There is a separate thread that checks the availability of all workers in an configurable time period which will mark the worker as available/functioning again when it becomes available, where after it will receive requests again. This is new functionality in the latest version of modjk(.27) I am not sure whether the request that determined the unavailability of the worker will be retried though, I don't think so. There has been a previous thread in the list that discussed retrying requests and the caching of request. I believe the conclusion was that it would be possible to implement but not necessarily simple. Regards -Original Message- From: Andrew Hole [mailto:andremailingl...@gmail.com] Sent: 21 January 2009 11:14 To: Tomcat Users List Subject: mod_jk - load balancing Hi Guys! What is the behavior of mod_jk if one of the workers stops? Mod_jk stops to send requests to that worker? Or it retries at each request and only after determine that the worker is down , it sends the request to the fine worker ? # -- # Load Balancer worker # -- worker.appbalancer.type= lb worker.appbalancer.balanced_workers= wk1,wk2 # # First worker # worker.wk1.port= 7001 worker.wk1.host= 10.250.14.43 worker.wk1.type= ajp13 worker.wk1.cache_timeout=600 worker.wk1.socket_timeout=5 # # Second worker # worker.wk2.port= 7001 worker.wk2.host= 10.250.14.44 worker.wk2.type= ajp13 worker.wk2.cache_timeout=600 worker.wk2.socket_timeout=5 Thanks __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
JMX Controlpanel Application
Hi I was just wondering if anyone can recommend a open source that one can use to build control panels based on jmx properties published by the jvm or your own application. We have monitoring software that can alert us when some jmx values exceeds a threshold but I would like to see a tool where I can easily collate different servers and be able to connect a button to a jmx action. (apologies if I don't use the correct jmx terminology). I was thinking something like JMX RAD(Rapid Application Development) Regards __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: AJP vs HTTP connectors?
-Original Message- From: André Warnier [mailto:a...@ice-sa.com] Sent: 03 February 2009 19:35 To: Tomcat Users List Subject: Re: AJP vs HTTP connectors? Hi. Maybe slightly off-topic, but having a moment of blues and lack of inspiration/motivation about working on what I should really be working on, and just in the spirit of communicating a user experience... We have also been very happy with modjk and it has always just worked for us. It allows us a lot of configuration flexibility as well as the ability to programmatically stop start load balancer worker members via the web interface. I have utilized this to write a deployment script that disables a node while upgrading it giving us zero downtime and zero errors. On a good day we process about 7M transactions on one of our clusters and modjk works don't even break a sweat under this volume. CPU usage is also so low as to be legible on the apache host. I believe modjk is also the recommended connector by JBoss for JBoss-Apachehttpd interaction. The support on the list is excellent. Regards __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: mod_jk
1) As far as I know, no, mod_jk does not read workers.properties dynamically. 2) Yes and no, it will not send a request unless communication has been established with the worker, it may happen that the worker fails, or someone shut it down. Depending on how you configure the workers and the number of workers, it can retry the request and/or try a different worker. Mod_jk will mark the worker on error when it does not respond, and it will try again after a configurable time -but it tries again with an actual request-. It would be really nice if you could test availability of a node with a configurable request instead of a live production request... (hint, hint) Regards __ This email has been scanned by the MessageLabs Email Security System. For more information please visit http://www.messagelabs.com/email __ - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
