find . -name '*.java' | xargs grep System.exit OR find . -type f | xargs grep System.exit
-Tim
Tim Funk wrote:
When someone (forget who) suggested looking for System.exit - they meant it might be in *your* code, not the tomcat code.
Here is an easy way to look for System.exit: find . -name '*.java' | grep System.exit OR find . -type f | grep System.exit
-Tim
Paridhi Bansal wrote:
If you could tell me where to look for that System.exit call??I mean in the tomcat scripts???
Paridhi
Try finding a rogue System.exit call :).
On Tue, 16 Sep 2003, Paridhi Bansal wrote:
Hi!!!!
I am using tomcat4.0.6 as a standalone server for my servlet -applet based application.The server initially listens at port 8443(SSL) and after the request, the servlet throws a jar file and opens up port 4004 for applet-servlet communication. However, when this port is openend, telnetting to the server on this open port i.e 4004 (which is actaully not included in tomcat's configuartion file but is hardcoded in the servlet and applet), the tomcat server itself crashes. All the java threads get terminated automatically.I have to restart tomcat to start things working.What can be the cause for this??Is there something to be included in the tomcat configuration??What can be the solution??
Any help will b highly appreciated...
Paridhi
--
--------------------------------------------------------------------- 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]
