This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
After years of running JRun 3.0 with no problem, we upgraded to JRun 3.1, also updated to JDK 1.3.1 at the same time. This is on a NT 4.0 dual processor system with IIS as the web server. Both the Admin server and the default server start and appear to run ok. I am able to use the Admin manager functions and run servlets on the default server. However, after a variable amount of time (5 min to 45 min) the server just stops! No errors are written to logs. This happens with the admin server running by itself or the default by itself. Monitoring system memory use and CPU use has not shown up anything. I would love to hear from any JRun user who has a suggestion as to why this might be happening! Bill
Author and all-around good cowpoke
Joined: Mar 22, 2000
It looks like this problem was due to something I should have recognized! Java 1.3 has a notorious problem when running as a service under NT and Win2000. When the user who started the service exits the system, the JVM dies without saying anything. The fix is to use a command line parameter -Xrs that tells the JVM to ignore the fact that the user left. user.javaargs=-Xrs Bill