Help! Having issues with Tomcat

[Peter Cuba]

I have a problem debugging my servlet code on the command prompt using Tomcat 4. When the code is executed, which is calling a MS Access database, it crashes the server and the command window immediately closes. I need it to remain open so I can see at what point in the code it crashed. I have added system.println at varios locations throughout the code to see where it is crashing. Is there a way to configure Tomcat to keep the prompt window open after the server crashes? I am using Win98. If anyone can help I would appreciate it.

Peter

[Mike Curwen]

Well, if the command window is closing because of the crash, then no, there is no way to prevent the closing of the window.

It's like asking Win98 to stop giving you a blue screen, so that you can see what went wrong.

The other thing you could do is to inspect the log files that Tomcat generates in the <CATALINA_HOME>/logs directory.

Of particular interest is the localhost_log.your-date-here.txt file... this is where stack traces get blown out.

[Tim Holloway]

Actually, if YOU open the command window and manually start Tomcat, it shouldn't close. Automatic window-closing is normally a result of running a process that also automatically opens the window. There IS a way of setting PIF options to keep the window open.
MS Access isn't really a good DBMS for use with web servers. But then Win/98 isn't a good DBMS for web servers either. I presume/hope that you're using this setup for R&D and not production.