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]
