Just a point of clarification. Even if you do run it as a service, the same errors you would have seen at the command line are in the logs--not the CF logs, but rather the [jrun]/logs (or in a standalone deployment of CF, it would be the [cf]/runtime/logs), where you will find files like cfusion-out.log (or in standalone, coldfusion-out.log.) Many do miss those logs and they're very valuable. Granted, it's still on you to think to look at them even if you know they exist! :-) And that's just not as easy as them popping up in the command line, but as Dave showed that's possible too. Still, the info is indeed there even when run as a service.
Hope that's helpful. /charlie -----Original Message----- From: Ed Zwart [mailto:[EMAIL PROTECTED] Sent: Monday, June 16, 2008 3:42 PM To: JRun-Talk Subject: Re: Google Web Toolkit and JRUN I'm sure JRUN/CF can be started from the command line! I should have said "_Being forced_ to start Jetty from the command line...". Feedback about failure when starting a Windows service would still be useful though. Although, that's probably an issue for Windows and not JRUN. Anyway, thanks for the heads up! e. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;203748912;27390454;j Archive: http://www.houseoffusion.com/groups/JRun-Talk/message.cfm/messageid:5839 Subscription: http://www.houseoffusion.com/groups/JRun-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.8
