We are having trouble understanding what's happening with the CFusion server when we try to stop it. The JRun Admin shows it as being stopped, the Services applet is showing it as being stopped, and the JRun Launcher is showing it as being stopped, however, we can still log into the CF Admin, and the CF enabled Web sites on the server still operate as if CF were running. There are 4 JRun servers running on this sysem, and all have stopped except the admin server. The others are named default, samples, pier, and cfusion. The default, samples, and pier servers normally do not run.
I seem to recall having this same issue in past; needing to stop a JRun server, and having it in fact not stop. We can probably resolve this by rebooting the server-- but want to save that as a last resort, naturally. The reason we need to stop the CFusion server is so we can delete some left over files from the /servers/cfusion/SERVER-INF/temp/ directory. It seems that JRun leaves a lot of garbage behind as we update various parts of the Java app. Why is that-- is that normal for JRun? The system is a single server running Win2003, IIS6, CF6.1 running as a J2EE app on JRun4. Thanks in advance for any advice. -- Best Regards, Ron Connelly [EMAIL PROTECTED] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:10:5409 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/10 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:10 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.10 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
