Re: permission trouble with WO 5.3 on Mac OS 10.5
Re: permission trouble with WO 5.3 on Mac OS 10.5
- Subject: Re: permission trouble with WO 5.3 on Mac OS 10.5
- From: Zak Burke <email@hidden>
- Date: Tue, 29 Jan 2008 16:14:57 -0500
On Jan 29, 2008, at 2:18 PM, Chuck Hill wrote:
On Jan 29, 2008, at 7:59 AM, Zak Burke wrote:
Following Mike's list of how to get the WO 5.3 frameworks running
under Mac OS 10.5,
http://lists.apple.com/archives/Webobjects-dev/2007/Oct/
msg00357.html,
I'm having some permissions errors that I can't unravel.
When I include the appserver/appserverusr keys in the wotaskd and
womonitor plists, those applications start and I can access the
monitor through my browser. Trying to start a deployed application,
however, fails. When I switch the user key to root, I can start my
deployed applications, but they only work in direct-connect mode.
I turned on adaptor debugging and saw the adaptor was trying to
cache info in /Library/WebObjects/Configuration/SiteConfig.xml, a
file owned by root, so I chowned that to appserver:appserverusr,
but that didn't help.
That user / group also needs execute permission on all of those
directories.
Aha. The problem is solved! The problem was two-fold:
Part One:
The default ant task in the new project wizard doesn't grant group
read/execute on the application script:
$pwd
/Users/zburke/workspace/ReallySimple/dist/ReallySimple.woa
$ ls -al
total 72
drwxr-xr-x 6 zburke zburke 204 Jan 28 20:18 .
drwxr-xr-x 3 zburke zburke 102 Jan 23 15:14 ..
drwxr-xr-x 8 zburke zburke 272 Jan 28 20:18 Contents
-rwxr-x--- 1 zburke zburke 11053 Jan 23 15:14 ReallySimple
-rw-r--r-- 1 zburke zburke 16246 Jan 28 20:18 ReallySimple.cmd
-rw-r--r-- 1 zburke zburke 6493 Jan 23 15:14 WOBootstrap.jar
Perhaps that's the right thing to do from a security point of view. I
have a shell script that explicitly sets permissions when I deploy to
production, but since I was just testing a local build, I wasn't
running that script. I don't recall having this trouble on previous
projects, but that was WO 5.3, Mac OS 10.4 and a different build.xml
file, so, uh, a few things have changed.
At any rate, if I chmod +rx ...dist/ReallySimple.woa/ReallySimple,
JavaMonitor, running as appserver:appserverusr starts the application.
Part Two:
Tweaking the permissions allows my app to start, but not to actually
work. Accessing the app via DirectConnect works, but going through
Apache I get:
The requested application was not found on this server.
I restarted Apache on a whim, just to see what would show up in the
adaptor log, and, well, nothing showed up in the adapter log. Well, I
thought, does that mean my app is working? And sure enough, it does.
I'm not sure why kicking Apache after changing permissions on a file
managed by JavaMonitor changes the behavior, but that seems to be the
case.
It could just be that, in the time it took me to kick Apache,
JavaMonitor and wotaskd got themselves squared away and the Apache
restart is a red herring. Dunno, but I can access my app through the
web server so I ain't complaining.
Thanks, as usual, to Chuck and Art for pointing me in the right
direction.
zak.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden