AW: Long Startup Time
Hi, is your application using some listeners / load-on-startup? Fohrer -Ursprüngliche Nachricht- Von: Mike Cherichetti (Renegade Internet) [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 30. März 2005 22:56 An: Tomcat Users Betreff: Long Startup Time Hi, I'm running Tomcat 5.0.28 with JDK 1.5.0_01 on Fedora Core 3. The problem that I'm having is pretty odd. It's taking Tomcat about 30 minutes to fully start up and start accepting connections. Here's where it's getting hung up at from the startup logs: Mar 30, 2005 10:52:10 AM org.apache.catalina.core.StandardHost start INFO: XML validation disabled Mar 30, 2005 11:21:03 AM org.apache.catalina.core.StandardHost getDeployer You can see that it's about 29 minutes between those two log entries. So, my question is, what is happening there that could take so long? There are no errors in the logs and once Tomcat does complete its startup stuff our application works just fine. Thanks, Mike - 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]
Long Startup Time
Hi, I'm running Tomcat 5.0.28 with JDK 1.5.0_01 on Fedora Core 3. The problem that I'm having is pretty odd. It's taking Tomcat about 30 minutes to fully start up and start accepting connections. Here's where it's getting hung up at from the startup logs: Mar 30, 2005 10:52:10 AM org.apache.catalina.core.StandardHost start INFO: XML validation disabled Mar 30, 2005 11:21:03 AM org.apache.catalina.core.StandardHost getDeployer You can see that it's about 29 minutes between those two log entries. So, my question is, what is happening there that could take so long? There are no errors in the logs and once Tomcat does complete its startup stuff our application works just fine. Thanks, Mike - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Long Startup Time
On what hardware it is running ?. Check for other processes running ?. Any antivirus scanner runnign ?. Check for ContextListeners and Servlets which are set to load on startup. Look at the web.xml to find such things. The bottleneck should be in your application. On Wed, 30 Mar 2005 15:55:39 -0500, Mike Cherichetti (Renegade Internet) [EMAIL PROTECTED] wrote: Hi, I'm running Tomcat 5.0.28 with JDK 1.5.0_01 on Fedora Core 3. The problem that I'm having is pretty odd. It's taking Tomcat about 30 minutes to fully start up and start accepting connections. Here's where it's getting hung up at from the startup logs: Mar 30, 2005 10:52:10 AM org.apache.catalina.core.StandardHost start INFO: XML validation disabled Mar 30, 2005 11:21:03 AM org.apache.catalina.core.StandardHost getDeployer You can see that it's about 29 minutes between those two log entries. So, my question is, what is happening there that could take so long? There are no errors in the logs and once Tomcat does complete its startup stuff our application works just fine. Thanks, Mike - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- rgds Antony Paul http://www.geocities.com/antonypaul24/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: long startup time with JDK1.4
I had the same problem sometime back. The following change worked for me. In the JAVA_HOME\jre\lib\logging.properties, I changed the property .level=ALL To .level=INFO -Original Message- FYI... This didn't work either. In the meantime I figured out, that the time is spent in the PlainSocket.initProt function just before binding to the port, which probably is Java/Linux-Version Problem. I am going to upgrade my linux-Version and hopefully get this fixed -Ursprüngliche Nachricht- Von: David Ramsey [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 20. Jänner 2004 18:02 An: Tomcat Users List Betreff: Re: long startup time with JDK1.4 I would remove your application from Tomcat and observe the startup times with only the shipped example applications loaded. In other words, be sure that Tomcat is at fault here and not your own application. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: long startup time with JDK1.4
FYI... This didn't work either. In the meantime I figured out, that the time is spent in the PlainSocket.initProt function just before binding to the port, which probably is Java/Linux-Version Problem. I am going to upgrade my linux-Version and hopefully get this fixed -Ursprüngliche Nachricht- Von: David Ramsey [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 20. Jänner 2004 18:02 An: Tomcat Users List Betreff: Re: long startup time with JDK1.4 I would remove your application from Tomcat and observe the startup times with only the shipped example applications loaded. In other words, be sure that Tomcat is at fault here and not your own application. __ Do you Yahoo!? Yahoo! Hotjobs: Enter the Signing Bonus Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus - 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: AW: long startup time with JDK1.4
What Linux distribution are you running? And are you running the Sun 1.4 JVM? Oscar On Wed, 21 Jan 2004, Roland Knor wrote: FYI... This didn't work either. In the meantime I figured out, that the time is spent in the PlainSocket.initProt function just before binding to the port, which probably is Java/Linux-Version Problem. I am going to upgrade my linux-Version and hopefully get this fixed -Ursprüngliche Nachricht- Von: David Ramsey [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 20. Jänner 2004 18:02 An: Tomcat Users List Betreff: Re: long startup time with JDK1.4 I would remove your application from Tomcat and observe the startup times with only the shipped example applications loaded. In other words, be sure that Tomcat is at fault here and not your own application. __ Do you Yahoo!? Yahoo! Hotjobs: Enter the Signing Bonus Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: long startup time with JDK1.4
Howdy, Nothing else changed, just the JDK? I.e. no new web applications, listeners, filters, valve, load-on-startup servlets? Yoav Shapira Millennium ChemInformatics -Original Message- From: Roland Knor [mailto:[EMAIL PROTECTED] Sent: Monday, January 19, 2004 9:13 PM To: [EMAIL PROTECTED] Subject: long startup time with JDK1.4 I am Using Tomcat V 3.2.3. I have encountered a strange behaviour of Tomcat when switching from JDK 1.3.1 to 1.4.2. The time until the server is bound to its listening port has increased from a few seconds up to 3 (!!!)minutes. All contexts are added within a second, however after adding the contexts, it seems that the server runs into a kind of timeout before it finally binds to its port (during this 3 minutes the server is idle). The same behaviour has been reached with the latest tomcat-Version (5.0.16). Any Guesses will be appreciated! Thanks in advance for any help! Roland 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]
AW: long startup time with JDK1.4
No, not anything. I just changed the symbolic link to the java-directory (its on a linux system), so that the new JDK is active! Any idea? -Ursprüngliche Nachricht- Von: Shapira, Yoav [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 20. Jänner 2004 14:54 An: Tomcat Users List Betreff: RE: long startup time with JDK1.4 Howdy, Nothing else changed, just the JDK? I.e. no new web applications, listeners, filters, valve, load-on-startup servlets? Yoav Shapira Millennium ChemInformatics -Original Message- From: Roland Knor [mailto:[EMAIL PROTECTED] Sent: Monday, January 19, 2004 9:13 PM To: [EMAIL PROTECTED] Subject: long startup time with JDK1.4 I am Using Tomcat V 3.2.3. I have encountered a strange behaviour of Tomcat when switching from JDK 1.3.1 to 1.4.2. The time until the server is bound to its listening port has increased from a few seconds up to 3 (!!!)minutes. All contexts are added within a second, however after adding the contexts, it seems that the server runs into a kind of timeout before it finally binds to its port (during this 3 minutes the server is idle). The same behaviour has been reached with the latest tomcat-Version (5.0.16). Any Guesses will be appreciated! Thanks in advance for any help! Roland 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: long startup time with JDK1.4
Howdy, Strange ;) I don't have any magic bullet idea ;) Does your app do a lot of XML parsing or manipulation on startup? Does it depend on some jars you added to $JAVA_HOME/jre/ext? Yoav Shapira Millennium ChemInformatics -Original Message- From: Roland Knor [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 20, 2004 9:44 AM To: 'Tomcat Users List' Subject: AW: long startup time with JDK1.4 No, not anything. I just changed the symbolic link to the java-directory (its on a linux system), so that the new JDK is active! Any idea? -Ursprüngliche Nachricht- Von: Shapira, Yoav [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 20. Jänner 2004 14:54 An: Tomcat Users List Betreff: RE: long startup time with JDK1.4 Howdy, Nothing else changed, just the JDK? I.e. no new web applications, listeners, filters, valve, load-on-startup servlets? Yoav Shapira Millennium ChemInformatics -Original Message- From: Roland Knor [mailto:[EMAIL PROTECTED] Sent: Monday, January 19, 2004 9:13 PM To: [EMAIL PROTECTED] Subject: long startup time with JDK1.4 I am Using Tomcat V 3.2.3. I have encountered a strange behaviour of Tomcat when switching from JDK 1.3.1 to 1.4.2. The time until the server is bound to its listening port has increased from a few seconds up to 3 (!!!)minutes. All contexts are added within a second, however after adding the contexts, it seems that the server runs into a kind of timeout before it finally binds to its port (during this 3 minutes the server is idle). The same behaviour has been reached with the latest tomcat-Version (5.0.16). Any Guesses will be appreciated! Thanks in advance for any help! Roland 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] 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: long startup time with JDK1.4
Is tomcat starting with the java -server param? server vm is new to 1.4 (Sun) and has a longer startup time. Shapira, Yoav wrote: Howdy, Strange ;) I don't have any magic bullet idea ;) Does your app do a lot of XML parsing or manipulation on startup? Does it depend on some jars you added to $JAVA_HOME/jre/ext? Yoav Shapira Millennium ChemInformatics -Original Message- From: Roland Knor [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 20, 2004 9:44 AM To: 'Tomcat Users List' Subject: AW: long startup time with JDK1.4 No, not anything. I just changed the symbolic link to the java-directory (its on a linux system), so that the new JDK is active! Any idea? -Ursprüngliche Nachricht- Von: Shapira, Yoav [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 20. Jänner 2004 14:54 An: Tomcat Users List Betreff: RE: long startup time with JDK1.4 Howdy, Nothing else changed, just the JDK? I.e. no new web applications, listeners, filters, valve, load-on-startup servlets? Yoav Shapira Millennium ChemInformatics -Original Message- From: Roland Knor [mailto:[EMAIL PROTECTED] Sent: Monday, January 19, 2004 9:13 PM To: [EMAIL PROTECTED] Subject: long startup time with JDK1.4 I am Using Tomcat V 3.2.3. I have encountered a strange behaviour of Tomcat when switching from JDK 1.3.1 to 1.4.2. The time until the server is bound to its listening port has increased from a few seconds up to 3 (!!!)minutes. All contexts are added within a second, however after adding the contexts, it seems that the server runs into a kind of timeout before it finally binds to its port (during this 3 minutes the server is idle). The same behaviour has been reached with the latest tomcat-Version (5.0.16). Any Guesses will be appreciated! Thanks in advance for any help! Roland 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] 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] -- Daniel Schmitt http://www.shiftomat.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: long startup time with JDK1.4
Howdy, Is tomcat starting with the java -server param? server vm is new to 1.4 (Sun) and has a longer startup time. Server VM is NOT new to JDK 1.4, it was introduced in 1.3. The server VM adds a minute amount of time to startup, not orders of magnitude as observed by Senor Knor. 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: long startup time with JDK1.4
I would remove your application from Tomcat and observe the startup times with only the shipped example applications loaded. In other words, be sure that Tomcat is at fault here and not your own application. __ Do you Yahoo!? Yahoo! Hotjobs: Enter the Signing Bonus Sweepstakes http://hotjobs.sweepstakes.yahoo.com/signingbonus - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
long startup time with JDK1.4
I am Using Tomcat V 3.2.3. I have encountered a strange behaviour of Tomcat when switching from JDK 1.3.1 to 1.4.2. The time until the server is bound to its listening port has increased from a few seconds up to 3 (!!!)minutes. All contexts are added within a second, however after adding the contexts, it seems that the server runs into a kind of timeout before it finally binds to its port (during this 3 minutes the server is idle). The same behaviour has been reached with the latest tomcat-Version (5.0.16). Any Guesses will be appreciated! Thanks in advance for any help! Roland
