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]
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]
