On 10-Sep-08, at 7:45 PM, TW wrote:
I have a project that I made minor changes to yesterday. My wo server is working normally and has another app running normally on it. So, there's no dns/hostname issues here. A prior version of the same app was also running on the server so there are already configured instances of this app -- it should just be a matter of replacement.The app runs normally in development mode. The only "big" change I've made is to the nightly build of WOLips with the New Hotness. The problem is when I try to run the app there is no instance output to indicate why it is failing. There is no output to webobjects.err either. WOMonitor just continues acting like it is starting the instance but it never says 'on.' So, my problem is that I don't really know how to diagnose this problem further when there's no info being output anywhere. I'm guessing maybe this is classpath related but I'm not sure where to begin.
Have you tried launching the app from the command line? ;david -- David LeBer Codeferous Software 'co-def-er-ous' adj. Literally 'code-bearing' site: http://codeferous.com blog: http://davidleber.net profile: http://www.linkedin.com/in/davidleber twitter: http://twitter.com/rebeld -- Toronto Area Cocoa / WebObjects developers group: http://tacow.org
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-deploy mailing list (Webobjects-deploy@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-deploy/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
