Hi Tim, thanks for the advise. The interesting part is that tomcat (process) doesn't seem to survive the re-initialization of the ServerSocket. It this a known bug?
Regards, Thomas > -----Ursprüngliche Nachricht----- > Von: Tim Funk [mailto:[EMAIL PROTECTED] > Gesendet am: Dienstag, 15. Juli 2003 13:02 > An: Tomcat Users List > Betreff: Re: Tomcat 4.1.24 + Security Manager + weird Exceptions > > - man ulimit > - Google (java "Too many open files" solaris) > > -Tim > > Haug Thomas wrote: > > Hi everybody, > > > > I am experiencing some strange behaviour with Tomcat 4.1.24 > running with a > > SecurityManager. The system is running on Solaris 8 using > Jdk 1.4.1_02 > > and/or 1.4.2 > > Our software seems to use up all available file > descriptors. If then tomcat > > tries to accept a new request the IO system throws an > SocketException > > telling us that there are too many files open (see > stacktrace below). > > Tomcat seems to reinitialize the ServerSocket but then the > whole Tomcat (or > > the Coyote HTTP connector) 'breaks down': The > securityManager starts to > > throw exceptions that class files are not allowed to be > loaded, Sockets are > > not allowed to be opened (see below), and other strange > things. At last we > > are not able anymore to request any http page from tomcat. > > > > Has anybody experienced a similar behaviour of tomcat. Or > even better does > > anybody know how to fix this problem (beside not using all > file descriptors > > ;-) ) > > > > Thank you very much, > > Thomas > > > > --------------------------------------------------------------------- > 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]
