Tomcat Hanging up !!!
Hi All, We have integrated two servers the first one is IBM_HTTP_SERVER and Tomcat 3.2.1. Here the IBM server acts the web server and Tomcat as the container for the Servlet and JSP. We could integrate both using the mod_jk connecter and deployed our application. The problem is Tomcat is hanging up and when we try to restart the Tomcat server it is not getting restarted. We had to restart the machine itself once again. Is there any solution for rectifying this problem. That too the tomcat server is not hanging up immediately Its hanging after few hours after successfully running the application We are not getting any error messages like out of memory or Stack overflow Can any one suggest a suitable way to get out of this. We are using the following configuratios. Our Server Machine is Windows 2000 server we have installed JDK 1.3.1_13 on our machine IBM_HTTP_SERVER as mentioned previously Tomcat 3.2.1 Container Thanks in Advance. Regards, Srinivas. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: Tomcat Hanging up !!!
Hi Come on, Tomcat 3.2.1??? This is way tooo old. JDK 1.3.1_13? The same! IBM_HTTP_SERVER? predecessor of Apache httpd? Again. Remove them altogether! Install jdk1.4.2_05 and tomcat 5.0.28. No neither use httpd NOR mod_jk. You will be fine and happy with this. I doublt, you will find someone to assist you with that old version of tomcat. Additionally, you propably won't find current mod_jk versions, which are tested against that version. Even in the 3.x branch, 3.3.2 is current! Regards, Steffen smime.p7s Description: S/MIME cryptographic signature
RE: Tomcat Hanging up !!!
Hi Steffen, It is a very old server which is used by the company. And the configuration for that is like that. If I install Apache 2.0 and Tomcat 4.1 and use mod_jk that is compatible for that I don't what Issues will be raised by that. More over the previous configuration was working fine till 15 days back but unfortunately the server crashed. So I had restore that some how I could restore it but tomcat is hanging up after running for few hours I am unable to understand the problem. I have another instance where I have Apache 2.0 and Tomcat 4.1 with a different mod_jk. It is working fine but can't say when the load on the server increase what will happen. Regards, Srinivas. -Original Message- From: Steffen Heil [mailto:[EMAIL PROTECTED] Sent: Thursday, September 23, 2004 4:08 PM To: 'Tomcat Users List' Subject: AW: Tomcat Hanging up !!! Hi Come on, Tomcat 3.2.1??? This is way tooo old. JDK 1.3.1_13? The same! IBM_HTTP_SERVER? predecessor of Apache httpd? Again. Remove them altogether! Install jdk1.4.2_05 and tomcat 5.0.28. No neither use httpd NOR mod_jk. You will be fine and happy with this. I doublt, you will find someone to assist you with that old version of tomcat. Additionally, you propably won't find current mod_jk versions, which are tested against that version. Even in the 3.x branch, 3.3.2 is current! Regards, Steffen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: Tomcat Hanging up !!!
Hi If I install Apache 2.0 and Tomcat 4.1 and use mod_jk that is compatible for that I don't what issues will be raised by that. Right, that is why I suggest using tomcat ONLY. This works, and even when tomcat 3.2.1 might be slower that ibm_httpd, tomcat 5.0 is really fast and is at almost at the level of apache. Just put tomcat 5 on a test mashine, put your app in and test, you will see, this works within a few minutes! Regards, Steffen smime.p7s Description: S/MIME cryptographic signature
Re: AW: Tomcat Hanging up !!!
Steffen Heil wrote: Hi If I install Apache 2.0 and Tomcat 4.1 and use mod_jk that is compatible for that I don't what issues will be raised by that. Right, that is why I suggest using tomcat ONLY. This works, and even when tomcat 3.2.1 might be slower that ibm_httpd, tomcat 5.0 is really fast and is at almost at the level of apache. Just put tomcat 5 on a test mashine, put your app in and test, you will see, this works within a few minutes! Regards, Steffen I only use Tomcat any more except cases where I have to run some other things on certain servers. Tomcat 5 branch. I haven't had any issues yet. Wade - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat Hanging...
Hi, First step in debugging this type of issue: take Apache and the connectors out of the equation. Run tomcat standalone and see if the issue still persists. My guess would be not. You're barking up the wrong tree completely when you think this is a Tomcat limitation. Tomcat instances routinely handle thousands of connections and millions of hits per day. How much of that is concurrent depends on your webapp and hardware of course. Yoav Shapira Millennium Research Informatics -Original Message- From: Ercan, Tolga [mailto:[EMAIL PROTECTED] Sent: Monday, September 20, 2004 9:24 PM To: [EMAIL PROTECTED] Subject: Tomcat Hanging... I'm currently trying to deploy tomcat and we're having a problem with tomcat appearing to hang. Here's the environment: Apache 1.3.19 Mod_jk Tomcat 5.0.27 We have 5 apache servers, connecting to 2 tomcat workers via mod_jk. These tomcat workers are load balanced via JK, and we've clustered the two instances. What we're seeing is the environment work for about 5 minutes. During that time, the number of open connections to either tomcat instance steadily increases to 250+. When we reach that threshold, mod_jk log starts to report the following errors for both workers: [Fri Sep 10 16:43:00 2004] [jk_ajp_common.c (1024)]: Error connecting to the Tomcat process. [Fri Sep 10 16:43:00 2004] [jk_ajp_common.c (1468)]: sending request to tomcat failed in send loop. err=1 [Fri Sep 10 16:43:21 2004] [jk_connect.c (188)]: jk_open_socket, connect() failed errno = 145 [Fri Sep 10 16:43:21 2004] [jk_ajp_common.c (720)]: Error connecting to tomcat. Tomcat is probably not started or is listening on the wrong host/port (xx.xx.xx.xx:8030). Failed errno = 145 [Fri Sep 10 16:43:21 2004] [jk_ajp_common.c (1024)]: Error connecting to the Tomcat process. [Fri Sep 10 16:43:21 2004] [jk_ajp_common.c (1468)]: sending request to tomcat failed in send loop. err=2 [Fri Sep 10 16:43:21 2004] [jk_ajp_common.c (1477)]: Error connecting to tomcat. Tomcat is probably not started or is listening on the wrong port. worker=worker1 failed errno = 145 The tomcat servers (worker1, worker2) are both up, and listening on port 8030 but at this point, the application appears to hang. My questions are: 1) Should there be this many open connections? Is having this many connections open create problems communicating with tomcat? 2) Is this a known issue? I haven't seen anyone else report the problem, so I'm assuming no... 3) Is this a tomcat performance issue? What are the performance limitations of tomcat? Or am I barking up the wrong tree in thinking this is a tomcat performance issue? Thanks! ~t 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]
Tomcat Hanging...
I'm currently trying to deploy tomcat and we're having a problem with tomcat appearing to hang. Here's the environment: Apache 1.3.19 Mod_jk Tomcat 5.0.27 We have 5 apache servers, connecting to 2 tomcat workers via mod_jk. These tomcat workers are load balanced via JK, and we've clustered the two instances. What we're seeing is the environment work for about 5 minutes. During that time, the number of open connections to either tomcat instance steadily increases to 250+. When we reach that threshold, mod_jk log starts to report the following errors for both workers: [Fri Sep 10 16:43:00 2004] [jk_ajp_common.c (1024)]: Error connecting to the Tomcat process. [Fri Sep 10 16:43:00 2004] [jk_ajp_common.c (1468)]: sending request to tomcat failed in send loop. err=1 [Fri Sep 10 16:43:21 2004] [jk_connect.c (188)]: jk_open_socket, connect() failed errno = 145 [Fri Sep 10 16:43:21 2004] [jk_ajp_common.c (720)]: Error connecting to tomcat. Tomcat is probably not started or is listening on the wrong host/port (xx.xx.xx.xx:8030). Failed errno = 145 [Fri Sep 10 16:43:21 2004] [jk_ajp_common.c (1024)]: Error connecting to the Tomcat process. [Fri Sep 10 16:43:21 2004] [jk_ajp_common.c (1468)]: sending request to tomcat failed in send loop. err=2 [Fri Sep 10 16:43:21 2004] [jk_ajp_common.c (1477)]: Error connecting to tomcat. Tomcat is probably not started or is listening on the wrong port. worker=worker1 failed errno = 145 The tomcat servers (worker1, worker2) are both up, and listening on port 8030 but at this point, the application appears to hang. My questions are: 1) Should there be this many open connections? Is having this many connections open create problems communicating with tomcat? 2) Is this a known issue? I haven't seen anyone else report the problem, so I'm assuming no... 3) Is this a tomcat performance issue? What are the performance limitations of tomcat? Or am I barking up the wrong tree in thinking this is a tomcat performance issue? Thanks! ~t
tomcat hanging during SSL handshake
We're running tomcat 5.0.16 with Java 1.4.1. I'm seeing this problem after things have been running fine for a while and the load starts increasing. What happens is the HTTP Coyote connector does not gracefully recover from an OutOfMemory exception and it gets into a situation where it hangs in the middle of the SSL-handshake. Is there a known bug that causes this to happen? We're thinking about upgrading to 5.0.24, but it'd be nice to know that this will solve this problem rather than just hope so. RW _ FREE pop-up blocking with the new MSN Toolbar get it now! http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Can large upload cause tomcat hanging?
Hi, I uploaded a 70Mb file using struts-1.1. The JVM process (jre-1.2.4_02, Linux, SuSe-8.1) got much larger and a couple of hours later tomcat didn't react to the most of the events. What can be the reason? Additionally I found strange the tomcat didn't create the localhost_log... files since the last startup. Here I are the data provided by top: SIZE: 175M RSS: 165M SHARE: 38980 STAT: S N %CPU: 0.0% %MEM: 33.3 TIME 0:05 The machine has 512Mb. Zsolt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Can large upload cause tomcat hanging?
Howdy, The most likely reason is that java ran out of memory. Yoav Shapira Millennium ChemInformatics -Original Message- From: Zsolt Koppany [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 10, 2003 1:58 PM To: Tomcat Users List Subject: Can large upload cause tomcat hanging? Hi, I uploaded a 70Mb file using struts-1.1. The JVM process (jre-1.2.4_02, Linux, SuSe-8.1) got much larger and a couple of hours later tomcat didn't react to the most of the events. What can be the reason? Additionally I found strange the tomcat didn't create the localhost_log... files since the last startup. Here I are the data provided by top: SIZE: 175M RSS: 165M SHARE: 38980 STAT: S N %CPU: 0.0% %MEM: 33.3 TIME 0:05 The machine has 512Mb. Zsolt - 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]
RE: Can large upload cause tomcat hanging?
If the file is in memory, then that might explain the memory expansion. Try increasing tomcat startup memory parameters. Also, you should look at how the file data is being handled, i.e. is it all in memory at once? -Original Message- From: Zsolt Koppany [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 10, 2003 1:52 PM To: Jakarta Commons Users List Subject: Can large upload cause tomcat hanging? Hi, I uploaded a 70Mb file using struts-1.1. The JVM process (jre-1.2.4_02, Linux, SuSe-8.1) got much larger and a couple of hours later tomcat didn't react to the most of the events. What can be the reason? Additionally I found strange the tomcat didn't create the localhost_log... files since the last startup. Here I are the data provided by top: SIZE: 175M RSS: 165M SHARE: 38980 STAT: S N %CPU: 0.0% %MEM: 33.3 TIME 0:05 The machine has 512Mb. Zsolt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This electronic transmission is strictly confidential to Smith Nephew and intended solely for the addressee. It may contain information which is covered by legal, professional or other privilege. If you are not the intended addressee, or someone authorized by the intended addressee to receive transmissions on behalf of the addressee, you must not retain, disclose in any form, copy or take any action in reliance on this transmission. If you have received this transmission in error, please notify the sender as soon as possible and destroy this message. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Can large upload cause tomcat hanging?
Increase your maxHeap in the JVM instance running tomcat. --- Zsolt Koppany [EMAIL PROTECTED] wrote: Hi, I uploaded a 70Mb file using struts-1.1. The JVM process (jre-1.2.4_02, Linux, SuSe-8.1) got much larger and a couple of hours later tomcat didn't react to the most of the events. What can be the reason? Additionally I found strange the tomcat didn't create the localhost_log... files since the last startup. Here I are the data provided by top: SIZE: 175M RSS: 165M SHARE: 38980 STAT: S N %CPU: 0.0% %MEM: 33.3 TIME 0:05 The machine has 512Mb. Zsolt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] __ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Can large upload cause tomcat hanging?
Hi, I uploaded a 70Mb file using struts-1.1. The JVM process (jre-1.2.4_02, Linux, SuSe-8.1) got much larger and a couple of hours later tomcat didn't react to the most of the events. What can be the reason? Additionally I found strange the tomcat didn't create the localhost_log... files since the last startup. Here I are the data provided by top: SIZE: 175M RSS: 165M SHARE: 38980 STAT: S N %CPU: 0.0% %MEM: 33.3 TIME 0:05 The machine has 512Mb. Zsolt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat hanging!! About to change container!! Please help!!
David Rees wrote: On Fri, October 3, 2003 at 1:02 pm, Remy Maucherat sent the following Interesting stuff about the logger. Anyway, in the dump, there's, as usual, only one connector listening on its server socket. And, as usual, it is Sun JDK 1.4.1 or 1.4.2 on Linux. I think there are way too many coincidences in these reports. I wonder what's the market share is today on Linux, but I don't even remember the last time I heard about stability issues with the IBM JDK. It's also interesting that it seems that a number of these reports are coming from Redhat 9 machines. I would confirm that the machine is running all the latest errata updates from Redhat (especially the glibc updates which have a number of thread fixes) and at the same time also upgrade to the latest 1.4.2 JDK from Sun (build 1.4.2_01-b06) if he doesn't want to try the latest from IBM. RH 9 had NGPT, and I read that most Sun VMs weren't supported under it, and the latest JDK 1.4.x was needed (whatever it is). I also read that IBM 1.4.1 was ok (although I think only 1.4.0 is available :-D). So, basically, I'm confused :) Indeed, I have noticed that these bugs with the connector all occurred on Linux 2.4 (usually, people don't mention the distro they are using, only the kernel version) + Sun JDK 1.4.1 or 1.4.2. If there's a clear confirmation of this, a recommendation not to use Sun JDKs on Linux would be added in the release notes. -- x Rémy Maucherat Senior Developer Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat hanging!! About to change container!! Please help!!
On Sun, October 5, 2003 1at 2:44 am, Remy Maucherat sent the following If there's a clear confirmation of this, a recommendation not to use Sun JDKs on Linux would be added in the release notes. I can't say I agree with this as I have about half a dozen machines running Tomcat on a Linux 2.4 kernel along with various Sun JDKs, and I have never experienced a JVM hang in the past year. However, none of these machines are running anything later than RedHat 7.3, a few are running Debian. All are running various almost vanilla 2.4 kernels since the 2.4.14 release. All now are running 2.4.20 or higher. If anything, instead of recommending to stay away from Linux and Sun JDK combos, I would simply add it as a comment or FAQ until there is hard documented evidence of a specific combination which causes problems. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat hanging!! About to change container!! Please help!!
David Rees wrote: On Sun, October 5, 2003 1at 2:44 am, Remy Maucherat sent the following If there's a clear confirmation of this, a recommendation not to use Sun JDKs on Linux would be added in the release notes. I can't say I agree with this as I have about half a dozen machines running Tomcat on a Linux 2.4 kernel along with various Sun JDKs, and I have never experienced a JVM hang in the past year. However, none of these machines are running anything later than RedHat 7.3, a few are running Debian. All are running various almost vanilla 2.4 kernels since the 2.4.14 release. All now are running 2.4.20 or higher. If anything, instead of recommending to stay away from Linux and Sun JDK combos, I would simply add it as a comment or FAQ until there is hard documented evidence of a specific combination which causes problems. Yes, not much is known right now, and nothing will be documented until there's a decent proof on which configurations are a problem. I think it will only occur with the standlone HTTP/1.1 connector (JK stresses the thread pool, and more importantly the network stack of the JVM a lot less). Also, there are hints it can be linked to the recent Redhats (ie, not 7.3). Feel free to add useful comments to this :) (the symptoms are the connector stopping to function after about 1 day, regardless of the server load level - a stack dump will reveal all the threads are idle waiting at the right spot, but no thread listening on the server socket) -- x Rémy Maucherat Senior Developer Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat hanging!! About to change container!! Please help!!
On Fri, October 3, 2003 at 1:02 pm, Remy Maucherat sent the following Interesting stuff about the logger. Anyway, in the dump, there's, as usual, only one connector listening on its server socket. And, as usual, it is Sun JDK 1.4.1 or 1.4.2 on Linux. I think there are way too many coincidences in these reports. I wonder what's the market share is today on Linux, but I don't even remember the last time I heard about stability issues with the IBM JDK. It's also interesting that it seems that a number of these reports are coming from Redhat 9 machines. I would confirm that the machine is running all the latest errata updates from Redhat (especially the glibc updates which have a number of thread fixes) and at the same time also upgrade to the latest 1.4.2 JDK from Sun (build 1.4.2_01-b06) if he doesn't want to try the latest from IBM. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat hanging!! About to change container!! Please help!!
Thanks for the suggestions. I made all of the changes except for using a text realm. Here are 2 thread traces. One is for a quiet server. The other is after the server sat overnight. I did a wget and the server hung. I immediately did a kill -QUIT. Looks like there is a hang in the Logging?! Could it have to do with rotating the log for a new day? I will now do a test removing the security realm. -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Thursday, October 02, 2003 10:52 AM To: Tomcat Users List Subject: RE: Tomcat hanging!! About to change container!! Please help!! Howdy, say 10-12 hours of browser inactivity, when attempting to login we get the BASIC Auth prompt, we enter our credentials and then tomcat hangs while loading our index.jsp. The request never completes. I've attached our configuration. Please let me know if there is anything that looks wrong. We,re using: Tomcat 4.1.27 Java 1.4.2 Redhat 9.0 Also, what kind of settings can I apply to help debug the problem effectively. Add debug=99 to your JDBC Realm, as well as your Host and Context definition server.xml. Make sure you DB is up and available, and that your connections are not stale. If you're using connection pooling, add validation queries so that the pool can check and recycle connections as needed. Does the lockup happen if you use a simple user authentication with tomcat-users.xml as opposed to your more complex JDBC realm? That's worth trying in order to isolate the problem. Does this behavior happen on other machines, e.g. the dev machines, or only this heavily loaded production one? BTW a constant 50% CPU load is heavy -- what's it doing out of curiosity? Yoav Shapira 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 hanging!! About to change container!! Please help!!
Howdy, Attachments don't come through the list server... Yoav Shapira Millennium ChemInformatics -Original Message- From: Joe Zendle [mailto:[EMAIL PROTECTED] Sent: Friday, October 03, 2003 1:03 PM To: Tomcat Users List Subject: RE: Tomcat hanging!! About to change container!! Please help!! Thanks for the suggestions. I made all of the changes except for using a text realm. Here are 2 thread traces. One is for a quiet server. The other is after the server sat overnight. I did a wget and the server hung. I immediately did a kill -QUIT. Looks like there is a hang in the Logging?! Could it have to do with rotating the log for a new day? I will now do a test removing the security realm. -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Thursday, October 02, 2003 10:52 AM To: Tomcat Users List Subject: RE: Tomcat hanging!! About to change container!! Please help!! Howdy, say 10-12 hours of browser inactivity, when attempting to login we get the BASIC Auth prompt, we enter our credentials and then tomcat hangs while loading our index.jsp. The request never completes. I've attached our configuration. Please let me know if there is anything that looks wrong. We,re using: Tomcat 4.1.27 Java 1.4.2 Redhat 9.0 Also, what kind of settings can I apply to help debug the problem effectively. Add debug=99 to your JDBC Realm, as well as your Host and Context definition server.xml. Make sure you DB is up and available, and that your connections are not stale. If you're using connection pooling, add validation queries so that the pool can check and recycle connections as needed. Does the lockup happen if you use a simple user authentication with tomcat-users.xml as opposed to your more complex JDBC realm? That's worth trying in order to isolate the problem. Does this behavior happen on other machines, e.g. the dev machines, or only this heavily loaded production one? BTW a constant 50% CPU load is heavy -- what's it doing out of curiosity? Yoav Shapira 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] 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 hanging!! About to change container!! Please help!!
(ManagerBase.java:66 4) - locked 0x45071620 (a java.util.HashMap) at org.apache.catalina.session.StandardManager.processExpires(StandardManag er.java:779) at org.apache.catalina.session.StandardManager.run(StandardManager.java:870 ) at java.lang.Thread.run(Thread.java:534) StandardManager[] daemon prio=1 tid=0x08099b00 nid=0x223b waiting on condition [4de86000..4de86714] at java.util.HashMap.newValueIterator(HashMap.java:833) at java.util.HashMap$Values.iterator(HashMap.java:896) at java.util.AbstractCollection.toArray(AbstractCollection.java:172) at org.apache.catalina.session.ManagerBase.findSessions(ManagerBase.java:66 4) - locked 0x44e89a70 (a java.util.HashMap) at org.apache.catalina.session.StandardManager.processExpires(StandardManag er.java:779) at org.apache.catalina.session.StandardManager.run(StandardManager.java:870 ) at java.lang.Thread.run(Thread.java:534) Signal Dispatcher daemon prio=1 tid=0x080a58e0 nid=0x223b waiting on condition [0..0] Finalizer daemon prio=1 tid=0x08090ca0 nid=0x223b in Object.wait() [4c9f4000..4c9f4714] at java.lang.Object.wait(Native Method) - waiting on 0x44cf8780 (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:111) - locked 0x44cf8780 (a java.lang.ref.ReferenceQueue$Lock) at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:127) at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:159) Reference Handler daemon prio=1 tid=0x08090030 nid=0x223b in Object.wait() [4c973000..4c973714] at java.lang.Object.wait(Native Method) - waiting on 0x44cf87e8 (a java.lang.ref.Reference$Lock) at java.lang.Object.wait(Object.java:429) at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:115) - locked 0x44cf87e8 (a java.lang.ref.Reference$Lock) main prio=1 tid=0x08052468 nid=0x223b runnable [bfffb000..bfffbfb8] at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:353) - locked 0x45217810 (a java.net.PlainSocketImpl) at java.net.ServerSocket.implAccept(ServerSocket.java:448) at java.net.ServerSocket.accept(ServerSocket.java:419) at org.apache.catalina.core.StandardServer.await(StandardServer.java:527) at org.apache.catalina.startup.Catalina.start(Catalina.java:521) 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) VM Thread prio=1 tid=0x0808eda0 nid=0x223b runnable VM Periodic Task Thread prio=1 tid=0x080a80e8 nid=0x223b waiting on condition Suspend Checker Thread prio=1 tid=0x080a4f10 nid=0x223b runnable -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Friday, October 03, 2003 11:37 AM To: Tomcat Users List Subject: RE: Tomcat hanging!! About to change container!! Please help!! Howdy, Attachments don't come through the list server... Yoav Shapira Millennium ChemInformatics -Original Message- From: Joe Zendle [mailto:[EMAIL PROTECTED] Sent: Friday, October 03, 2003 1:03 PM To: Tomcat Users List Subject: RE: Tomcat hanging!! About to change container!! Please help!! Thanks for the suggestions. I made all of the changes except for using a text realm. Here are 2 thread traces. One is for a quiet server. The other is after the server sat overnight. I did a wget and the server hung. I immediately did a kill -QUIT. Looks like there is a hang in the Logging?! Could it have to do with rotating the log for a new day? I will now do a test removing the security realm. -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Thursday, October 02, 2003 10:52 AM To: Tomcat Users List Subject: RE: Tomcat hanging!! About to change container!! Please help!! Howdy, say 10-12 hours of browser inactivity, when attempting to login we get the BASIC Auth prompt, we enter our credentials and then tomcat hangs while loading our index.jsp. The request never completes. I've attached our configuration. Please let me know if there is anything that looks wrong. We,re using: Tomcat 4.1.27 Java 1.4.2 Redhat 9.0 Also, what kind of settings can I apply to help debug the problem effectively. Add debug=99 to your JDBC Realm, as well as your Host and Context definition server.xml. Make sure you DB is up and available, and that your connections are not stale. If you're using connection
RE: Tomcat hanging!! About to change container!! Please help!!
Howdy, Oh, interesting... Thread-2 daemon prio=1 tid=0x084201a0 nid=0x223b waiting on condition [4e08..4e080714] at java.io.PrintWriter.print(PrintWriter.java:375) at java.io.PrintWriter.println(PrintWriter.java:515) - locked 0x44a33ae0 (a java.io.FileWriter) at org.apache.catalina.logger.FileLogger.log(FileLogger.java:293) I saw the above and the StandardHost thread stuck on PrintWriter.print. I wonder if that's OK. Maybe there's a problem with rotating the log files? Or disk space? Or file descriptors (ulimit on unix)? I would still try it without the JDBC Realm. Yoav Shapira Millennium ChemInformatics -Original Message- From: Joe Zendle [mailto:[EMAIL PROTECTED] Sent: Friday, October 03, 2003 1:53 PM To: Tomcat Users List Subject: RE: Tomcat hanging!! About to change container!! Please help!! Sorry, here are the thread traces -- Happy Server: -- Full thread dump Java HotSpot(TM) Client VM (1.4.2-b28 mixed mode): MonitorRunnable daemon prio=1 tid=0x0872d0d8 nid=0x223b in Object.wait() [4e684000..4e684714] at java.lang.Object.wait(Native Method) - waiting on 0x4524c590 (a org.apache.tomcat.util.threads.ThreadPool$MonitorRunnable) at org.apache.tomcat.util.threads.ThreadPool$MonitorRunnable.run(ThreadPoo l .java:503) - locked 0x4524c590 (a org.apache.tomcat.util.threads.ThreadPool$MonitorRunnable) at java.lang.Thread.run(Thread.java:534) Thread-10 daemon prio=1 tid=0x0872c490 nid=0x223b runnable [4e603000..4e603714] at java.net.PlainSocketImpl.socketAccept(Native Method) at java.net.PlainSocketImpl.accept(PlainSocketImpl.java:353) - locked 0x4524c610 (a java.net.PlainSocketImpl) at java.net.ServerSocket.implAccept(ServerSocket.java:448) at java.net.ServerSocket.accept(ServerSocket.java:419) at org.apache.jk.common.ChannelSocket.accept(ChannelSocket.java:268) at org.apache.jk.common.ChannelSocket.acceptConnections(ChannelSocket.java : 531) at org.apache.jk.common.SocketAcceptor.runIt(ChannelSocket.java:660) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPoo l .java:619) at java.lang.Thread.run(Thread.java:534) Thread-9 daemon prio=1 tid=0x08732188 nid=0x223b in Object.wait() [4e582000..4e582714] at java.lang.Object.wait(Native Method) - waiting on 0x4524c808 (a org.apache.tomcat.util.threads.ThreadPool$ControlRunnable) at java.lang.Object.wait(Object.java:429) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPoo l .java:595) - locked 0x4524c808 (a org.apache.tomcat.util.threads.ThreadPool$ControlRunnable) at java.lang.Thread.run(Thread.java:534) Thread-8 daemon prio=1 tid=0x0872da18 nid=0x223b in Object.wait() [4e501000..4e501714] at java.lang.Object.wait(Native Method) - waiting on 0x4524c880 (a org.apache.tomcat.util.threads.ThreadPool$ControlRunnable) at java.lang.Object.wait(Object.java:429) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPoo l .java:595) - locked 0x4524c880 (a org.apache.tomcat.util.threads.ThreadPool$ControlRunnable) at java.lang.Thread.run(Thread.java:534) Thread-7 daemon prio=1 tid=0x0872d7c0 nid=0x223b in Object.wait() [4e48..4e480714] at java.lang.Object.wait(Native Method) - waiting on 0x4524c8f8 (a org.apache.tomcat.util.threads.ThreadPool$ControlRunnable) at java.lang.Object.wait(Object.java:429) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPoo l .java:595) - locked 0x4524c8f8 (a org.apache.tomcat.util.threads.ThreadPool$ControlRunnable) at java.lang.Thread.run(Thread.java:534) MonitorRunnable daemon prio=1 tid=0x0872b440 nid=0x223b in Object.wait() [4e284000..4e284714] at java.lang.Object.wait(Native Method) - waiting on 0x4523c638 (a org.apache.tomcat.util.threads.ThreadPool$MonitorRunnable) at org.apache.tomcat.util.threads.ThreadPool$MonitorRunnable.run(ThreadPoo l .java:503) - locked 0x4523c638 (a org.apache.tomcat.util.threads.ThreadPool$MonitorRunnable) at java.lang.Thread.run(Thread.java:534) Thread-5 daemon prio=1 tid=0x0841fd88 nid=0x223b in Object.wait() [4e203000..4e203714] at java.lang.Object.wait(Native Method) - waiting on 0x4523c6b8 (a org.apache.tomcat.util.threads.ThreadPool$ControlRunnable) at java.lang.Object.wait(Object.java:429) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPoo l .java:595) - locked 0x4523c6b8 (a org.apache.tomcat.util.threads.ThreadPool$ControlRunnable) at java.lang.Thread.run(Thread.java:534) Thread-4 daemon prio=1 tid=0x0841f1d0 nid=0x223b in Object.wait() [4e182000..4e182714] at java.lang.Object.wait(Native Method) - waiting on 0x4523c730 (a org.apache.tomcat.util.threads.ThreadPool$ControlRunnable
Re: Tomcat hanging!! About to change container!! Please help!!
Shapira, Yoav wrote: Howdy, Oh, interesting... Thread-2 daemon prio=1 tid=0x084201a0 nid=0x223b waiting on condition [4e08..4e080714] at java.io.PrintWriter.print(PrintWriter.java:375) at java.io.PrintWriter.println(PrintWriter.java:515) - locked 0x44a33ae0 (a java.io.FileWriter) at org.apache.catalina.logger.FileLogger.log(FileLogger.java:293) I saw the above and the StandardHost thread stuck on PrintWriter.print. I wonder if that's OK. Maybe there's a problem with rotating the log files? Or disk space? Or file descriptors (ulimit on unix)? I would still try it without the JDBC Realm. Interesting stuff about the logger. Anyway, in the dump, there's, as usual, only one connector listening on its server socket. And, as usual, it is Sun JDK 1.4.1 or 1.4.2 on Linux. I think there are way too many coincidences in these reports. I wonder what's the market share is today on Linux, but I don't even remember the last time I heard about stability issues with the IBM JDK. -- x Rémy Maucherat Senior Developer Consultant JBoss Group (Europe) SàRL x - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tomcat hanging!! About to change container!! Please help!!
We have 10 days until we go GA. We are experiencing periodic and regular lockups of Tomcat. We are testing on a machine that is fairly loaded with background work (about 50% cpu). Our web app is accessed by very few users so Tomcat per se, is not under load handling requests. After say 10-12 hours of browser inactivity, when attempting to login we get the BASIC Auth prompt, we enter our credentials and then tomcat hangs while loading our index.jsp. The request never completes. I've attached our configuration. Please let me know if there is anything that looks wrong. We,re using: Tomcat 4.1.27 Java 1.4.2 Redhat 9.0 Also, what kind of settings can I apply to help debug the problem effectively. BTW, I've seen similar complaints on this mailing list but no suggestions :-). Please help! Regards. !-- Example Server Configuration File -- !-- Note that component elements are nested corresponding to their parent-child relationships with each other -- !-- A Server is a singleton element that represents the entire JVM, which may contain one or more Service instances. The Server listens for a shutdown command on the indicated port. Note: A Server is not itself a Container, so you may not define subcomponents such as Valves or Loggers at this level. -- Server port=8005 shutdown=SHUTDOWN debug=0 !-- Uncomment these entries to enable JMX MBeans support -- Listener className=org.apache.catalina.mbeans.ServerLifecycleListener debug=0/ Listener className=org.apache.catalina.mbeans.GlobalResourcesLifecycleListener debug=0/ !-- Global JNDI resources -- GlobalNamingResources !-- Mail Client -- Resource name=mail/Session auth=Container type=javax.mail.Session/ ResourceParams name=mail/Session parameter namemail.smtp.host/name valuelocalhost/value /parameter /ResourceParams Resource name=UserDatabase auth=Container type=org.apache.catalina.UserDatabase description=User database that can be updated and saved /Resource ResourceParams name=UserDatabase parameter namefactory/name valueorg.apache.catalina.users.MemoryUserDatabaseFactory/value /parameter parameter namepathname/name valueconf/tomcat-users.xml/value /parameter /ResourceParams /GlobalNamingResources !-- A Service is a collection of one or more Connectors that share a single Container (and therefore the web applications visible within that Container). Normally, that Container is an Engine, but this is not required. Note: A Service is not itself a Container, so you may not define subcomponents such as Valves or Loggers at this level. -- !-- Define the Tomcat Stand-Alone Service -- Service name=Tomcat-Standalone !-- A Connector represents an endpoint by which requests are received and responses are returned. Each Connector passes requests on to the associated Container (normally an Engine) for processing. By default, a non-SSL HTTP/1.1 Connector is established on port 8080. You can also enable an SSL HTTP/1.1 Connector on port 8443 by following the instructions below and uncommenting the second Connector entry. SSL support requires the following steps (see the SSL Config HOWTO in the Tomcat 4.0 documentation bundle for more detailed instructions): * Download and install JSSE 1.0.2 or later, and put the JAR files into $JAVA_HOME/jre/lib/ext. * Execute: %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows) $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA (Unix) with a password value of changeit for both the certificate and the keystore itself. By default, DNS lookups are enabled when a web application calls request.getRemoteHost(). This can have an adverse impact on performance, so you can disable it by setting the enableLookups attribute to false. When DNS lookups are disabled, request.getRemoteHost() will return the String version of the IP address of the remote client. -- !-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8081 -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8080 minProcessors=5 maxProcessors=75 enableLookups=false acceptCount=100 debug=0 connectionTimeout=2 useURIValidationHack=false disableUploadTimeout=true / !-- Note : To disable connection timeouts, set connectionTimeout value to -1 -- !-- Define a SSL Coyote HTTP/1.1 Connector on port 8443 -- Connector className=org.apache.coyote.tomcat4.CoyoteConnector port=8443 minProcessors=5
RE: Tomcat hanging!! About to change container!! Please help!!
Howdy, say 10-12 hours of browser inactivity, when attempting to login we get the BASIC Auth prompt, we enter our credentials and then tomcat hangs while loading our index.jsp. The request never completes. I've attached our configuration. Please let me know if there is anything that looks wrong. We,re using: Tomcat 4.1.27 Java 1.4.2 Redhat 9.0 Also, what kind of settings can I apply to help debug the problem effectively. Add debug=99 to your JDBC Realm, as well as your Host and Context definition server.xml. Make sure you DB is up and available, and that your connections are not stale. If you're using connection pooling, add validation queries so that the pool can check and recycle connections as needed. Does the lockup happen if you use a simple user authentication with tomcat-users.xml as opposed to your more complex JDBC realm? That's worth trying in order to isolate the problem. Does this behavior happen on other machines, e.g. the dev machines, or only this heavily loaded production one? BTW a constant 50% CPU load is heavy -- what's it doing out of curiosity? Yoav Shapira 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 hanging!! About to change container!! Please help!!
Since I see SSL stuff .. you may want to look at building from HEAD until 4.1.28 comes out. I think there were some connector fixes as well as ssl fixes. I don't know if the fixes were performance related. -Tim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat hanging!! About to change container!! Please help!!
Hi Joe, I'm experiencing a similar problem to what you are describing. What I've now tried to do based on Rémy Maucherat advice is to try the IBM JVM instead of the Sun JVM. I don't have conclusive results yet, but if you are using the Sun JVM, try using the IBM VM. Regards, Noam - Original Message - From: Joe Zendle [EMAIL PROTECTED] To: Tomcat Users List [EMAIL PROTECTED] Sent: Thursday, October 02, 2003 6:44 PM Subject: Tomcat hanging!! About to change container!! Please help!! We have 10 days until we go GA. We are experiencing periodic and regular lockups of Tomcat. We are testing on a machine that is fairly loaded with background work (about 50% cpu). Our web app is accessed by very few users so Tomcat per se, is not under load handling requests. After say 10-12 hours of browser inactivity, when attempting to login we get the BASIC Auth prompt, we enter our credentials and then tomcat hangs while loading our index.jsp. The request never completes. I've attached our configuration. Please let me know if there is anything that looks wrong. We,re using: Tomcat 4.1.27 Java 1.4.2 Redhat 9.0 Also, what kind of settings can I apply to help debug the problem effectively. BTW, I've seen similar complaints on this mailing list but no suggestions :-). Please help! Regards. - 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 hanging!! About to change container!! Please help!!
On Thu, October 2, 2003 at 9:44 am, Joe Zendle sent the following We have 10 days until we go GA. We are experiencing periodic and regular lockups of Tomcat. We are testing on a machine that is fairly loaded with background work (about 50% cpu). Our web app is accessed by very few users so Tomcat per se, is not under load handling requests. After say 10-12 hours of browser inactivity, when attempting to login we get the BASIC Auth prompt, we enter our credentials and then tomcat hangs while loading our index.jsp. The request never completes. I've attached our configuration. Please let me know if there is anything that looks wrong. We,re using: Tomcat 4.1.27 Java 1.4.2 Redhat 9.0 Also, what kind of settings can I apply to help debug the problem effectively. BTW, I've seen similar complaints on this mailing list but no suggestions :-). Please help! Last time I saw similar hangs it was a bug in my application. When you notice that Tomcat hangs, send it a QUIT signal and take a look at the output. You've probably got a thread in an infinite loop somewhere stuck inside of a synchronized section. -Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat hanging!! About to change container!! Please help!!
Joe: Are you sure it is hanging? Have you left it for a very long time to see if it responds? We are experiencing a problem where an occasional request take about 4 minutes to complete, and it is on a login page that only presents a form to input a login and password. I wonder if you are seeing the same thing. Thanks, Neil -- Neil Aggarwal, JAMM Consulting, (972)612-6056, www.JAMMConsulting.com FREE! Valuable info on how your business can reduce operating costs by 17% or more in 6 months or less! = http://newsletter.JAMMConsulting.com Original message from Joe Zendle We have 10 days until we go GA. We are experiencing periodic and regular lockups of Tomcat. We are testing on a machine that is fairly loaded with background work (about 50% cpu). Our web app is accessed by very few users so Tomcat per se, is not under load handling requests. After say 10-12 hours of browser inactivity, when attempting to login we get the BASIC Auth prompt, we enter our credentials and then tomcat hangs while loading our index.jsp. The request never completes. I've attached our configuration. Please let me know if there is anything that looks wrong.=20 We,re using: Tomcat 4.1.27 Java 1.4.2 Redhat 9.0 Also, what kind of settings can I apply to help debug the problem effectively. BTW, I've seen similar complaints on this mailing list but no suggestions :-). Please help! Regards. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat hanging!! About to change container!! Please help!!
Subject: Re: Tomcat hanging!! About to change container!! Please help!! Joe Zendle We have 10 days until we go GA. We are experiencing Joe Zendle periodic and regular lockups of Tomcat. We are testing on Joe Zendle a machine that is fairly loaded with background work Joe Zendle (about 50% cpu). Our web app is accessed by very few users Joe Zendle so Tomcat per se, is not under load handling Joe Zendle requests. After say 10-12 hours of browser inactivity, Joe Zendle when attempting to login we get the BASIC Auth prompt, we Joe Zendle enter our credentials and then tomcat hangs while loading Joe Zendle our index.jsp. The request never completes. Joe Zendle Also, what kind of settings can I apply to help debug the Joe Zendle problem effectively. This may help in debugging. Fixing is another story. During one of your periods of inactivity, send a few SIGQUITs to the jvm (eg - kill -QUIT TOMCAT_PID). In CATALINA_HOME/logs/catalina.out you'll see a series of stack traces (thread dumps). Use these to get an idea of what an idle server looks like. Then, get tomcat to hang. Send a few more SIGQUITs. Look for threads that weren't in your previous listing, but appear after the hang occurred. One of these is probably the culprit. Once you have an idea about where the problem is occurring, figuring out the why may be a little easier. Good luck ... -- Steve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Tomcat hanging!! About to change container!! Please help!!
those are good suggestions, also, can you produce a test case? as soon as you have a test case, the tomcat developers will figure it out until then, it is hard Filip - Original Message - From: [EMAIL PROTECTED] To: 'Tomcat-User' [EMAIL PROTECTED] Sent: Thursday, October 02, 2003 2:06 PM Subject: Re: Tomcat hanging!! About to change container!! Please help!! Subject: Re: Tomcat hanging!! About to change container!! Please help!! Joe Zendle We have 10 days until we go GA. We are experiencing Joe Zendle periodic and regular lockups of Tomcat. We are testing on Joe Zendle a machine that is fairly loaded with background work Joe Zendle (about 50% cpu). Our web app is accessed by very few users Joe Zendle so Tomcat per se, is not under load handling Joe Zendle requests. After say 10-12 hours of browser inactivity, Joe Zendle when attempting to login we get the BASIC Auth prompt, we Joe Zendle enter our credentials and then tomcat hangs while loading Joe Zendle our index.jsp. The request never completes. Joe Zendle Also, what kind of settings can I apply to help debug the Joe Zendle problem effectively. This may help in debugging. Fixing is another story. During one of your periods of inactivity, send a few SIGQUITs to the jvm (eg - kill -QUIT TOMCAT_PID). In CATALINA_HOME/logs/catalina.out you'll see a series of stack traces (thread dumps). Use these to get an idea of what an idle server looks like. Then, get tomcat to hang. Send a few more SIGQUITs. Look for threads that weren't in your previous listing, but appear after the hang occurred. One of these is probably the culprit. Once you have an idea about where the problem is occurring, figuring out the why may be a little easier. Good luck ... -- Steve - 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]
Tomcat hanging on Solaris 2.9
Alright having several extremely frustrating issues right now. The first is tomcat 4.1.18 is hanging on Solaris 2.9. I have not seen anything logged so I really don't have a clue as to why. It will run perfectly for minutes to hours and then just hang. Any ideas on what the test or where to look for a clue would be appreciated. I attempted to update to .24 and now I receive a new error that I included below, along with continuing to hang. Any hints on either one of these issues would be great. Sorry again about the vagueness of the first but I can't even seem to find a specific action that is causing it...I am lost. Mar 31, 2003 12:12:48 PM org.apache.tomcat.util.net.PoolTcpEndpoint closeServerSocket SEVERE: Caught exception trying to unlock accept. java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:295) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:161) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:148) at java.net.Socket.connect(Socket.java:425) at java.net.Socket.connect(Socket.java:375) at java.net.Socket.init(Socket.java:290) at java.net.Socket.init(Socket.java:118) at org.apache.tomcat.util.net.PoolTcpEndpoint.closeServerSocket(PoolTcpEndpoint .java:326) at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint.java :397) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:529) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:619) at java.lang.Thread.run(Thread.java:536) Mar 31, 2003 12:12:48 PM org.apache.tomcat.util.net.PoolTcpEndpoint closeServerSocket SEVERE: Caught exception trying to close socket. java.lang.NullPointerException at org.apache.tomcat.util.net.PoolTcpEndpoint.closeServerSocket(PoolTcpEndpoint .java:338) at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint.java :397) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:529) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav a:619) at java.lang.Thread.run(Thread.java:536) Mar 31, 2003 12:12:48 PM org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket WARNING: Reinitializing ServerSocket Mar 31, 2003 12:13:00 PM org.apache.commons.modeler.Registry loadRegistry INFO: Loading registry information Mar 31, 2003 12:13:00 PM org.apache.commons.modeler.Registry getRegistry INFO: Creating new Registry instance Mar 31, 2003 12:13:01 PM org.apache.commons.modeler.Registry getServer INFO: Creating MBeanServer Mar 31, 2003 12:13:02 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 Starting service Tomcat-Standalone Apache Tomcat/4.1.24 Mar 31, 2003 12:13:08 PM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Mar 31, 2003 12:13:09 PM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on /0.0.0.0:8009 Mar 31, 2003 12:13:09 PM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=1/56 config=/usr/local/jakarta-tomcat-4.1.24/conf/jk 2.properties Stopping service Tomcat-Standalone Mar 31, 2003 12:16:54 PM org.apache.commons.modeler.Registry loadRegistry INFO: Loading registry information Mar 31, 2003 12:16:54 PM org.apache.commons.modeler.Registry getRegistry INFO: Creating new Registry instance Mar 31, 2003 12:16:55 PM org.apache.commons.modeler.Registry getServer INFO: Creating MBeanServer Mar 31, 2003 12:16:55 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 Starting service Tomcat-Standalone Apache Tomcat/4.1.24 Mar 31, 2003 12:17:02 PM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Mar 31, 2003 12:17:02 PM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on /0.0.0.0:8009 Mar 31, 2003 12:17:02 PM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=2/124 config=/usr/local/jakarta-tomcat-4.1.24/conf/j k2.properties Steve Gums - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Tomcat hanging on Solaris 2.9
Howdy, Does it ever lock up running standalone, or only with JK? Yoav Shapira Millennium ChemInformatics -Original Message- From: Steve Gums [mailto:[EMAIL PROTECTED] Sent: Monday, March 31, 2003 2:37 PM To: Tcat Users Subject: Tomcat hanging on Solaris 2.9 Alright having several extremely frustrating issues right now. The first is tomcat 4.1.18 is hanging on Solaris 2.9. I have not seen anything logged so I really don't have a clue as to why. It will run perfectly for minutes to hours and then just hang. Any ideas on what the test or where to look for a clue would be appreciated. I attempted to update to .24 and now I receive a new error that I included below, along with continuing to hang. Any hints on either one of these issues would be great. Sorry again about the vagueness of the first but I can't even seem to find a specific action that is causing it...I am lost. Mar 31, 2003 12:12:48 PM org.apache.tomcat.util.net.PoolTcpEndpoint closeServerSocket SEVERE: Caught exception trying to unlock accept. java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:295) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:161) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:148) at java.net.Socket.connect(Socket.java:425) at java.net.Socket.connect(Socket.java:375) at java.net.Socket.init(Socket.java:290) at java.net.Socket.init(Socket.java:118) at org.apache.tomcat.util.net.PoolTcpEndpoint.closeServerSocket(PoolTcpEnd poin t .java:326) at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint .jav a :397) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:5 29) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPoo l.ja v a:619) at java.lang.Thread.run(Thread.java:536) Mar 31, 2003 12:12:48 PM org.apache.tomcat.util.net.PoolTcpEndpoint closeServerSocket SEVERE: Caught exception trying to close socket. java.lang.NullPointerException at org.apache.tomcat.util.net.PoolTcpEndpoint.closeServerSocket(PoolTcpEnd poin t .java:338) at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint .jav a :397) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:5 29) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPoo l.ja v a:619) at java.lang.Thread.run(Thread.java:536) Mar 31, 2003 12:12:48 PM org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket WARNING: Reinitializing ServerSocket Mar 31, 2003 12:13:00 PM org.apache.commons.modeler.Registry loadRegistry INFO: Loading registry information Mar 31, 2003 12:13:00 PM org.apache.commons.modeler.Registry getRegistry INFO: Creating new Registry instance Mar 31, 2003 12:13:01 PM org.apache.commons.modeler.Registry getServer INFO: Creating MBeanServer Mar 31, 2003 12:13:02 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 Starting service Tomcat-Standalone Apache Tomcat/4.1.24 Mar 31, 2003 12:13:08 PM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Mar 31, 2003 12:13:09 PM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on /0.0.0.0:8009 Mar 31, 2003 12:13:09 PM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=1/56 config=/usr/local/jakarta-tomcat-4.1.24/conf/jk 2.properties Stopping service Tomcat-Standalone Mar 31, 2003 12:16:54 PM org.apache.commons.modeler.Registry loadRegistry INFO: Loading registry information Mar 31, 2003 12:16:54 PM org.apache.commons.modeler.Registry getRegistry INFO: Creating new Registry instance Mar 31, 2003 12:16:55 PM org.apache.commons.modeler.Registry getServer INFO: Creating MBeanServer Mar 31, 2003 12:16:55 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 Starting service Tomcat-Standalone Apache Tomcat/4.1.24 Mar 31, 2003 12:17:02 PM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Mar 31, 2003 12:17:02 PM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on /0.0.0.0:8009 Mar 31, 2003 12:17:02 PM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=2/124 config=/usr/local/jakarta-tomcat-4.1.24/conf/j k2.properties Steve Gums - 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
RE: Tomcat hanging on Solaris 2.9
Standalone, I haven't installed JK yet, but plan to as soon as I can resolve this. I am connecting to a mysql with almost all servlets/JSP pages and mysql doesn't appear to be the issue. It remains fully operational and very fast. -Original Message- From: Shapira, Yoav [mailto:[EMAIL PROTECTED] Sent: Monday, March 31, 2003 1:08 PM To: Tomcat Users List Subject: RE: Tomcat hanging on Solaris 2.9 Howdy, Does it ever lock up running standalone, or only with JK? Yoav Shapira Millennium ChemInformatics -Original Message- From: Steve Gums [mailto:[EMAIL PROTECTED] Sent: Monday, March 31, 2003 2:37 PM To: Tcat Users Subject: Tomcat hanging on Solaris 2.9 Alright having several extremely frustrating issues right now. The first is tomcat 4.1.18 is hanging on Solaris 2.9. I have not seen anything logged so I really don't have a clue as to why. It will run perfectly for minutes to hours and then just hang. Any ideas on what the test or where to look for a clue would be appreciated. I attempted to update to .24 and now I receive a new error that I included below, along with continuing to hang. Any hints on either one of these issues would be great. Sorry again about the vagueness of the first but I can't even seem to find a specific action that is causing it...I am lost. Mar 31, 2003 12:12:48 PM org.apache.tomcat.util.net.PoolTcpEndpoint closeServerSocket SEVERE: Caught exception trying to unlock accept. java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:295) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:161) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:148) at java.net.Socket.connect(Socket.java:425) at java.net.Socket.connect(Socket.java:375) at java.net.Socket.init(Socket.java:290) at java.net.Socket.init(Socket.java:118) at org.apache.tomcat.util.net.PoolTcpEndpoint.closeServerSocket(PoolTcpEnd poin t .java:326) at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint .jav a :397) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:5 29) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPoo l.ja v a:619) at java.lang.Thread.run(Thread.java:536) Mar 31, 2003 12:12:48 PM org.apache.tomcat.util.net.PoolTcpEndpoint closeServerSocket SEVERE: Caught exception trying to close socket. java.lang.NullPointerException at org.apache.tomcat.util.net.PoolTcpEndpoint.closeServerSocket(PoolTcpEnd poin t .java:338) at org.apache.tomcat.util.net.PoolTcpEndpoint.acceptSocket(PoolTcpEndpoint .jav a :397) at org.apache.tomcat.util.net.TcpWorkerThread.runIt(PoolTcpEndpoint.java:5 29) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPoo l.ja v a:619) at java.lang.Thread.run(Thread.java:536) Mar 31, 2003 12:12:48 PM org.apache.tomcat.util.net.PoolTcpEndpoint acceptSocket WARNING: Reinitializing ServerSocket Mar 31, 2003 12:13:00 PM org.apache.commons.modeler.Registry loadRegistry INFO: Loading registry information Mar 31, 2003 12:13:00 PM org.apache.commons.modeler.Registry getRegistry INFO: Creating new Registry instance Mar 31, 2003 12:13:01 PM org.apache.commons.modeler.Registry getServer INFO: Creating MBeanServer Mar 31, 2003 12:13:02 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 Starting service Tomcat-Standalone Apache Tomcat/4.1.24 Mar 31, 2003 12:13:08 PM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Mar 31, 2003 12:13:09 PM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on /0.0.0.0:8009 Mar 31, 2003 12:13:09 PM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=1/56 config=/usr/local/jakarta-tomcat-4.1.24/conf/jk 2.properties Stopping service Tomcat-Standalone Mar 31, 2003 12:16:54 PM org.apache.commons.modeler.Registry loadRegistry INFO: Loading registry information Mar 31, 2003 12:16:54 PM org.apache.commons.modeler.Registry getRegistry INFO: Creating new Registry instance Mar 31, 2003 12:16:55 PM org.apache.commons.modeler.Registry getServer INFO: Creating MBeanServer Mar 31, 2003 12:16:55 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on port 8080 Starting service Tomcat-Standalone Apache Tomcat/4.1.24 Mar 31, 2003 12:17:02 PM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on port 8080 Mar 31, 2003 12:17:02 PM org.apache.jk.common.ChannelSocket init INFO: JK2: ajp13 listening on /0.0.0.0:8009 Mar 31, 2003 12:17:02 PM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=2/124 config=/usr/local/jakarta-tomcat-4.1.24/conf/j k2.properties Steve Gums - To unsubscribe, e
Re: Tomcat Hanging
Do a thread dump on the hanging process. Its CTRL-BREAK on a windows machine, I'm not sure of the Solaris equivalent command. It will likely show a few objects waiting indefinitely for some resource. In my experience it has always been my own code that trips up tomcat. Dave - Original Message - From: Jeremy P [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, October 01, 2001 12:42 PM Subject: Tomcat Hanging Hi all, I am having some trouble with a fleet of production tomcat servers. The servers are running Tomcat 3.2.3 in a fairly high-volume system (approx. 500,000 requests per day) on Solaris 8 using JDK1.3.1 . After starting the servers. They run fantastically for about 20 minutes, with no signs of being slow due to load or any other problems. After this 20 minutes, they hang completely. Running top on the machines shows that they drop off the CPU list completely. Running netstat shows that all connections are stuck in the ESTABLISHED state. Sometimes it takes longer than 20 minutes, sometimes less, but eventually it will hang in the described state. This problem occurs both when running tomcat in standalone operation and via the Apache module. I have seen a few bug reports describing similiar problems but they all say they were fixed prior to 3.2.3. Furthermore, I have even switched one of the machines to Tomcat 4 to see if that would fix the problem, but it did not. Has anyone encountered similiar problems, or have any suggestions as to what may be the cause. Thanks Jeremy __ Do You Yahoo!? Listen to your Yahoo! Mail messages from any phone. http://phone.yahoo.com
IOException and Tomcat hanging
Hi, I've got random java.sql.SQLException: Io exception: Socket closed error in my web application, which uses Tomcat 3.2.2 and struts. It happens only when a link is clicked without the page fully loaded. I don't get any exception while the page is fully loaded. The exception caught in the application is : SQLExcpetion: Io Exceptoin: socket closed The exception at tomcat console is : ContextManager: SocketException reading request, ignored - java.net.SocketException: Connection reset by peer Did someone have similar case before ? Thanks. Xiaoyu attached: Error message in tomcat console: ContextManager: SocketException reading request, ignored - java.net.SocketException: Connection reset by peer at java.net.PlainSocketImpl.socketAvailable(Native Method) at java.net.PlainSocketImpl.available(PlainSocketImpl.java:451) at java.net.SocketInputStream.available(SocketInputStream.java:137) at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:217) at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501) at java.lang.Thread.run(Thread.java:484) Error message our application caught: com.cisco.tte.rims.model.DatabaseErrorException: java.sql.SQLException: Io exception: Socket closed at com.cisco.tte.rims.model.Workspace.getAttributeById(Workspace.java:2809) at com.cisco.tte.rims.actions.ViewWorkspaceConfigAction.handleAction(ViewWorkspaceConfigAction.java:174) at com.cisco.tte.rims.actions.BaseAction.perform(BaseAction.java:174) at org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.java:1726) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1536) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:491) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:405) at org.apache.tomcat.core.Handler.service(Handler.java:287) at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372) at org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:797) at org.apache.tomcat.core.ContextManager.service(ContextManager.java:743) at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:213) at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501) at java.lang.Thread.run(Thread.java:484)
RE: IOException and Tomcat hanging
are you using the JDBCRealm? Filip ~Namaste - I bow to the divine in you~Filip HanikSoftware Architect[EMAIL PROTECTED]www.filip.net -Original Message-From: Xiaoyu Zhang [mailto:[EMAIL PROTECTED]]Sent: Monday, July 02, 2001 10:16 AMTo: [EMAIL PROTECTED]Subject: IOException and Tomcat hanging Hi,I've got random java.sql.SQLException: Io exception: Socket closed error in my web application, which uses Tomcat 3.2.2 and struts. It happens only when a link is clicked without the page fully loaded. I don't get any exception while the page is fully loaded.The exception caught in the application is : SQLExcpetion: Io Exceptoin: socket closedThe exception at tomcat console is : ContextManager: SocketException reading request, ignored - java.net.SocketException: Connection reset by peerDid someone have similar case before ?Thanks. Xiaoyuattached:Error message in tomcat console:ContextManager: SocketException reading request, ignored - java.net.SocketException: Connection reset by peer at java.net.PlainSocketImpl.socketAvailable(Native Method) at java.net.PlainSocketImpl.available(PlainSocketImpl.java:451) at java.net.SocketInputStream.available(SocketInputStream.java:137) at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:217) at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501) at java.lang.Thread.run(Thread.java:484)Error message our application caught:com.cisco.tte.rims.model.DatabaseErrorException: java.sql.SQLException: Io exception: Socket closed at com.cisco.tte.rims.model.Workspace.getAttributeById(Workspace.java:2809) at com.cisco.tte.rims.actions.ViewWorkspaceConfigAction.handleAction(ViewWorkspaceConfigAction.java:174) at com.cisco.tte.rims.actions.BaseAction.perform(BaseAction.java:174) at org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.java:1726) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1536) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:491) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:405) at org.apache.tomcat.core.Handler.service(Handler.java:287) at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372) at org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:797) at org.apache.tomcat.core.ContextManager.service(ContextManager.java:743) at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpConnectionHandler.java:213) at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501) at java.lang.Thread.run(Thread.java:484)
RE: IOException and Tomcat hanging
I've got random java.sql.SQLException: Io exception: Socket closed error in my web application, which uses Tomcat 3.2.2 and struts. It happens only when a link is clicked without the page fully loaded. I don't get any exception while the page is fully loaded. That exception tells you that,... the user clicked on another link, before the page was completely loaded. Really. The page couldn't be delivered because a new page was selected. What you do with that exception is up to you. In most cases, though, you probably want to ignore it, and let it percolate back up to the servlet engine. After all, there's no one asking for the page anymore--what would you do with the output? If you're using the servlet call to do something unrelated to page generation (e.g., to start a service or pre-load data), you may want to move that work off to a separate thread, so it doesn't get interrupted by I/O failures. -- Bill K. -Original Message- From: Xiaoyu Zhang [mailto:[EMAIL PROTECTED]] Sent: Monday, July 02, 2001 10:16 AM To: [EMAIL PROTECTED] Subject: IOException and Tomcat hanging Hi, I've got random java.sql.SQLException: Io exception: Socket closed error in my web application, which uses Tomcat 3.2.2 and struts. It happens only when a link is clicked without the page fully loaded. I don't get any exception while the page is fully loaded. The exception caught in the application is : SQLExcpetion: Io Exceptoin: socket closed The exception at tomcat console is : ContextManager: SocketException reading request, ignored - java.net.SocketException: Connection reset by peer Did someone have similar case before ? Thanks. Xiaoyu attached: Error message in tomcat console: ContextManager: SocketException reading request, ignored - java.net.SocketException: Connection reset by peer at java.net.PlainSocketImpl.socketAvailable(Native Method) at java.net.PlainSocketImpl.available(PlainSocketImpl.java:451) at java.net.SocketInputStream.available(SocketInputStream.java:137) at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC onnectionHandler.java:217) at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501) at java.lang.Thread.run(Thread.java:484) Error message our application caught: com.cisco.tte.rims.model.DatabaseErrorException: java.sql.SQLException: Io exception: Socket closed at com.cisco.tte.rims.model.Workspace.getAttributeById(Workspace.java:2809) at com.cisco.tte.rims.actions.ViewWorkspaceConfigAction.handleAction(ViewWorksp aceConfigAction.java:174) at com.cisco.tte.rims.actions.BaseAction.perform(BaseAction.java:174) at org.apache.struts.action.ActionServlet.processActionPerform(ActionServlet.ja va:1726) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1536) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:491) at javax.servlet.http.HttpServlet.service(HttpServlet.java:740) at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) at org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:405) at org.apache.tomcat.core.Handler.service(Handler.java:287) at org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372) at org.apache.tomcat.core.ContextManager.internalService(ContextManager.java:79 7) at org.apache.tomcat.core.ContextManager.service(ContextManager.java:743) at org.apache.tomcat.service.http.HttpConnectionHandler.processConnection(HttpC onnectionHandler.java:213) at org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416) at org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501) at java.lang.Thread.run(Thread.java:484)
Tomcat hanging
Hi, I have some problems with tomcat. Sometimes when I am using tomcat, and a some other users, tomcat hangs. Very strange. Some jsp pages are oke after the crash, but some not, I don't know when en why it crashes. But when it crashes, it are always the same pages that are oke and not oke. When I want to request a page (bad page) after the crash, it is searching for the page, but he doesn't let see the page to me. When I reboot tomcat, everythins is oke. The time between rebooting and crashing is different, sometimes after 1 hour but sometimes after 6 hours. I use a lot of heavy jsp pages, such as a upload servlet, big search results pages. I am using tomcat 3.2.1, interbase 6.0, interclient 2.0, windows2000. It seems that it is a internal tomcat error, does anybody know what's the problem and how I can solve it? Grtz Pieter
Re: Tomcat hanging
Are you using mod_jk with tomcat 3.2.1 ?, it is a bug...it is fixed in 3.2.2... Guido. - Original Message - From: Heijns, P.J.B. [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, May 30, 2001 2:58 AM Subject: Tomcat hanging Hi, I have some problems with tomcat. Sometimes when I am using tomcat, and a some other users, tomcat hangs. Very strange. Some jsp pages are oke after the crash, but some not, I don't know when en why it crashes. But when it crashes, it are always the same pages that are oke and not oke. When I want to request a page (bad page) after the crash, it is searching for the page, but he doesn't let see the page to me. When I reboot tomcat, everythins is oke. The time between rebooting and crashing is different, sometimes after 1 hour but sometimes after 6 hours. I use a lot of heavy jsp pages, such as a upload servlet, big search results pages. I am using tomcat 3.2.1, interbase 6.0, interclient 2.0, windows2000. It seems that it is a internal tomcat error, does anybody know what's the problem and how I can solve it? Grtz Pieter
RE: Tomcat hanging
I think that I am not using mod_jk, I have never installed it. I only use tomcat as a standalone webserver. Do you know if my problem is solved in tomcat 3.2.2.? Thanks Pieter -Original Message- From: Guido Medina [mailto:[EMAIL PROTECTED]] Sent: woensdag 30 mei 2001 9:01 To: [EMAIL PROTECTED] Subject: Re: Tomcat hanging Are you using mod_jk with tomcat 3.2.1 ?, it is a bug...it is fixed in 3.2.2... Guido. - Original Message - From: Heijns, P.J.B. [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, May 30, 2001 2:58 AM Subject: Tomcat hanging Hi, I have some problems with tomcat. Sometimes when I am using tomcat, and a some other users, tomcat hangs. Very strange. Some jsp pages are oke after the crash, but some not, I don't know when en why it crashes. But when it crashes, it are always the same pages that are oke and not oke. When I want to request a page (bad page) after the crash, it is searching for the page, but he doesn't let see the page to me. When I reboot tomcat, everythins is oke. The time between rebooting and crashing is different, sometimes after 1 hour but sometimes after 6 hours. I use a lot of heavy jsp pages, such as a upload servlet, big search results pages. I am using tomcat 3.2.1, interbase 6.0, interclient 2.0, windows2000. It seems that it is a internal tomcat error, does anybody know what's the problem and how I can solve it? Grtz Pieter
Re: Tomcat hanging
A lot of bugs are solved in 3.2.2 and the migration is very easy, of course, don't overwrite the files without read a litle bit but you almost can may do it... You can also put running apache web server in windows, is ten times faster than IIS and is very fast for static page, use the bridge mod_jk to comunicate one with other...try it, you will like it, I did on a Windows 98 machine for my Freelance jobs... Guido. - Original Message - From: Heijns, P.J.B. [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, May 30, 2001 3:09 AM Subject: RE: Tomcat hanging I think that I am not using mod_jk, I have never installed it. I only use tomcat as a standalone webserver. Do you know if my problem is solved in tomcat 3.2.2.? Thanks Pieter -Original Message- From: Guido Medina [mailto:[EMAIL PROTECTED]] Sent: woensdag 30 mei 2001 9:01 To: [EMAIL PROTECTED] Subject: Re: Tomcat hanging Are you using mod_jk with tomcat 3.2.1 ?, it is a bug...it is fixed in 3.2.2... Guido. - Original Message - From: Heijns, P.J.B. [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, May 30, 2001 2:58 AM Subject: Tomcat hanging Hi, I have some problems with tomcat. Sometimes when I am using tomcat, and a some other users, tomcat hangs. Very strange. Some jsp pages are oke after the crash, but some not, I don't know when en why it crashes. But when it crashes, it are always the same pages that are oke and not oke. When I want to request a page (bad page) after the crash, it is searching for the page, but he doesn't let see the page to me. When I reboot tomcat, everythins is oke. The time between rebooting and crashing is different, sometimes after 1 hour but sometimes after 6 hours. I use a lot of heavy jsp pages, such as a upload servlet, big search results pages. I am using tomcat 3.2.1, interbase 6.0, interclient 2.0, windows2000. It seems that it is a internal tomcat error, does anybody know what's the problem and how I can solve it? Grtz Pieter
Tomcat hanging
Hi, I have some problems with tomcat. Sometimes when I am using tomcat, and a some other users, tomcat hangs. Very strange. Some jsp pages are oke after the crash, but some not, I don't know when en why it crashes. But when it crashes, it are always the same pages that are oke and not oke. When I want to request a page (bad page) after the crash, it is searching for the page, but he doesn't let see the page to me (the browser says website found waiting for reply). When I reboot tomcat, everythins is oke. The time between rebooting and crashing is different, sometimes after 1 hour but sometimes after 6 hours. I use a lot of heavy jsp pages, such as a upload servlet, big search results pages. I am using tomcat 3.2.2, interbase 6.0, interclient 2.0, windows2000. It seems that it is a internal tomcat error, does anybody know what's the problem and how I can solve it? Grtz Pieter
Re: Tomcat hanging
Are you using Java 1.3? If so, downgrade to the last 1.2.2.5 (or the latest 1.2). Java 1.3 has some very serious, and unfortunately very intermittent thread problems. Chris Original Message On 5/30/01, 6:12:27 AM, Heijns, P.J.B. [EMAIL PROTECTED] wrote regarding Tomcat hanging: Hi, I have some problems with tomcat. Sometimes when I am using tomcat, and a some other users, tomcat hangs. Very strange. Some jsp pages are oke after the crash, but some not, I don't know when en why it crashes. But when it crashes, it are always the same pages that are oke and not oke. When I want to request a page (bad page) after the crash, it is searching for the page, but he doesn't let see the page to me (the browser says website found waiting for reply). When I reboot tomcat, everythins is oke. The time between rebooting and crashing is different, sometimes after 1 hour but sometimes after 6 hours. I use a lot of heavy jsp pages, such as a upload servlet, big search results pages. I am using tomcat 3.2.2, interbase 6.0, interclient 2.0, windows2000. It seems that it is a internal tomcat error, does anybody know what's the problem and how I can solve it? Grtz Pieter
RE: Tomcat hanging
i've started using java 1.3.1 a week ago and all thread releated problems known fron 1.3.0 seem to have disappeared michael -Original Message- From: Chris Janicki [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 30, 2001 3:39 PM To: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Tomcat hanging Are you using Java 1.3? If so, downgrade to the last 1.2.2.5 (or the latest 1.2). Java 1.3 has some very serious, and unfortunately very intermittent thread problems. Chris
