On Jun 25, 2007, at 8:24 AM, Ken Tabb wrote:

Hi folks,

it's been a while since I last deployed a WO app, and I'm having some grief with it. I'm developing using Xcode 2.4.1 / Mac OS X 10.4.10 (although 10.4.9 was doing the same), and deploying on Mac OS X Server 10.4.10 (again no better or worse with MOSXS 10.4.9).

The app's EOModels connect to MySQL locally, and (perhaps importantly) the app doesn't use any WebServerResources - it just sticks in the URLs of things already in the Apache document root (eg. css file, images etc.).

The apache document root is _not_ /Library/WebServer/Documents/ in case that is relevant to the following discussion.

Basically in development mode on my powerbook, it all works fine (either to the local MySQL clone on the powerbook, or to the production database on the web server).

If I build it (from within Xcode) as Deployment, and try to start up instances of that within Monitor, they die.

The same happens if I instead do a
sudo xcodebuild install -configuration Deployment DSTROOT=/
... and copy that, make instances of that etc..

And again the instances still die if I do a
sudo xcodebuild install -configuration WebServer DSTROOT=/
... and copy that (into either <apache's document root>/WebObjects/ or into /Library/WebServer/Documents/WebObjects/)

I'm guessing I shouldn't even need to do the '-configuration WebServer' build if there aren't any actual project specific web server resources, but figured I ought to try to appease the WO Gods, even if it is with empty offerings. There actually isn't a WebServerResources subfolder made within myApp.woa/Contents/, but even if I add an empty 'WebServerResources' here the instances still die.

In Monitor, the URL to Adaptor is set to 'http://www.mydomain.com/ cgi-bin/WebObjects'.

I can't help thinking I'm missing something obvious, but any help would be gratefully appreciated! I've read the WO Deployment Guide from cover to cover (several times!) and also the Monitor help (ditto), but can't see anything suspicious, they just die :(

Thanks in advance,
Ken

- - - - - - - - - -
Dr. Ken Tabb
Mac & UNIX Developer - Health & Human Sciences
Machine Vision & Neural Network researcher - School of Computer Science
University of Hertfordshire, UK


Did you solve your problems with this?

I suspect the crux of the problem is your non-standard apache root. Xcode is not very intelligent about how it handles these things. There are usually variables one can set in the project that get around the issues, but it is sometimes not clear what those options might be.

What was the output when the app crashed? You may have to set the output log directory parameter to get this. The output would help identify the nature of the problem.

- ray

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [EMAIL PROTECTED]

Reply via email to