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
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 -05
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.ca
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 applic
t; 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 appli
liche 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 loade
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 Bon
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 Shapir
ed 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 symbo
ilto:[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!
>
: 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
t;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 second
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 co
13 matches
Mail list logo
