Tomcat processes
Hi everyone, I have a question related to the scalability and performance of Tomcat. Typically, when tomcat gets started, it creates one process that spawns all the threads required to answer the requests for all the deployed web applications. Let's assume that I have 6 distinct web applications to deploy on a tomcat instance. If tomcat runs on a single high end server machine (with multi CPU), I am wondering which approach would scale better: 1) launch tomcat once with the 6 web applications (the regular way) 2) create two server.xml files (one server.xml including 3 web apps, and another one containing the remaining 3), and start two tomcat instances (running on different port obviously) on the same machine. 3) Follow approach 2 except that each tomcat instance contains all 6 web apps (and some load balancer is put in front). In short, I am wondering if having multiple tomcat processes running on a multi CPU box would scale better than having a single tomcat process dealing with everything. Is there a way to tune up the number or tomcat processes from server.xml or elsewhere? I could not find anything related to the number of processes to spawn at all. In some app server, it is possible to create several process for the same application. Is there anything similar in Tomcat? Best regards, Iannis
RE: Tomcat processes
Generally speaking, one process with a lot of threads should perform better than distributing the threads among multiple processes because you're not doing as much context switching and it's more efficient on caches. J. Ryan Earl Systems/Network Engineer dynaConnections Corporation 512.306.9898 -Original Message- From: Iannis Hanen [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 04, 2005 12:01 PM To: tomcat-user@jakarta.apache.org Subject: Tomcat processes Hi everyone, I have a question related to the scalability and performance of Tomcat. Typically, when tomcat gets started, it creates one process that spawns all the threads required to answer the requests for all the deployed web applications. Let's assume that I have 6 distinct web applications to deploy on a tomcat instance. If tomcat runs on a single high end server machine (with multi CPU), I am wondering which approach would scale better: 1) launch tomcat once with the 6 web applications (the regular way) 2) create two server.xml files (one server.xml including 3 web apps, and another one containing the remaining 3), and start two tomcat instances (running on different port obviously) on the same machine. 3) Follow approach 2 except that each tomcat instance contains all 6 web apps (and some load balancer is put in front). In short, I am wondering if having multiple tomcat processes running on a multi CPU box would scale better than having a single tomcat process dealing with everything. Is there a way to tune up the number or tomcat processes from server.xml or elsewhere? I could not find anything related to the number of processes to spawn at all. In some app server, it is possible to create several process for the same application. Is there anything similar in Tomcat? Best regards, Iannis - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Lots of seemingly dead tomcat processes
Hi, If you're using the top command, those are not processes, they're threads within the same (one) JVM process. That's normal and expected. The threads may be active (servicing a request), or idle waiting for one. In the idle state, they consume negligible system resources. To configure how many threads Tomcat creates, check out the maxThread/minThreads/maxSpareThreads and related parameters on the Connector element in Tomcat's Configuration Reference documentation. Yoav Shapira http://www.yoavshapira.com -Original Message- From: Andrew Garrett [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 24, 2004 7:24 PM To: [EMAIL PROTECTED] Subject: Lots of seemingly dead tomcat processes Hi All. I've got a bit of an issue with a tomcat installation - I have an ever increasing number of processes, and the system users complain of intermittant slow performance. When a particular request is taking a long time (generally not responding at all - timing out after a couple of minutes) a page-refresh will generally generate a response in a normal time frame (on the order of 1-2 seconds). To me, this is symptomatic of a particular request hitting a dead tomcat process, while the refresh (being a different request) hits a different tomcat process, which responds in a more normal time. I'm a sys-admin type, not a developer, and my tomcat-foo is reasonably weak (but getting stronger, the more I do with it, of course). The system is running on a dual processor 2.8 GHz Xeon box, with 4 gig of ram. Base OS is Debian GNU/Linux I'm using the JRockit JVM, and Tomcat 5.0.27 The JVM and tomcat are in a chroot jail The tomcat server is making SOAP calls to another machine, and talking directly to an MS-SQL box - both the machine to which it makes the SOAP calls and the MS-SQL box show no indications of load. When tomcat is freshly restarted, I have 44 tomcat processes (ps ax | grep jrockit | wc -l). Over time (a number of days) this increases, until it hits around 245 processes, and it goes no higher than this. What I'm looking for is some sort of solution - either some tomcat setting I'm unfamiliar with that might be causing this, or some way outside of Tomcat I can put a band-aid style fix in place - restarting tomcat every X days, but that's uglier than I'd like - I'd far rather identify and fix the problem, than do scheduled restarts. Any assistance or suggestions that any kind soul can offer would be greatly appreciated. Thanks. Andrew -- They sicken of the calm; http://scroll.redemption.co.nz/ That know the storm. http://www.gadgets-weblog.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Lots of seemingly dead tomcat processes
Hi All. I've got a bit of an issue with a tomcat installation - I have an ever increasing number of processes, and the system users complain of intermittant slow performance. When a particular request is taking a long time (generally not responding at all - timing out after a couple of minutes) a page-refresh will generally generate a response in a normal time frame (on the order of 1-2 seconds). To me, this is symptomatic of a particular request hitting a dead tomcat process, while the refresh (being a different request) hits a different tomcat process, which responds in a more normal time. I'm a sys-admin type, not a developer, and my tomcat-foo is reasonably weak (but getting stronger, the more I do with it, of course). The system is running on a dual processor 2.8 GHz Xeon box, with 4 gig of ram. Base OS is Debian GNU/Linux I'm using the JRockit JVM, and Tomcat 5.0.27 The JVM and tomcat are in a chroot jail The tomcat server is making SOAP calls to another machine, and talking directly to an MS-SQL box - both the machine to which it makes the SOAP calls and the MS-SQL box show no indications of load. When tomcat is freshly restarted, I have 44 tomcat processes (ps ax | grep jrockit | wc -l). Over time (a number of days) this increases, until it hits around 245 processes, and it goes no higher than this. What I'm looking for is some sort of solution - either some tomcat setting I'm unfamiliar with that might be causing this, or some way outside of Tomcat I can put a band-aid style fix in place - restarting tomcat every X days, but that's uglier than I'd like - I'd far rather identify and fix the problem, than do scheduled restarts. Any assistance or suggestions that any kind soul can offer would be greatly appreciated. Thanks. Andrew -- They sicken of the calm; http://scroll.redemption.co.nz/ That know the storm. http://www.gadgets-weblog.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Hanging tomcat processes on heavy access
Hello, Chris: I have a couple of suggestions (but no answers). 1) you can attach to a process with the 'truss' command and monitor the read/write activity of the process. Syntax, options, and examples of truss can be had via man truss or Google Unix truss command. This *might* reveal something. 2) you can kill hanging processes and release the port via a Unix command (the name escapes me right now), which may help reduce the number of time you need to reboot 3) try experimenting with the min/max heap size for Java; perhaps you can set both of them to small values in a test environment to quickly reproduce the problem and use #1 Since other people can continue working normally, it does not appear that you've read the maximum number of socket connections (338, if I remember correctly). Did this problem start after having installed new software or changing the environment? Perhaps you can try rolling back to see if the problem disappears Cordially, Oswald Christoph Fischer [EMAIL PROTECTED] wrote: Hello everyone, here is my configuration: linux server with tomcat 4.1.29 connected to apache 1.3.29 via nod_jk java version 1.4.2_03 from tomcat server.xml port=8009 minProcessors=5 maxProcessors=500 acceptCount=10 debug=0/ At heavy access times the user gets a blank screen on the browser and on the server a java process is hanging. Tomcat is still working and responding to further tasks, but the 'hanging' processes will stay around until reboot. Unfortunately the hanging processes will also keep a socket connection on port 8009 to apache, so after some time the system hangs due to too much connections. I could rebuild this situation also with jmeter and a simple servlet which only responds a simple html site, so the problem couldn't come from my coding. How can I solve this problem ? Is it coming from tomcat, apache or mod_jk??? Thanks very much for any hints Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Do you Yahoo!? Get better spam protection with Yahoo! Mail
Re: Hanging tomcat processes on heavy access
Oswald Campesato wrote: Hello, Chris: I have a couple of suggestions (but no answers). 1) you can attach to a process with the 'truss' command and monitor the read/write activity of the process. Syntax, options, and examples of truss can be had via man truss or Google Unix truss command. This *might* reveal something. 2) you can kill hanging processes and release the port via a Unix command (the name escapes me right now), which may help reduce the number of time you need to reboot 3) try experimenting with the min/max heap size for Java; perhaps you can set both of them to small values in a test environment to quickly reproduce the problem and use #1 Since other people can continue working normally, it does not appear that you've read the maximum number of socket connections (338, if I remember correctly). Did this problem start after having installed new software or changing the environment? Perhaps you can try rolling back to see if the problem disappears Cordially, Oswald Christoph Fischer [EMAIL PROTECTED] wrote: Hello everyone, here is my configuration: linux server with tomcat 4.1.29 connected to apache 1.3.29 via nod_jk java version 1.4.2_03 from tomcat server.xml port=8009 minProcessors=5 maxProcessors=500 acceptCount=10 debug=0/ At heavy access times the user gets a blank screen on the browser and on the server a java process is hanging. Tomcat is still working and responding to further tasks, but the 'hanging' processes will stay around until reboot. Unfortunately the hanging processes will also keep a socket connection on port 8009 to apache, so after some time the system hangs due to too much connections. I could rebuild this situation also with jmeter and a simple servlet which only responds a simple html site, so the problem couldn't come from my coding. How can I solve this problem ? Is it coming from tomcat, apache or mod_jk??? Hi christopher, I'd like to add that you may need to improve the mod_jk config using arguments (parameters) like the TIME_WAIT ? could be helpful to release more quickly connections have you setted the KEEP-ALIVE parameter ? I guess that a deep look to you mod_jk configuration may solve much troubles... HTH Jerome -- Auteur cahier du programmeur Java tome 2 - Eyrolles 10/2003 http://www.eyrolles.com/php.informatique/Ouvrages/ouvrage.php3?ouv_ean13=9782212111941 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Hanging tomcat processes on heavy access
Hello and thank you for your response, until now it workes as I've set up the min.-processes up to 100 and changed the min and max heap to 256/512MB Chris jerome moliere wrote: Oswald Campesato wrote: Hello, Chris: I have a couple of suggestions (but no answers). 1) you can attach to a process with the 'truss' command and monitor the read/write activity of the process. Syntax, options, and examples of truss can be had via man truss or Google Unix truss command. This *might* reveal something. 2) you can kill hanging processes and release the port via a Unix command (the name escapes me right now), which may help reduce the number of time you need to reboot 3) try experimenting with the min/max heap size for Java; perhaps you can set both of them to small values in a test environment to quickly reproduce the problem and use #1 Since other people can continue working normally, it does not appear that you've read the maximum number of socket connections (338, if I remember correctly). Did this problem start after having installed new software or changing the environment? Perhaps you can try rolling back to see if the problem disappears Cordially, Oswald Christoph Fischer [EMAIL PROTECTED] wrote: Hello everyone, here is my configuration: linux server with tomcat 4.1.29 connected to apache 1.3.29 via nod_jk java version 1.4.2_03 from tomcat server.xml port=8009 minProcessors=5 maxProcessors=500 acceptCount=10 debug=0/ At heavy access times the user gets a blank screen on the browser and on the server a java process is hanging. Tomcat is still working and responding to further tasks, but the 'hanging' processes will stay around until reboot. Unfortunately the hanging processes will also keep a socket connection on port 8009 to apache, so after some time the system hangs due to too much connections. I could rebuild this situation also with jmeter and a simple servlet which only responds a simple html site, so the problem couldn't come from my coding. How can I solve this problem ? Is it coming from tomcat, apache or mod_jk??? Hi christopher, I'd like to add that you may need to improve the mod_jk config using arguments (parameters) like the TIME_WAIT ? could be helpful to release more quickly connections have you setted the KEEP-ALIVE parameter ? I guess that a deep look to you mod_jk configuration may solve much troubles... HTH Jerome - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Hanging tomcat processes on heavy access
Hello everyone, here is my configuration: linux server with tomcat 4.1.29 connected to apache 1.3.29 via nod_jk java version 1.4.2_03 from tomcat server.xml !-- Define an AJP 1.3 Connector on port 8009 -- Connector className=org.apache.ajp.tomcat4.Ajp13Connector port=8009 minProcessors=5 maxProcessors=500 acceptCount=10 debug=0/ At heavy access times the user gets a blank screen on the browser and on the server a java process is hanging. Tomcat is still working and responding to further tasks, but the 'hanging' processes will stay around until reboot. Unfortunately the hanging processes will also keep a socket connection on port 8009 to apache, so after some time the system hangs due to too much connections. I could rebuild this situation also with jmeter and a simple servlet which only responds a simple html site, so the problem couldn't come from my coding. How can I solve this problem ? Is it coming from tomcat, apache or mod_jk??? Thanks very much for any hints Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Rouge tomcat processes
Hi, We have a problem in that tomcat processes are taking up 100% CPU. We're just upgraded the JVM to jdk1.4.2_02 to try and fix this, as per the FAQ at apache.org and this hasn't changed anything. We don't know what is causing this and wondered if there is any way to match the pid's with Tomcat session id's so we can look through the logs to investigate what might have caused this? Thanks Chris ** The information contained in this message or any of its attachments may be privileged and confidential and intended for the exclusive use of the addressee. The views expressed may not be APAK policy but the personal views of the originator. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message and any attachments without retaining a copy. This footnote also confirms that this email message has been swept for the presence of known computer viruses before being sent. **
Re: Rouge tomcat processes
Nope. Your best chance is to perform some thread dumps. (Google on how to do a thread dump) From the thread dumps get some when things are good, and multiple ones when things are bad. With luck your see a pattern in the dumps. You'll notice a lot of stuff waiting and sleeping that have similar traces, you can ignore those since those are probably workers waiting for work. -Tim Chris Haskins wrote: Hi, We have a problem in that tomcat processes are taking up 100% CPU. We're just upgraded the JVM to jdk1.4.2_02 to try and fix this, as per the FAQ at apache.org and this hasn't changed anything. We don't know what is causing this and wondered if there is any way to match the pid's with Tomcat session id's so we can look through the logs to investigate what might have caused this? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
tomcat shutdown.sh doesn't kill tomcat processes
So the symptom is /usr/local/tomcat/bin/shutdown.sh does not stop tomcat. By the way tomcat is running jk2 connector on port 8080 to apache on port 80 Even after i stop tomcat, I will see in netstat -nap | grep 8080 that the socket is still open, and ps -elf | grep tomcat that the process for tomcat are still running. Any ideas or seen this? When I try to stop it again of course it complains, because it thinks its stopped; # service tomcat stop Stopping Tomcat Using CATALINA_BASE: /usr/local/tomcat Using CATALINA_HOME: /usr/local/tomcat Using CATALINA_TMPDIR: /usr/local/tomcat/temp Using JAVA_HOME: /usr/local/java Catalina.stop: java.net.ConnectException: Connection refused java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158) at java.net.Socket.connect(Socket.java:426) at java.net.Socket.connect(Socket.java:376) at java.net.Socket.init(Socket.java:291) at java.net.Socket.init(Socket.java:119) at org.apache.catalina.startup.Catalina.stop(Catalina.java:581) at org.apache.catalina.startup.Catalina.execute(Catalina.java:402) at org.apache.catalina.startup.Catalina.process(Catalina.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203) the corresponding out in catalina.out is: Catalina.start: LifecycleException: Protocol handler initialization failed: java.net.BindException: Address already in use:8080 LifecycleException: Protocol handler initialization failed: java.net.BindException: Address already in use:8080 at org.apache.coyote.tomcat4.CoyoteConnector.initialize(CoyoteConnector.jav a:11 19) at org.apache.catalina.core.StandardService.initialize(StandardService.java :579 ) at org.apache.catalina.core.StandardServer.initialize(StandardServer.java:2 246) at org.apache.catalina.startup.Catalina.start(Catalina.java:511) at org.apache.catalina.startup.Catalina.execute(Catalina.java:400) at org.apache.catalina.startup.Catalina.process(Catalina.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203) Catalina.stop: LifecycleException: This server has not yet been started Regards, Patrice Seyed, System Administrator RHCE, SCSA Genetics Program, BU School of Medicine
RE: tomcat shutdown.sh doesn't kill tomcat processes
Howdy, Hey, you're virtually next door to me ;) Anyways, you most likely have non-daemon threads in your app. Tomcat can't shut those down for you (see javadoc in java.lang.Thread as well as many discussions on this list in the past). That's why the process is still alive, shutdown isn't properly completed, and you can't start the server again because the socket is still bound. Yoav Shapira Millennium ChemInformatics -Original Message- From: Patrice Seyed [mailto:[EMAIL PROTECTED] Sent: Thursday, September 25, 2003 1:43 PM To: [EMAIL PROTECTED] Subject: tomcat shutdown.sh doesn't kill tomcat processes So the symptom is /usr/local/tomcat/bin/shutdown.sh does not stop tomcat. By the way tomcat is running jk2 connector on port 8080 to apache on port 80 Even after i stop tomcat, I will see in netstat -nap | grep 8080 that the socket is still open, and ps -elf | grep tomcat that the process for tomcat are still running. Any ideas or seen this? When I try to stop it again of course it complains, because it thinks its stopped; # service tomcat stop Stopping Tomcat Using CATALINA_BASE: /usr/local/tomcat Using CATALINA_HOME: /usr/local/tomcat Using CATALINA_TMPDIR: /usr/local/tomcat/temp Using JAVA_HOME: /usr/local/java Catalina.stop: java.net.ConnectException: Connection refused java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158) at java.net.Socket.connect(Socket.java:426) at java.net.Socket.connect(Socket.java:376) at java.net.Socket.init(Socket.java:291) at java.net.Socket.init(Socket.java:119) at org.apache.catalina.startup.Catalina.stop(Catalina.java:581) at org.apache.catalina.startup.Catalina.execute(Catalina.java:402) at org.apache.catalina.startup.Catalina.process(Catalina.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.ja v a:39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso r Impl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203) the corresponding out in catalina.out is: Catalina.start: LifecycleException: Protocol handler initialization failed: java.net.BindException: Address already in use:8080 LifecycleException: Protocol handler initialization failed: java.net.BindException: Address already in use:8080 at org.apache.coyote.tomcat4.CoyoteConnector.initialize(CoyoteConnector.ja v a:11 19) at org.apache.catalina.core.StandardService.initialize(StandardService.jav a :579 ) at org.apache.catalina.core.StandardServer.initialize(StandardServer.java: 2 246) at org.apache.catalina.startup.Catalina.start(Catalina.java:511) at org.apache.catalina.startup.Catalina.execute(Catalina.java:400) at org.apache.catalina.startup.Catalina.process(Catalina.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.ja v a:39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso r Impl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203) Catalina.stop: LifecycleException: This server has not yet been started Regards, Patrice Seyed, System Administrator RHCE, SCSA Genetics Program, BU School of Medicine This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: tomcat shutdown.sh doesn't kill tomcat processes
I've thumbed through the archives, can anyone give me larger hint? -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Thursday, September 25, 2003 1:44 PM To: Tomcat Users List Subject: RE: tomcat shutdown.sh doesn't kill tomcat processes Howdy, Hey, you're virtually next door to me ;) Anyways, you most likely have non-daemon threads in your app. Tomcat can't shut those down for you (see javadoc in java.lang.Thread as well as many discussions on this list in the past). That's why the process is still alive, shutdown isn't properly completed, and you can't start the server again because the socket is still bound. Yoav Shapira Millennium ChemInformatics -Original Message- From: Patrice Seyed [mailto:[EMAIL PROTECTED] Sent: Thursday, September 25, 2003 1:43 PM To: [EMAIL PROTECTED] Subject: tomcat shutdown.sh doesn't kill tomcat processes So the symptom is /usr/local/tomcat/bin/shutdown.sh does not stop tomcat. By the way tomcat is running jk2 connector on port 8080 to apache on port 80 Even after i stop tomcat, I will see in netstat -nap | grep 8080 that the socket is still open, and ps -elf | grep tomcat that the process for tomcat are still running. Any ideas or seen this? When I try to stop it again of course it complains, because it thinks its stopped; # service tomcat stop Stopping Tomcat Using CATALINA_BASE: /usr/local/tomcat Using CATALINA_HOME: /usr/local/tomcat Using CATALINA_TMPDIR: /usr/local/tomcat/temp Using JAVA_HOME: /usr/local/java Catalina.stop: java.net.ConnectException: Connection refused java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158) at java.net.Socket.connect(Socket.java:426) at java.net.Socket.connect(Socket.java:376) at java.net.Socket.init(Socket.java:291) at java.net.Socket.init(Socket.java:119) at org.apache.catalina.startup.Catalina.stop(Catalina.java:581) at org.apache.catalina.startup.Catalina.execute(Catalina.java:402) at org.apache.catalina.startup.Catalina.process(Catalina.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.ja v a:39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso r Impl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203) the corresponding out in catalina.out is: Catalina.start: LifecycleException: Protocol handler initialization failed: java.net.BindException: Address already in use:8080 LifecycleException: Protocol handler initialization failed: java.net.BindException: Address already in use:8080 at org.apache.coyote.tomcat4.CoyoteConnector.initialize(CoyoteConnector.ja v a:11 19) at org.apache.catalina.core.StandardService.initialize(StandardService.jav a :579 ) at org.apache.catalina.core.StandardServer.initialize(StandardServer.java: 2 246) at org.apache.catalina.startup.Catalina.start(Catalina.java:511) at org.apache.catalina.startup.Catalina.execute(Catalina.java:400) at org.apache.catalina.startup.Catalina.process(Catalina.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.ja v a:39 ) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccesso r Impl .java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:203) Catalina.stop: LifecycleException: This server has not yet been started Regards, Patrice Seyed, System Administrator RHCE, SCSA Genetics Program, BU School of Medicine This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. - 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]
Re: tomcat shutdown.sh doesn't kill tomcat processes
kill -3 tomcatprocessid to force a thread dump after you try to shut tomcat down. From the thread dump look for any thread which is NOT a daemon thread. That is the thing keeping the JVM alive. -Tim Patrice Seyed wrote: I've thumbed through the archives, can anyone give me larger hint? -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Thursday, September 25, 2003 1:44 PM To: Tomcat Users List Subject: RE: tomcat shutdown.sh doesn't kill tomcat processes Howdy, Hey, you're virtually next door to me ;) Anyways, you most likely have non-daemon threads in your app. Tomcat can't shut those down for you (see javadoc in java.lang.Thread as well as many discussions on this list in the past). That's why the process is still alive, shutdown isn't properly completed, and you can't start the server again because the socket is still bound. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat processes
Hi is it possible to increases the number of processes tomcat can handle. If yes the How? Thanks Amit Lonkar Want to sell your car? advertise on Yahoo Autos Classifieds. It's Free!! visit http://in.autos.yahoo.com -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
RE: Tomcat processes
Howdy, You will need to be a bit more specific regarding what the definition of number of processes. I assume you mean concurrent user requests. If that's the case, check the documentation for minProcessors, maxProcessors, and acceptCount at: http://jakarta.apache.org/tomcat/tomcat-4.0-doc/config/http11.html You will also want to take a look at the Coyote HTTP connector information in the 4.1.x release notes and docs. 4.1.x is not a production release yet, but it's been in beta for a while and getting pretty close. And needless to say, your hardware and JVM have a lot to do with this. ;) Yoav Shapira Millennium ChemInformatics -Original Message- From: Amit Lonkar [mailto:[EMAIL PROTECTED]] Sent: Wednesday, August 14, 2002 2:27 AM To: [EMAIL PROTECTED] Subject: Tomcat processes Hi is it possible to increases the number of processes tomcat can handle. If yes the How? Thanks Amit Lonkar ___ _ Want to sell your car? advertise on Yahoo Autos Classifieds. It's Free!! visit http://in.autos.yahoo.com -- To unsubscribe, e-mail: mailto:tomcat-user- [EMAIL PROTECTED] For additional commands, e-mail: mailto:tomcat-user- [EMAIL PROTECTED] This e-mail, including any attachments, is a confidential business communication, and may contain information that is confidential, proprietary and/or privileged. This e-mail is intended only for the individual(s) to whom it is addressed, and may not be saved, copied, printed, disclosed or used by anyone else. If you are not the(an) intended recipient, please immediately delete this e-mail from your computer system and notify the sender. Thank you. -- To unsubscribe, e-mail: mailto:[EMAIL PROTECTED] For additional commands, e-mail: mailto:[EMAIL PROTECTED]
Tomcat processes stay alive after shutdown
I've read the FAQ but didn't find an answer to this exact issue. Versions: Solaris 8 SPARC, Tomcat 4.0.2b2, Apache 1.3.23, j2sdk1.3.1_01 . There are 2 Tomcats sharing connections from Apache,both are experiencing the same problem.If I start them by tomcat1/bin/startup.sh and tomcat2/bin/startup.sh, 2 processes are up which look like root 14240 0.0 3.96863238776 pts/6S 10:54:23 0:20 /usr/j2sdk1_3_1_01/bin/../bin/sparc/native_threads/java -classpath /usr/local/tomcat1/bin/bootstrap.jar:other jars... -Dcatalina.base=/usr/local/tomcat1 -Dcatalina.home=/usr/local/tomcat1 org.apache.catalina.startup.Bootstrap start and the other one whick looks almost the same (except tomcat1 it's tomcat2). When I try to shutdown both of them by running tomcat1/bin/shutdown.sh and tomcat2/bin/shutdown.sh, both commands successfully complete, but the processes are still in the air. The next try of shutdown's results in Catalina.stop: java.net.ConnectException: Connection refused complaints, which tells me that probably the first shutdown did its job. How can I be sure? If it kills at the first time the Tomcat, then why are those processes still hanging around? If this is an expected behavior, can somebody explain this, please? And, of course I can kill -9 it, but I don't feel it's the right solution. After all this is not two services trying to bind to the same port situation. Thanks, Edward -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Re: Tomcat processes stay alive after shutdown
Does your program use threads? Does it have connections to other machines via jdbc/etc? These can keep the process alive until they are closed properly. - Toni -- To unsubscribe: mailto:[EMAIL PROTECTED] For additional commands: mailto:[EMAIL PROTECTED] Troubles with the list: mailto:[EMAIL PROTECTED]
Everlasting tomcat processes
Dear all, in my production system I have some processes which last very long. They seem to never die. I can have many processes like that are lasting 10/20 mn and using my CPU and memory in an useless manner. What I can see making a top command : 1216 root 10 0 14604 12M 1984 S 0.5 10.4 10:28 java I there a parameter to set to prevent from these everlasting tomcat process ? Can i say somewhere kill these process if they last more than 4mn for example ? Best regards, Eric
RE: Everlasting tomcat processes
It's probable these 'ever-lasting' process are tomcat running normally. Do you know these threads to started by a JSP or Servlet in reponse to a connection? Does the number and PIDs remain stable? - Original Message - From: Chaber, Eric [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Mon, 24 Sep 2001 08:09:53 -0700 Subject: Everlasting tomcat processes Dear all, in my production system I have some processes which last very long. They seem to never die. I can have many processes like that are lasting 10/20 mn and using my CPU and memory in an useless manner. What I can see making a top command : 1216 root 10 0 14604 12M 1984 S 0.5 10.4 10:28 java I there a parameter to set to prevent from these everlasting tomcat process ? Can i say somewhere kill these process if they last more than 4mn for example ? Best regards, Eric - This email has been sent using TurtleMail - Get your free email address from www.purpleturtle.com now!
RE: Everlasting tomcat processes
These threads are made by calls to servlets PIDs remain stable But there are CPU and RAM consuming so i'd like to stop them if they last too long. -Original Message- From: Janek Bogucki [mailto:[EMAIL PROTECTED]] Sent: September 24 2001 17:30 To: [EMAIL PROTECTED] Subject: RE: Everlasting tomcat processes It's probable these 'ever-lasting' process are tomcat running normally. Do you know these threads to started by a JSP or Servlet in reponse to a connection? Does the number and PIDs remain stable? - Original Message - From: Chaber, Eric [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Mon, 24 Sep 2001 08:09:53 -0700 Subject: Everlasting tomcat processes Dear all, in my production system I have some processes which last very long. They seem to never die. I can have many processes like that are lasting 10/20 mn and using my CPU and memory in an useless manner. What I can see making a top command : 1216 root 10 0 14604 12M 1984 S 0.5 10.4 10:28 java I there a parameter to set to prevent from these everlasting tomcat process ? Can i say somewhere kill these process if they last more than 4mn for example ? Best regards, Eric - This email has been sent using TurtleMail - Get your free email address from www.purpleturtle.com now!
RE: to many tomcat processes!! AAH!!
which JDK are you using ? Shuklix -Original Message- From: Georges Boutros [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 18, 2001 1:34 AM To: '[EMAIL PROTECTED]' Subject: RE: to many tomcat processes!! AAH!! does anyone know how can i force java to use green threads? thanks -Original Message- From: Ansgar W. Konermann [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 12, 2001 8:31 PM To: [EMAIL PROTECTED] Subject: Re: to many tomcat processes!! AAH!! Hi, maybe the many processes are because jdk1.2 and up use native threads (AFAIK, 1.1 used green threads, i. e. a threading package implemented in java itself). With 1.2+, every java thread is a native OS thread and therefor gets listed by ps. Have you tried forcing java to use green threads? I'm quite sure that it is possible (RTFM). -- Best regards, Ansgar W. Konermann eMail: [EMAIL PROTECTED] --- Hello, I am a message footer. -
Re: to many tomcat processes!! AAH!!
Hei, i use JDK 1.3 Saurabh Shukla wrote: which JDK are you using ? Shuklix -Original Message- From: Georges Boutros [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 18, 2001 1:34 AM To: '[EMAIL PROTECTED]' Subject: RE: to many tomcat processes!! AAH!! does anyone know how can i force java to use green threads? thanks -Original Message- From: Ansgar W. Konermann [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 12, 2001 8:31 PM To: [EMAIL PROTECTED] Subject: Re: to many tomcat processes!! AAH!! Hi, maybe the many processes are because jdk1.2 and up use native threads (AFAIK, 1.1 used green threads, i. e. a threading package implemented in java itself). With 1.2+, every java thread is a native OS thread and therefor gets listed by ps. Have you tried forcing java to use green threads? I'm quite sure that it is possible (RTFM). -- Best regards, Ansgar W. Konermann eMail: [EMAIL PROTECTED] --- Hello, I am a message footer. - -- __ Gruss, Wolle --- [EMAIL PROTECTED]
RE: to many tomcat processes!! AAH!!
ok, open your java file, it is a shell script. (it should be in your JAVA_HOME/bin/ ) look for this line DEFAULT_THREADS_FLAG=native change native to green . ie now the DEFAULT_THREADS_FLAG=green this should do the job. let me know if it does't/does works. Regards, Shuklix -Original Message- From: Wolle [mailto:[EMAIL PROTECTED]] Sent: Monday, April 23, 2001 5:00 PM To: [EMAIL PROTECTED] Subject: Re: to many tomcat processes!! AAH!! Hei, i use JDK 1.3 Saurabh Shukla wrote: which JDK are you using ? Shuklix -Original Message- From: Georges Boutros [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 18, 2001 1:34 AM To: '[EMAIL PROTECTED]' Subject: RE: to many tomcat processes!! AAH!! does anyone know how can i force java to use green threads? thanks -Original Message- From: Ansgar W. Konermann [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 12, 2001 8:31 PM To: [EMAIL PROTECTED] Subject: Re: to many tomcat processes!! AAH!! Hi, maybe the many processes are because jdk1.2 and up use native threads (AFAIK, 1.1 used green threads, i. e. a threading package implemented in java itself). With 1.2+, every java thread is a native OS thread and therefor gets listed by ps. Have you tried forcing java to use green threads? I'm quite sure that it is possible (RTFM). -- Best regards, Ansgar W. Konermann eMail: [EMAIL PROTECTED] --- Hello, I am a message footer. - -- __ Gruss, Wolle --- [EMAIL PROTECTED]
RE: to many tomcat processes!! AAH!!
I do not know why you would want to do this other then for testing but -- change your startup script for tomcat to include the option java -classic and you will be using green threads. Be aware that it is now easier to create a deadlock situation. I believe that it would be a big mistake to deploy a system with green threads. My system incorrectly reports that I am using 217 meg of ram but that is incorrect, It is actually using 74 meg of ram.(with tomcat running) Use gps for a more accurate reading. Pushing the server hard during testing does not increase the ram used significantly. (cpu usage reflects as you would expect) All those processes that you are seeing are simply sleeping threads. They are NOT using any resources and are being incorrectly reported as consuming processes. This is the very compelling reason that you would want to use java in the first place. Native multi-threading. You have a thread pool ready to respond without the overhead of creating new processes on demand. Good luck, Craig Let us know what you find out. -Original Message- From: Wolle [mailto:[EMAIL PROTECTED]] Sent: Monday, April 23, 2001 4:30 AM To: [EMAIL PROTECTED] Subject: Re: to many tomcat processes!! AAH!! Hei, i use JDK 1.3 Saurabh Shukla wrote: which JDK are you using ? Shuklix -Original Message- From: Georges Boutros [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 18, 2001 1:34 AM To: '[EMAIL PROTECTED]' Subject: RE: to many tomcat processes!! AAH!! does anyone know how can i force java to use green threads? thanks -Original Message- From: Ansgar W. Konermann [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 12, 2001 8:31 PM To: [EMAIL PROTECTED] Subject: Re: to many tomcat processes!! AAH!! Hi, maybe the many processes are because jdk1.2 and up use native threads (AFAIK, 1.1 used green threads, i. e. a threading package implemented in java itself). With 1.2+, every java thread is a native OS thread and therefor gets listed by ps. Have you tried forcing java to use green threads? I'm quite sure that it is possible (RTFM). -- Best regards, Ansgar W. Konermann eMail: [EMAIL PROTECTED] --- Hello, I am a message footer. - -- __ Gruss, Wolle --- [EMAIL PROTECTED]
RE: to many tomcat processes!! AAH!!
Or you can do try thing also.
open the file $Tomcat_home/bin/tomcat.sh
in there look for the word native , if there is any such thing change it to
green.(this is assuming that your tomcat start script specifies that it is
using native threads)
in the tomcat.sh file, the command line which runs tomcat looks something
like this.
$JAVACMD -native -Xms64M -Xmx128M $TOMCAT_OPTS -Dtomcat.home=${TOMCAT_HOME}
org.apache.tomcat.startup.Tomcat $@
or
make it $JAVACMD -green -Xms64M -Xmx128M
$TOMCAT_OPTS -Dtomcat.home=${TOMCAT_HOME} org.apache.tomcat.startup.Tomcat
$@
to use the green threads.
However too many java process should not be an issue to worry about, coz' in
green threads
all those processes are shown as a part of one process. Infact your
performance might deteriorate because of use of green threads. You can check
out the performance using
green threads and native threads and then decide if to use green or native
threads.
Shuklix
-Original Message-
From: Wolle [mailto:[EMAIL PROTECTED]]
Sent: Monday, April 23, 2001 5:00 PM
To: [EMAIL PROTECTED]
Subject: Re: to many tomcat processes!! AAH!!
Hei,
i use JDK 1.3
Saurabh Shukla wrote:
which JDK are you using ?
Shuklix
-Original Message-
From: Georges Boutros [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 18, 2001 1:34 AM
To: '[EMAIL PROTECTED]'
Subject: RE: to many tomcat processes!! AAH!!
does anyone know how can i force java to use green threads?
thanks
-Original Message-
From: Ansgar W. Konermann [mailto:[EMAIL PROTECTED]]
Sent: Thursday, April 12, 2001 8:31 PM
To: [EMAIL PROTECTED]
Subject: Re: to many tomcat processes!! AAH!!
Hi,
maybe the many processes are because jdk1.2 and up use native threads
(AFAIK, 1.1 used green threads, i. e. a threading package implemented
in java itself).
With 1.2+, every java thread is a native OS thread and therefor gets
listed by ps. Have you tried forcing java to use green threads? I'm
quite sure that it is possible (RTFM).
--
Best regards,
Ansgar W. Konermann
eMail: [EMAIL PROTECTED]
--- Hello, I am a message footer. -
--
__
Gruss,
Wolle
---
[EMAIL PROTECTED]
Re: to many tomcat processes!! AAH!!
Thanks for all the Information, i don't want to change it in green Threads, I would only knew what's goining on with these Threads , and know I have these Information, thanks a lot ! Greetings, Wolle Craig O'Brien wrote: I do not know why you would want to do this other then for testing but -- change your startup script for tomcat to include the option java -classic and you will be using green threads. Be aware that it is now easier to create a deadlock situation. I believe that it would be a big mistake to deploy a system with green threads. My system incorrectly reports that I am using 217 meg of ram but that is incorrect, It is actually using 74 meg of ram.(with tomcat running) Use gps for a more accurate reading. Pushing the server hard during testing does not increase the ram used significantly. (cpu usage reflects as you would expect) All those processes that you are seeing are simply sleeping threads. They are NOT using any resources and are being incorrectly reported as consuming processes. This is the very compelling reason that you would want to use java in the first place. Native multi-threading. You have a thread pool ready to respond without the overhead of creating new processes on demand. Good luck, Craig Let us know what you find out. -Original Message- From: Wolle [mailto:[EMAIL PROTECTED]] Sent: Monday, April 23, 2001 4:30 AM To: [EMAIL PROTECTED] Subject: Re: to many tomcat processes!! AAH!! Hei, i use JDK 1.3 Saurabh Shukla wrote: which JDK are you using ? Shuklix -Original Message- From: Georges Boutros [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 18, 2001 1:34 AM To: '[EMAIL PROTECTED]' Subject: RE: to many tomcat processes!! AAH!! does anyone know how can i force java to use green threads? thanks -Original Message- From: Ansgar W. Konermann [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 12, 2001 8:31 PM To: [EMAIL PROTECTED] Subject: Re: to many tomcat processes!! AAH!! Hi, maybe the many processes are because jdk1.2 and up use native threads (AFAIK, 1.1 used green threads, i. e. a threading package implemented in java itself). With 1.2+, every java thread is a native OS thread and therefor gets listed by ps. Have you tried forcing java to use green threads? I'm quite sure that it is possible (RTFM). -- Best regards, Ansgar W. Konermann eMail: [EMAIL PROTECTED] --- Hello, I am a message footer. -
RE: to many tomcat processes!! AAH!!
Please get me off this list --- Saurabh Shukla [EMAIL PROTECTED] wrote: ok, open your java file, it is a shell script. (it should be in your JAVA_HOME/bin/ ) look for this line DEFAULT_THREADS_FLAG=native change native to green . ie now the DEFAULT_THREADS_FLAG=green this should do the job. let me know if it does't/does works. Regards, Shuklix -Original Message- From: Wolle [mailto:[EMAIL PROTECTED]] Sent: Monday, April 23, 2001 5:00 PM To: [EMAIL PROTECTED] Subject: Re: to many tomcat processes!! AAH!! Hei, i use JDK 1.3 Saurabh Shukla wrote: which JDK are you using ? Shuklix -Original Message- From: Georges Boutros [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 18, 2001 1:34 AM To: '[EMAIL PROTECTED]' Subject: RE: to many tomcat processes!! AAH!! does anyone know how can i force java to use green threads? thanks -Original Message- From: Ansgar W. Konermann [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 12, 2001 8:31 PM To: [EMAIL PROTECTED] Subject: Re: to many tomcat processes!! AAH!! Hi, maybe the many processes are because jdk1.2 and up use native threads (AFAIK, 1.1 used green threads, i. e. a threading package implemented in java itself). With 1.2+, every java thread is a native OS thread and therefor gets listed by ps. Have you tried forcing java to use green threads? I'm quite sure that it is possible (RTFM). -- Best regards, Ansgar W. Konermann eMail: [EMAIL PROTECTED] --- Hello, I am a message footer. - -- __ Gruss, Wolle --- [EMAIL PROTECTED] = If your into Body For Life, check out http://clubs.yahoo.com/clubs/bodyforlifestatenislandny __ Do You Yahoo!? Yahoo! Auctions - buy the things you want at great prices http://auctions.yahoo.com/
RE: to many tomcat processes!! AAH!!
does anyone know how can i force java to use green threads? thanks -Original Message- From: Ansgar W. Konermann [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 12, 2001 8:31 PM To: [EMAIL PROTECTED] Subject: Re: to many tomcat processes!! AAH!! Hi, maybe the many processes are because jdk1.2 and up use native threads (AFAIK, 1.1 used "green" threads, i. e. a threading package implemented in java itself). With 1.2+, every java thread is a native OS thread and therefor gets listed by ps. Have you tried forcing java to use green threads? I'm quite sure that it is possible (RTFM). -- Best regards, Ansgar W. Konermann eMail: [EMAIL PROTECTED] --- Hello, I am a message footer. -
RE: to many tomcat processes!! AAH!!
At 04:03 PM 4/17/01 -0400, you wrote: does anyone know how can i force java to use green threads? thanks I don't know how, but why would you want to do it? The native thread use should be more efficient. The only drawback is the the way that the ps command displays the threads, but it is only a display issue. The threads aren't actually using up all the memory that the ps command output suggests.. Ed -Original Message- From: Ansgar W. Konermann [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 12, 2001 8:31 PM To: [EMAIL PROTECTED] Subject: Re: to many tomcat processes!! AAH!! Hi, maybe the many processes are because jdk1.2 and up use native threads (AFAIK, 1.1 used "green" threads, i. e. a threading package implemented in java itself). With 1.2+, every java thread is a native OS thread and therefor gets listed by ps. Have you tried forcing java to use green threads? I'm quite sure that it is possible (RTFM). -- Best regards, Ansgar W. Konermann eMail: [EMAIL PROTECTED] --- Hello, I am a message footer. -
RE: to many tomcat processes!! AAH!!
Try something like -green (as opposed to -native) as the first command line argument. This is how it works on the bd jdk 1.17 at least. If not, have a look at the $JAVA_HOME/bin/java wrapper, it should have details in there, and probably a way to change the default threading model. Like you, the process lists used to annoy me, but after getting over the initial emotional trauma (!), they became easy to live with. The process lists on some of my boxes are so large anyway that I use 'ps ax|grep whatever' to find processes regardless. Kevin On Tue, 17 Apr 2001, Georges Boutros wrote: does anyone know how can i force java to use green threads? thanks -Original Message- From: Ansgar W. Konermann [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 12, 2001 8:31 PM To: [EMAIL PROTECTED] Subject: Re: to many tomcat processes!! AAH!! Hi, maybe the many processes are because jdk1.2 and up use native threads (AFAIK, 1.1 used "green" threads, i. e. a threading package implemented in java itself). With 1.2+, every java thread is a native OS thread and therefor gets listed by ps. Have you tried forcing java to use green threads? I'm quite sure that it is possible (RTFM). -- Best regards, Ansgar W. Konermann eMail: [EMAIL PROTECTED] --- Hello, I am a message footer. -
RE: to many tomcat processes!! AAH!!
You can use green threads instead of native threads and thou shall see just one process. :-) Shuklix -Original Message-From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of David CrookeSent: Friday, April 13, 2001 9:45 AMTo: [EMAIL PROTECTED]Subject: Re: to many tomcat processes!! AAH!!This is how Linux shows kernel threads; nothing to be alarmed about. There is only one process. "Brendon M. Maragia" wrote: Dear Readers, I finally!!! Got Jakarta Tomcatvhosting with Cocoon and it was soso beautiful andsweet, I jumped around the room screaming in joy.Don't tryan tell me you've never done that.Anyways, I was usingjdk1.1.3 ;]ewww, I know.So I upgraded to j2sdk1.3 and fired everything back up.Low and behold when runningps -aux, I was confronted with this root2806 44.54.1 76632 10580 pts/1S20:010:01 /usr/local/jdk1.2.2/bin/i386/native_threads/java -Dtomcat.home=/usr/l root28440.04.1 76632 10580 pts/1S20:010:00 /usr/local/jdk1.2.2/bin/i386/native_threads/java -Dtomcat.home=/usr/l root28450.04.1 76632 10580 pts/1S20:010:00 /usr/local/jdk1.2.2/bin/i386/native_threads/java -Dtomcat.home=/usr/l root28460.04.1 76632 10580 pts/1S20:010:00 /usr/local/jdk1.2.2/bin/i386/native_threads/java -Dtomcat.home=/usr/l Not just that about 50 more.In total about 54 Jakarta Tomcat processes, all this right after I upgraded to j2sdk1.3.I tried downgrading again to jdk1.2.2, no dice same error.I searched through the mail archives and noticed a guy buy the name of Pete Wright had posted a similar error.I emailed him and he told me the list hadn't been much help.So in posting the same error again I hope to raise usersympathy ;]please help! Sincerely, Brendon Maragia
Re: to many tomcat processes!! AAH!!
Read my last post. It tells you where to find the configuration examples. --jeff - Original Message - From: Georges Boutros To: '[EMAIL PROTECTED]' Sent: Friday, April 13, 2001 6:54 AM Subject: RE: to many tomcat processes!! AAH!! hi, how can you configure server.xml ?? Do you have an example about the configuration of PoolTCPConnectors for ajp12 and ajp13 thanks, Georges -Original Message-From: Jeff Kilbride [mailto:[EMAIL PROTECTED]]Sent: Thursday, April 12, 2001 10:10 PMTo: [EMAIL PROTECTED]Subject: Re: to many tomcat processes!! AAH!! Go to the Tomcat User's Guide: http://jakarta.apache.org/tomcat/jakarta-tomcat/src/doc/index.html and do a search for "max_threads". You can configure your PoolTCPConnectors for ajp12 and ajp13 via the server.xml file. BE CAREFUL. If you set these values too low, you will undoubtedly hamper performance. However, you shouldn't leave these at the default values once you understand what they do. In my case, I am using ajp13 in all of my code. ajp12, as far as I know, is only being used for startup/shutdown of Tomcat itself. So, I cut the values way back for ajp12 and increased the defaults for ajp13. Thanks, --jeff - Original Message - From: Brendon M. Maragia To: [EMAIL PROTECTED] Sent: Thursday, April 12, 2001 5:14 PM Subject: to many tomcat processes!! AAH!! Dear Readers, I finally!!! Got Jakarta Tomcat vhosting with Cocoon and it was so so beautiful and sweet, I jumped around the room screaming in joy. Dont try an tell me youve never done that. Anyways, I was using jdk1.1.3 ;] ewww, I know. So I upgraded to j2sdk1.3 and fired everything back up. Low and behold when running ps aux, I was confronted with this. root 2806 44.5 4.1 76632 10580 pts/1 S 20:01 0:01 /usr/local/jdk1.2.2/bin/i386/native_threads/java -Dtomcat.home=/usr/l root 2844 0.0 4.1 76632 10580 pts/1 S 20:01 0:00 /usr/local/jdk1.2.2/bin/i386/native_threads/java -Dtomcat.home=/usr/l root 2845 0.0 4.1 76632 10580 pts/1 S 20:01 0:00 /usr/local/jdk1.2.2/bin/i386/native_threads/java -Dtomcat.home=/usr/l root 2846 0.0 4.1 76632 10580 pts/1 S 20:01 0:00 /usr/local/jdk1.2.2/bin/i386/native_threads/java -Dtomcat.home=/usr/l Not just that about 50 more. In total about 54 Jakarta Tomcat processes, all this right after I upgraded to j2sdk1.3. I tried downgrading again to jdk1.2.2, no dice same error. I searched through the mail archives and noticed a guy buy the name of Pete Wright had posted a similar error. I emailed him and he told me the list hadnt been much help. So in posting the same error again I hope to raise user sympathy ;] please help! Sincerely, Brendon Maragia
to many tomcat processes!! AAH!!
Dear Readers, I finally!!! Got Jakarta Tomcat vhosting with Cocoon and it was so so beautiful and sweet, I jumped around the room screaming in joy. Dont try an tell me youve never done that. Anyways, I was using jdk1.1.3 ;] ewww, I know. So I upgraded to j2sdk1.3 and fired everything back up. Low and behold when running ps aux, I was confronted with this. root 2806 44.5 4.1 76632 10580 pts/1 S 20:01 0:01 /usr/local/jdk1.2.2/bin/i386/native_threads/java -Dtomcat.home=/usr/l root 2844 0.0 4.1 76632 10580 pts/1 S 20:01 0:00 /usr/local/jdk1.2.2/bin/i386/native_threads/java -Dtomcat.home=/usr/l root 2845 0.0 4.1 76632 10580 pts/1 S 20:01 0:00 /usr/local/jdk1.2.2/bin/i386/native_threads/java -Dtomcat.home=/usr/l root 2846 0.0 4.1 76632 10580 pts/1 S 20:01 0:00 /usr/local/jdk1.2.2/bin/i386/native_threads/java -Dtomcat.home=/usr/l Not just that about 50 more. In total about 54 Jakarta Tomcat processes, all this right after I upgraded to j2sdk1.3. I tried downgrading again to jdk1.2.2, no dice same error. I searched through the mail archives and noticed a guy buy the name of Pete Wright had posted a similar error. I emailed him and he told me the list hadnt been much help. So in posting the same error again I hope to raise user sympathy ;] please help! Sincerely, Brendon Maragia
Re: to many tomcat processes!! AAH!!
Hi, maybe the many processes are because jdk1.2 and up use native threads (AFAIK, 1.1 used "green" threads, i. e. a threading package implemented in java itself). With 1.2+, every java thread is a native OS thread and therefor gets listed by ps. Have you tried forcing java to use green threads? I'm quite sure that it is possible (RTFM). -- Best regards, Ansgar W. Konermann eMail: [EMAIL PROTECTED] --- Hello, I am a message footer. -
Re: to many tomcat processes!! AAH!!
Go to the Tomcat User's Guide: http://jakarta.apache.org/tomcat/jakarta-tomcat/src/doc/index.html and do a search for "max_threads". You can configure your PoolTCPConnectors for ajp12 and ajp13 via the server.xml file. BE CAREFUL. If you set these values too low, you will undoubtedly hamper performance. However, you shouldn't leave these at the default values once you understand what they do. In my case, I am using ajp13 in all of my code. ajp12, as far as I know, is only being used for startup/shutdown of Tomcat itself. So, I cut the values way back for ajp12 and increased the defaults for ajp13. Thanks, --jeff - Original Message - From: Brendon M. Maragia To: [EMAIL PROTECTED] Sent: Thursday, April 12, 2001 5:14 PM Subject: to many tomcat processes!! AAH!! Dear Readers, I finally!!! Got Jakarta Tomcat vhosting with Cocoon and it was so so beautiful and sweet, I jumped around the room screaming in joy. Dont try an tell me youve never done that. Anyways, I was using jdk1.1.3 ;] ewww, I know. So I upgraded to j2sdk1.3 and fired everything back up. Low and behold when running ps aux, I was confronted with this. root 2806 44.5 4.1 76632 10580 pts/1 S 20:01 0:01 /usr/local/jdk1.2.2/bin/i386/native_threads/java -Dtomcat.home=/usr/l root 2844 0.0 4.1 76632 10580 pts/1 S 20:01 0:00 /usr/local/jdk1.2.2/bin/i386/native_threads/java -Dtomcat.home=/usr/l root 2845 0.0 4.1 76632 10580 pts/1 S 20:01 0:00 /usr/local/jdk1.2.2/bin/i386/native_threads/java -Dtomcat.home=/usr/l root 2846 0.0 4.1 76632 10580 pts/1 S 20:01 0:00 /usr/local/jdk1.2.2/bin/i386/native_threads/java -Dtomcat.home=/usr/l Not just that about 50 more. In total about 54 Jakarta Tomcat processes, all this right after I upgraded to j2sdk1.3. I tried downgrading again to jdk1.2.2, no dice same error. I searched through the mail archives and noticed a guy buy the name of Pete Wright had posted a similar error. I emailed him and he told me the list hadnt been much help. So in posting the same error again I hope to raise user sympathy ;] please help! Sincerely, Brendon Maragia
Re: to many tomcat processes!! AAH!!
This is how Linux shows kernel threads; nothing to be alarmed about. There is only one process. "Brendon M. Maragia" wrote: Dear Readers, I finally!!! Got Jakarta Tomcatvhosting with Cocoon and it was soso beautiful andsweet, I jumped around the room screaming in joy.Don't tryan tell me you've never done that.Anyways, I was usingjdk1.1.3 ;]ewww, I know.So I upgraded to j2sdk1.3 and fired everything back up.Low and behold when runningps -aux, I was confronted with this root2806 44.54.1 76632 10580 pts/1S20:010:01 /usr/local/jdk1.2.2/bin/i386/native_threads/java -Dtomcat.home=/usr/l root28440.04.1 76632 10580 pts/1S20:010:00 /usr/local/jdk1.2.2/bin/i386/native_threads/java -Dtomcat.home=/usr/l root28450.04.1 76632 10580 pts/1S20:010:00 /usr/local/jdk1.2.2/bin/i386/native_threads/java -Dtomcat.home=/usr/l root28460.04.1 76632 10580 pts/1S20:010:00 /usr/local/jdk1.2.2/bin/i386/native_threads/java -Dtomcat.home=/usr/l Not just that about 50 more.In total about 54 Jakarta Tomcat processes, all this right after I upgraded to j2sdk1.3.I tried downgrading again to jdk1.2.2, no dice same error.I searched through the mail archives and noticed a guy buy the name of Pete Wright had posted a similar error.I emailed him and he told me the list hadn't been much help.So in posting the same error again I hope to raise usersympathy ;]please help! Sincerely, Brendon Maragia
Tomcat processes.
When I start Tomcat I see the following- = [vikas@wow bin]$ ps -aefl --cols=300 | grep java 000 S vikas 858 1 4 60 0- 35712 rt_sig 13:47 pts/0 00:00:01 /net/java/jdk1.3/bin/i386/native_threads/java -Dtomcat.home=./.. org.apache.tomcat.startup.Tomcat 040 S vikas 903 858 0 60 0- 35712 do_pol 13:47 pts/0 00:00:00 /net/java/jdk1.3/bin/i386/native_threads/java -Dtomcat.home=./.. org.apache.tomcat.startup.Tomcat 040 S vikas 904 903 0 60 0- 35712 nanosl 13:47 pts/0 00:00:00 /net/java/jdk1.3/bin/i386/native_threads/java -Dtomcat.home=./.. org.apache.tomcat.startup.Tomcat 040 S vikas 905 903 0 60 0- 35712 nanosl 13:47 pts/0 00:00:00 /net/java/jdk1.3/bin/i386/native_threads/java -Dtomcat.home=./.. org.apache.tomcat.startup.Tomcat ... ... ... 040 S vikas 948 903 0 60 0- 35712 nanosl 13:47 pts/0 00:00:00 /net/java/jdk1.3/bin/i386/native_threads/java -Dtomcat.home=./.. org.apache.tomcat.startup.Tomcat 040 S vikas 949 903 0 60 0- 35712 nanosl 13:47 pts/0 00:00:00 /net/java/jdk1.3/bin/i386/native_threads/java -Dtomcat.home=./.. org.apache.tomcat.startup.Tomcat == It looks like that PID 858 creates a process (PID-903) which in turn creates 46 Tomcat processes (PIDS: 904-949). Where is it configured? Is there any way I can change this? So that I can start Tomcat with the no. of processes I want, say 25, 100.. whatever.. Any help in this regard is appreciated. Thanks, Vikas.
How many tomcat processes ??? (more than 20 for me...)
Hello to all, I've got currently a big problem. I have too many tomcat processes. I'm running under Linux Mandrake, latest version. I've made a simple test, I called bin/startup.sh without calling any web page. /usr/local/jdk1.3/jre/bin/exe/ja means java --Dtomcat_home so a tomcat process What is happening ? Why do I have httpd process ?? My machine is not on a open network and noone can access my machine. If I shutdown tomcat, I don't have any process anymore At 10:57, I did bin/startup.sh and then ps- fe at 11.37 !! sam 5828 1 0 10:57 pts/100:00:02 /usr/local/jdk1.3/jre/bin/exe/ja sam 5837 5828 0 10:57 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5838 5837 0 10:57 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5839 5837 0 10:57 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5840 5837 0 10:57 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5847 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5848 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5849 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5850 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5851 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5852 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5853 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5854 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5855 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5856 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5857 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5858 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5859 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5860 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5861 5837 0 10:58 pts/100:00:09 /usr/local/jdk1.3/jre/bin/exe/ja sam 5862 5837 1 10:58 pts/100:00:24 /usr/local/jdk1.3/jre/bin/exe/ja sam 5863 5837 1 10:58 pts/100:00:40 /usr/local/jdk1.3/jre/bin/exe/ja sam 5864 5837 2 10:58 pts/100:00:57 /usr/local/jdk1.3/jre/bin/exe/ja sam 5865 5837 3 10:58 pts/100:01:17 /usr/local/jdk1.3/jre/bin/exe/ja sam 5866 5837 4 10:58 pts/100:01:36 /usr/local/jdk1.3/jre/bin/exe/ja sam 5867 5837 5 10:58 pts/100:02:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5868 5837 6 10:58 pts/100:02:25 /usr/local/jdk1.3/jre/bin/exe/ja sam 5869 5837 7 10:58 pts/100:02:53 /usr/local/jdk1.3/jre/bin/exe/ja sam 5870 5837 8 10:58 pts/100:03:20 /usr/local/jdk1.3/jre/bin/exe/ja sam 5871 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja nobody5960 3858 0 11:15 ?00:00:00 /usr/share/apache/bin/httpd nobody5966 3858 0 11:19 ?00:00:00 /usr/share/apache/bin/httpd nobody5978 3858 0 11:23 ?00:00:00 /usr/share/apache/bin/httpd nobody5981 3858 0 11:27 ?00:00:00 /usr/share/apache/bin/httpd nobody5990 3858 0 11:31 ?00:00:00 /usr/share/apache/bin/httpd sam 6000 5837 0 11:35 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 6001 5837 0 11:35 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 6002 5837 0 11:35 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 6003 5837 0 11:35 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 6004 5837 0 11:35 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 6005 5837 0 11:35 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 6006 5837 0 11:35 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja nobody6007 3858 0 11:35 ?00:00:00 /usr/share/apache/bin/httpd sam 6008 5837 0 11:35 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 6009 5837 0 11:35 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 6010 5837 0 11:35 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja root 6024 2072 0 11:37 pts/300:00:00 ps -fe
Re: How many tomcat processes ??? (more than 20 for me...)
ooops I forgot to say I'm using tomcat 3.2.1
RE: How many tomcat processes ??? (more than 20 for me...)
The processes are not processes but rather Threads and they are displayed as processes due to the Linux implementation of Threads. Why is HTTPD started? Dont know, look at your startup script for tomcat. It probably runs tomcat as mod_jk which requires HTTPD. -Original Message- From: Samuel Arnod-Prin [mailto:[EMAIL PROTECTED]] Sent: den 27 mars 2001 11:51 To: [EMAIL PROTECTED] Subject: How many tomcat processes ??? (more than 20 for me...) Hello to all, I've got currently a big problem. I have too many tomcat processes. I'm running under Linux Mandrake, latest version. I've made a simple test, I called bin/startup.sh without calling any web page. /usr/local/jdk1.3/jre/bin/exe/ja means java --Dtomcat_home so a tomcat process What is happening ? Why do I have httpd process ?? My machine is not on a open network and noone can access my machine. If I shutdown tomcat, I don't have any process anymore At 10:57, I did bin/startup.sh and then ps- fe at 11.37 !! sam 5828 1 0 10:57 pts/100:00:02 /usr/local/jdk1.3/jre/bin/exe/ja sam 5837 5828 0 10:57 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5838 5837 0 10:57 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5839 5837 0 10:57 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5840 5837 0 10:57 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5847 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5848 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5849 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5850 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5851 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5852 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5853 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5854 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5855 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5856 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5857 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5858 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5859 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5860 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5861 5837 0 10:58 pts/100:00:09 /usr/local/jdk1.3/jre/bin/exe/ja sam 5862 5837 1 10:58 pts/100:00:24 /usr/local/jdk1.3/jre/bin/exe/ja sam 5863 5837 1 10:58 pts/100:00:40 /usr/local/jdk1.3/jre/bin/exe/ja sam 5864 5837 2 10:58 pts/100:00:57 /usr/local/jdk1.3/jre/bin/exe/ja sam 5865 5837 3 10:58 pts/100:01:17 /usr/local/jdk1.3/jre/bin/exe/ja sam 5866 5837 4 10:58 pts/100:01:36 /usr/local/jdk1.3/jre/bin/exe/ja sam 5867 5837 5 10:58 pts/100:02:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5868 5837 6 10:58 pts/100:02:25 /usr/local/jdk1.3/jre/bin/exe/ja sam 5869 5837 7 10:58 pts/100:02:53 /usr/local/jdk1.3/jre/bin/exe/ja sam 5870 5837 8 10:58 pts/100:03:20 /usr/local/jdk1.3/jre/bin/exe/ja sam 5871 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja nobody5960 3858 0 11:15 ?00:00:00 /usr/share/apache/bin/httpd nobody5966 3858 0 11:19 ?00:00:00 /usr/share/apache/bin/httpd nobody5978 3858 0 11:23 ?00:00:00 /usr/share/apache/bin/httpd nobody5981 3858 0 11:27 ?00:00:00 /usr/share/apache/bin/httpd nobody5990 3858 0 11:31 ?00:00:00 /usr/share/apache/bin/httpd sam 6000 5837 0 11:35 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 6001 5837 0 11:35 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 6002 5837 0 11:35 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 6003 5837 0 11:35 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 6004 5837 0 11:35 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 6005 5837 0 11:35 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 6006 5837 0 11:35 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja nobody6007 3858 0 11:35 ?00:00:00 /usr/share/apache/bin/httpd sam 6008 5837 0 11:35 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 6009 5837 0 11:35 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 6010 5837 0 11:35 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja root 6024 2072 0 11:37 pts/300:00:00 ps -fe
Re: How many tomcat processes ??? (more than 20 for me...)
of course, I meant threads for process, what I wanted to underline is that there could be a link between httpd and tomcat.. httpd is started because I use mod_jk but I don't understand why httpd creates more processes when I do nothing... as tomcat does "Cato, Christopher" wrote: The processes are not processes but rather Threads and they are displayed as processes due to the Linux implementation of Threads. Why is HTTPD started? Dont know, look at your startup script for tomcat. It probably runs tomcat as mod_jk which requires HTTPD. -Original Message- From: Samuel Arnod-Prin [mailto:[EMAIL PROTECTED]] Sent: den 27 mars 2001 11:51 To: [EMAIL PROTECTED] Subject: How many tomcat processes ??? (more than 20 for me...) Hello to all, I've got currently a big problem. I have too many tomcat processes. I'm running under Linux Mandrake, latest version. I've made a simple test, I called bin/startup.sh without calling any web page. /usr/local/jdk1.3/jre/bin/exe/ja means java --Dtomcat_home so a tomcat process What is happening ? Why do I have httpd process ?? My machine is not on a open network and noone can access my machine. If I shutdown tomcat, I don't have any process anymore At 10:57, I did bin/startup.sh and then ps- fe at 11.37 !! sam 5828 1 0 10:57 pts/100:00:02 /usr/local/jdk1.3/jre/bin/exe/ja sam 5837 5828 0 10:57 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5838 5837 0 10:57 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5839 5837 0 10:57 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5840 5837 0 10:57 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5847 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5848 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5849 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5850 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5851 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5852 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5853 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5854 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5855 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5856 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5857 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5858 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5859 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5860 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5861 5837 0 10:58 pts/100:00:09 /usr/local/jdk1.3/jre/bin/exe/ja sam 5862 5837 1 10:58 pts/100:00:24 /usr/local/jdk1.3/jre/bin/exe/ja sam 5863 5837 1 10:58 pts/100:00:40 /usr/local/jdk1.3/jre/bin/exe/ja sam 5864 5837 2 10:58 pts/100:00:57 /usr/local/jdk1.3/jre/bin/exe/ja sam 5865 5837 3 10:58 pts/100:01:17 /usr/local/jdk1.3/jre/bin/exe/ja sam 5866 5837 4 10:58 pts/100:01:36 /usr/local/jdk1.3/jre/bin/exe/ja sam 5867 5837 5 10:58 pts/100:02:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 5868 5837 6 10:58 pts/100:02:25 /usr/local/jdk1.3/jre/bin/exe/ja sam 5869 5837 7 10:58 pts/100:02:53 /usr/local/jdk1.3/jre/bin/exe/ja sam 5870 5837 8 10:58 pts/100:03:20 /usr/local/jdk1.3/jre/bin/exe/ja sam 5871 5837 0 10:58 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja nobody5960 3858 0 11:15 ?00:00:00 /usr/share/apache/bin/httpd nobody5966 3858 0 11:19 ?00:00:00 /usr/share/apache/bin/httpd nobody5978 3858 0 11:23 ?00:00:00 /usr/share/apache/bin/httpd nobody5981 3858 0 11:27 ?00:00:00 /usr/share/apache/bin/httpd nobody5990 3858 0 11:31 ?00:00:00 /usr/share/apache/bin/httpd sam 6000 5837 0 11:35 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 6001 5837 0 11:35 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 6002 5837 0 11:35 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 6003 5837 0 11:35 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 6004 5837 0 11:35 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 6005 5837 0 11:35 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja sam 6006 5837 0 11:35 pts/100:00:00 /usr/local/jdk1.3/jre/bin/exe/ja nobody6007 3858 0 11:35 ?00:00:00 /usr/share/apache/bin/httpd sam 6008 5837 0 11:35 pts/1
RE: How many tomcat processes ??? (more than 20 for me...)
Httpd (apache) usually starts a number of processes specified in httpd.conf. Below is an excerpt of my ps -ef output: root 29819 1 0 Mar22 ?00:00:02 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29864 29819 0 Mar22 ?00:00:00 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29865 29864 0 Mar22 ?00:00:08 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29866 29864 0 Mar22 ?00:00:00 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29867 29864 0 Mar22 ?00:00:00 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29868 29864 0 Mar22 ?00:00:00 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29869 29864 0 Mar22 ?00:00:00 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29870 29864 0 Mar22 ?00:00:00 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29871 29864 0 Mar22 ?00:00:00 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29872 29864 0 Mar22 ?00:00:00 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29873 29864 0 Mar22 ?00:00:00 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29874 29864 0 Mar22 ?00:00:00 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29875 29864 0 Mar22 ?00:00:00 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29876 29864 0 Mar22 ?00:00:00 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29877 29864 0 Mar22 ?00:00:00 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29878 29864 0 Mar22 ?00:00:00 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29879 29864 0 Mar22 ?00:00:00 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29880 29864 0 Mar22 ?00:00:00 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29881 29864 0 Mar22 ?00:00:00 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29882 29864 0 Mar22 ?00:00:00 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29883 29864 0 Mar22 ?00:00:00 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29884 29864 0 Mar22 ?00:00:00 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29885 29864 0 Mar22 ?00:00:00 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29886 29864 0 Mar22 ?00:00:00 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29887 29864 0 Mar22 ?00:00:00 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29888 29864 0 Mar22 ?00:00:00 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29889 29864 0 Mar22 ?00:00:00 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29890 29864 0 Mar22 ?00:00:00 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29891 29864 0 Mar22 ?00:00:00 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29892 29864 0 Mar22 ?00:00:00 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29893 29864 0 Mar22 ?00:00:00 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29894 29864 0 Mar22 ?00:00:00 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29895 29864 0 Mar22 ?00:00:00 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29896 29864 0 Mar22 ?00:00:00 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29897 29864 0 Mar22 ?00:00:01 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29898 29864 0 Mar22 ?00:00:00 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= root 29899 29864 0 Mar22 ?00:00:08 /usr/local/jdk1.3/bin/i386/native_threads/java -Dtomcat.home= nobody3562 612 0 Mar25 ?00:00:00 httpd nobody3563 612 0 Mar25 ?00:00:00 httpd nobody3564 612 0 Mar25 ?00:00:00 httpd nobody3565 612 0 Mar25 ?00:00:00 httpd nobody3566 612 0 Mar25 ?00:00:00 httpd nobody3567 612 0 Mar25 ?00:00:00 httpd nobody3568 612 0 Mar25 ?00:00:00 httpd nobody3569 612 0 Mar25 ?00:00:00 httpd nobody3570 612 0 Mar25 ?00:00:00 httpd nobody3571 612 0 Mar25 ?00:00:00 httpd So, yours looks okay to me.. Mine looks somewhat the same... -Original Message- From: Samuel Arnod-Prin [mailto:[EMAIL PROTECTED]] Sent: den 27 mars 2001 13:05 To: [EMAIL PROTECTED] Subject: Re: How many tomcat processes ??? (more than 20 for me
Re: How many tomcat processes ??? (more than 20 for me...)
t the same...
-Original Message-
From: Samuel Arnod-Prin [mailto:[EMAIL PROTECTED]]
Sent: den 27 mars 2001 13:05
To: [EMAIL PROTECTED]
Subject: Re: How many tomcat processes ??? (more than 20 for me...)
of course, I meant threads for process,
what I wanted to underline is that there could be a link
between httpd and
tomcat..
httpd is started because I use mod_jk
but I don't understand why httpd creates more processes when
I do nothing... as
tomcat does
"Cato, Christopher" wrote:
The processes are not processes but rather Threads and they
are displayed as
processes due to the Linux implementation of Threads. Why
is HTTPD started?
Dont know, look at your startup script for tomcat. It
probably runs tomcat
as mod_jk which requires HTTPD.
-Original Message-
From: Samuel Arnod-Prin [mailto:[EMAIL PROTECTED]]
Sent: den 27 mars 2001 11:51
To: [EMAIL PROTECTED]
Subject: How many tomcat processes ??? (more than 20 for me...)
Hello to all,
I've got currently a big problem. I have too many tomcat
processes. I'm
running under Linux Mandrake, latest version.
I've made a simple test, I called bin/startup.sh without
calling any web
page.
/usr/local/jdk1.3/jre/bin/exe/ja means java
--Dtomcat_home so a
tomcat process
What is happening ? Why do I have httpd process ?? My machine
is not on
a open network and noone can access my machine. If I
shutdown tomcat, I
don't have any process anymore
At 10:57, I did bin/startup.sh and then ps- fe at 11.37 !!
sam 5828 1 0 10:57 pts/100:00:02
/usr/local/jdk1.3/jre/bin/exe/ja
sam 5837 5828 0 10:57 pts/100:00:00
/usr/local/jdk1.3/jre/bin/exe/ja
sam 5838 5837 0 10:57 pts/100:00:00
/usr/local/jdk1.3/jre/bin/exe/ja
sam 5839 5837 0 10:57 pts/100:00:00
/usr/local/jdk1.3/jre/bin/exe/ja
sam 5840 5837 0 10:57 pts/100:00:00
/usr/local/jdk1.3/jre/bin/exe/ja
sam 5847 5837 0 10:58 pts/100:00:00
/usr/local/jdk1.3/jre/bin/exe/ja
sam 5848 5837 0 10:58 pts/100:00:00
/usr/local/jdk1.3/jre/bin/exe/ja
sam 5849 5837 0 10:58 pts/100:00:00
/usr/local/jdk1.3/jre/bin/exe/ja
sam 5850 5837 0 10:58 pts/100:00:00
/usr/local/jdk1.3/jre/bin/exe/ja
sam 5851 5837 0 10:58 pts/100:00:00
/usr/local/jdk1.3/jre/bin/exe/ja
sam 5852 5837 0 10:58 pts/100:00:00
/usr/local/jdk1.3/jre/bin/exe/ja
sam 5853 5837 0 10:58 pts/100:00:00
/usr/local/jdk1.3/jre/bin/exe/ja
sam 5854 5837 0 10:58 pts/100:00:00
/usr/local/jdk1.3/jre/bin/exe/ja
sam 5855 5837 0 10:58 pts/100:00:00
/usr/local/jdk1.3/jre/bin/exe/ja
sam 5856 5837 0 10:58 pts/100:00:00
/usr/local/jdk1.3/jre/bin/exe/ja
sam 5857 5837 0 10:58 pts/100:00:00
/usr/local/jdk1.3/jre/bin/exe/ja
sam 5858 5837 0 10:58 pts/100:00:00
/usr/local/jdk1.3/jre/bin/exe/ja
sam 5859 5837 0 10:58 pts/100:00:00
/usr/local/jdk1.3/jre/bin/exe/ja
sam 5860 5837 0 10:58 pts/100:00:00
/usr/local/jdk1.3/jre/bin/exe/ja
sam 5861 5837 0 10:58 pts/100:00:09
/usr/local/jdk1.3/jre/bin/exe/ja
sam 5862 5837 1 10:58 pts/100:00:24
/usr/local/jdk1.3/jre/bin/exe/ja
sam 5863 5837 1 10:58 pts/100:00:40
/usr/local/jdk1.3/jre/bin/exe/ja
sam 5864 5837 2 10:58 pts/100:00:57
/usr/local/jdk1.3/jre/bin/exe/ja
sam 5865 5837 3 10:58 pts/100:01:17
/usr/local/jdk1.3/jre/bin/exe/ja
sam 5866 5837 4 10:58 pts/100:01:36
/usr/local/jdk1.3/jre/bin/exe/ja
sam 5867 5837 5 10:58 pts/100:02:00
/usr/local/jdk1.3/jre/bin/exe/ja
sam 5868 5837 6 10:58 pts/100:02:25
/usr/local/jdk1.3/jre/bin/exe/ja
sam 5869 5837 7 10:58 pts/100:02:53
/usr/local/jdk1.3/jre/bin/exe/ja
sam 5870 5837 8 10:58 pts/100:03:20
/usr/local/jdk1.3/jre/bin/exe/ja
sam 5871 5837 0 10:58 pts/100:00:00
/usr/local/jdk1.3/jre/bin/exe/ja
nobody5960 3858 0 11:15 ?00:00:00
/usr/share/apache/bin/httpd
nobody5966 3858 0 11:19 ?00:00:00
/usr/share/apache/bin/httpd
nobody5978 3858 0 11:23 ?00:00:00
/usr/share/apache/bin/httpd
nobody5981 3858 0 11:27 ?00:00:00
/usr/share/apache/bin/httpd
nobody5990 3858 0 11:31 ?00:00:00
/usr/share/apache/bin/httpd
sam 6000 5837 0 11:35 pts/100:00:00
/usr/local/jdk1.3/jre/bin/exe/ja
sam 6001 5837 0 11:35 pts/100:00:00
/usr/local/jdk1.3/jre/bin/exe/ja
sam 6002 5837 0 11:35 pts/100:00:00
/usr/local/jdk1.3/jre/bin/exe/ja
sam
AW: Actually RE: Tomcat processes... (to Christoph Rooms)
Which jdk 1.3 do you use, Sun or IBM ? Sun's jdk tends to use much more memory than the IBM jdk. (At least that's our experience) -Ursprngliche Nachricht- Von: Christoph Rooms [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 24. Januar 2001 23:55 An: [EMAIL PROTECTED] Betreff: RE: Actually RE: Tomcat processes... (to Christoph Rooms) snip/ I am using 3.2.1 ... using jdk 1.3. Strange ... but how is it possible that I'm getting 140MB and another user only 10 ? snip/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Re: Actually RE: Tomcat processes... (to Christoph Rooms)
If you're talking about java processes it's really just one process and what you're seeing are actually threads. It's normal. Michael Wentzel wrote: I'm running Tomcat on linux. From the moment I start up Tomcat, I see 51 processes and these processes takes up 142 MB of memory. Is this normal ? Doesn't sound right to me. Can you send a copy or the long output of ps? As well as a description of your configuration(OS, tomcat standalone vs tomcat/apache, webapp configuration, etc...). PS - Changed subject of thread to more appropriate subject. --- Michael Wentzel Software Developer A HREF="http://www.aswethink.com"Software As We Think/A A HREF="mailto:[EMAIL PROTECTED]"Michael Wentzel/A - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Actually RE: Tomcat processes... (to Christoph Rooms)
But is it normal that it takes 140 MB of RAM ? (I know that I only have to count 1 process) I have a provider that wanted to support servlets using tomcat. But it seems I managed to bring down his machine that was online for more then 200 days. What's the best way to avoid this ? greetz, Christoph -Original Message- From: tlittle [mailto:tlittle]On Behalf Of Trevor Little Sent: woensdag 24 januari 2001 22:37 To: [EMAIL PROTECTED] Subject: Re: Actually RE: Tomcat processes... (to Christoph Rooms) If you're talking about java processes it's really just one process and what you're seeing are actually threads. It's normal. Michael Wentzel wrote: I'm running Tomcat on linux. From the moment I start up Tomcat, I see 51 processes and these processes takes up 142 MB of memory. Is this normal ? Doesn't sound right to me. Can you send a copy or the long output of ps? As well as a description of your configuration(OS, tomcat standalone vs tomcat/apache, webapp configuration, etc...). PS - Changed subject of thread to more appropriate subject. --- Michael Wentzel Software Developer A HREF="http://www.aswethink.com"Software As We Think/A A HREF="mailto:[EMAIL PROTECTED]"Michael Wentzel/A - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Actually RE: Tomcat processes... (to Christoph Rooms)
Hi, How do I use these parameters ? Can you give more info on it ? An example ? thanks ! Christoph -Original Message- From: CPC Livelink Admin [mailto:[EMAIL PROTECTED]] Sent: woensdag 24 januari 2001 22:57 To: [EMAIL PROTECTED] Subject: RE: Actually RE: Tomcat processes... (to Christoph Rooms) I don't suppose your setup is using the parameters which set initial heap size on the java command line are they. My installs run 10% of the size you are quoting when run out of the box. Regards, Paul -Original Message- From: Christoph Rooms [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 24, 2001 4:57 PM To: [EMAIL PROTECTED] Subject: RE: Actually RE: Tomcat processes... (to Christoph Rooms) But is it normal that it takes 140 MB of RAM ? (I know that I only have to count 1 process) I have a provider that wanted to support servlets using tomcat. But it seems I managed to bring down his machine that was online for more then 200 days. What's the best way to avoid this ? greetz, Christoph -Original Message- From: tlittle [mailto:tlittle]On Behalf Of Trevor Little Sent: woensdag 24 januari 2001 22:37 To: [EMAIL PROTECTED] Subject: Re: Actually RE: Tomcat processes... (to Christoph Rooms) If you're talking about java processes it's really just one process and what you're seeing are actually threads. It's normal. Michael Wentzel wrote: I'm running Tomcat on linux. From the moment I start up Tomcat, I see 51 processes and these processes takes up 142 MB of memory. Is this normal ? Doesn't sound right to me. Can you send a copy or the long output of ps? As well as a description of your configuration(OS, tomcat standalone vs tomcat/apache, webapp configuration, etc...). PS - Changed subject of thread to more appropriate subject. --- Michael Wentzel Software Developer A HREF="http://www.aswethink.com"Software As We Think/A A HREF="mailto:[EMAIL PROTECTED]"Michael Wentzel/A - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
RE: Actually RE: Tomcat processes... (to Christoph Rooms)
Hi, I am using 3.2.1 ... using jdk 1.3. Strange ... but how is it possible that I'm getting 140MB and another user only 10 ? I don't understand ... Christoph -Original Message- From: Steve Ruby [mailto:[EMAIL PROTECTED]] Sent: woensdag 24 januari 2001 23:40 To: [EMAIL PROTECTED] Subject: Re: Actually RE: Tomcat processes... (to Christoph Rooms) Christoph Rooms wrote: Hi, So I putted -Xmx24m in after the java command in tomcat.sh What I see he now uses 50M. Anybody knows why ? greetz, Christoph You can only configure the heap size for java, you can't limit the total memory requirements of the JVM... Limiting the heap should catch any run-away servlets that might take too much memory, or even tomcat in the even of a leak. What version of tomcat are you using? I started up tomcat 4.0 under linux with -Xmx24m and hit a couple of servlets and I'm at 40meg VSZ and 14 RSZ (using green threads). - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
Multiple tomcat processes
I could not find this in the faq... I launch Tomcat (3.2.1 under linux JDK 1.3) and I launches a bunch of processes. However, it does not appear that it is using the memory that it should if these were all independent processes. Are these just threads, or what? Thx, Joe Laffey LAFFEY Computer Imaging St. Louis, MO - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
tomcat processes
Hi, I'm using Tomcat 3.2-b7 on Linux and I noticed that when I start tomcat it opens a lot of processes, all of theme running org.apache.tomcat.startup.Tomcat. Why there are so many processes (in my case about 50)? how this processes can be controlled? Thanks.
Re: tomcat processes
The Linux ps command mis-reports threads as processes. http://www.mail-archive.com/tomcat-user@jakarta.apache.org/msg00639.html http://www.mail-archive.com/tomcat-user@jakarta.apache.org/msg00583.html *** REPLY SEPARATOR *** On 12/26/2000 at 8:41 PM Eli Sherman wrote: Hi, I'm using Tomcat 3.2-b7 on Linux and I noticed that when I start tomcat it opens a lot of processes, all of theme running org.apache.tomcat.startup.Tomcat. Why there are so many processes (in my case about 50)? how this processes can be controlled? Thanks.
RE: tomcat processes
archives and google will be of great help. Shuklix -Original Message- From: Eli Sherman [mailto:[EMAIL PROTECTED]] Sent: Wednesday, December 27, 2000 12:12 AM To: '[EMAIL PROTECTED]' Subject: tomcat processes Hi, I'm using Tomcat 3.2-b7 on Linux and I noticed that when I start tomcat it opens a lot of processes, all of theme running org.apache.tomcat.startup.Tomcat. Why there are so many processes (in my case about 50)? how this processes can be controlled? Thanks.
