I have run into this problem too.
When deployed on OS X Server 10.3, I was able to solve the problem by changing the owner of /System/Library/WebObjects/JavaApplications/wotaskd.woa/wotaskd and /System/Library/WebObjects/JavaApplications/wotaskd.woa/Contents/Resources/javawoservice.sh to root instead of appserver. Then, the startup script at /System/Library/StartupItems/WebObjects/WebObjects would run these as root, and the Quicktime Java would work fine.
Under OS X Server 10.4, a different mechanism is used to start WebObjects -- it is turned on and off in Server Admin. Using this method, WebObjects is running as appserver instead of root, even though I changed the owner of the files listed above. I'd like to understand the Server Admin process that starts WebObjects, but I don't.
As a workaround, I've turned off WebObjects in Server Admin and copied /System/Library/StartupItems/WebObjects from an older 10.3 deployment. Now, WebObjects is starting fine and running as root.
On Jun 14, 2005, at 9:23 AM, Alex Johnson wrote: On Jun 11, 2005, at 12:02 PM, Jaime Magiera wrote:
I'm working on a WebObjects application that uses Quicktime Java to edit movie files through the web. On my development machine, calling qtsession.open() works without a problem. However, when I deploy my application on the server, qtsession.open() throws an error in WebObjects. The only thing that I notice as different is that on my development machine, calling qtsession.open() from within WO launches a "bootloader" application. The same used to be true to for my server, but since 10.3, the error appears instead.
This is a bit over my head. Can anyone shed some light on this error or the mechanisms at work? Any thoughts much appreciated.
Don't know if this will answer your questions, but I think the problem is this:
With no one logged into your server, the only running window server is owned by root. Thus, if you're WO app is running as any other user (like appserver, f.x.) it will not have the proper permissions to connect to the window server. It works in dev. because both your wo app and the window server are your processes. You will have to do something similar on the dep box.
HTH
Alex Johnson
|