It was the old WOHost parameter, with a twist. I originally set up my Host in javamonitor to be the actual IP of the server. That worked fine until this specific reboot of the system, at which point I couldn't start my app.

I then tried adding:

WOHost=<ip address>

to /System/Library/WebObjects/JavaApplications/wotaskd.woa/Contents/ Resources/Properties and that didn't work. Actually the app would then start, but I couldn't reach the app from the outside (no instance available error I think)

Then I tried just changing to:

WOHost=localhost

Keeping my Host set to its IP. Again, the app would start, but I couldn't get to it from the outside.

Finally, I set both WOHost and the Host in Javamonitor to localhost, and it all started working again.

Phew!

Jeff

On Mar 17, 2009, at 2:22 AM, Jeff Schmitz wrote:

I've got the same symptoms after a reboot, but permissions look ok on app and logs:

LOG File Dir
drwxrwxr-x  91 _appserver  _appserveradm  3094 Mar 17 01:57 Logs

Log File
-rw-r--r-- 1 _appserver _appserveradm 147577 Mar 17 01:08 netBrackets-2

App Files (I brute forced them to make sure):
drwxrwxrwx  8 root  _appserveradm    272 Mar 16 22:49 Contents
-rwxrwxrwx  1 root  _appserveradm   6305 Mar 16 22:49 WOBootstrap.jar
-rwxrwxrwx  1 root  _appserveradm  11053 Mar 16 22:49 netBrackets
-rwxrwxrwx  1 root  _appserveradm  16246 Mar 16 22:49 netBrackets.cmd

Java monitor shows the instances, but it doesn't start the app. No log output. No Deaths. WOStats button is greyed out. HELP!

I was able to launch from the command line as root and it runs fine.

Jeff


On Jan 26, 2009, at 3:15 PM, Chuck Hill wrote:


On Jan 23, 2009, at 8:36 AM, David Peter Shaykewich wrote:

Thanks Chuck!

That seems to have done the trick (and I got some sleep last night). We gave everything in the app permissions of 'o+x', 'o +w', and 'o+r' and suddenly the green light in JavaMonitor was on.

Now that we've opened everything up to the world, is there a resource out there that defines which files need which permissions on the server?

Probably not.  :-)  This is worth reading: 
http://developer.apple.com/documentation/WebObjects/Deployment/Deploying_Applications/Introduction/chapter_1_section_1.html

At one point, WOLips was not marking the script that starts the app as executable. That might have been it. It was the .woa directory that you changed permissions on? It needs to be readable by the user that wotaskd is running as. This should be _appserver if things are setup correctly. _appserver also needs execute permission on the AppName.woa/AppName script.


Chuck




-----Original Message-----
From: Chuck Hill [mailto:ch...@global-village.net]
Sent: Thursday, January 22, 2009 3:02 PM
To: David Peter Shaykewich
Cc: webobjects-deploy@lists.apple.com
Subject: Re: Can't Launch in JavaMonitor


On Jan 22, 2009, at 2:52 PM, David Peter Shaykewich wrote:

Hi Folks.

Summary:
        I can't start an instance of an app (migrated from XCode) built in
WOLips with JavaMonitor, but I can run it from the command line
(MyApp.woa/MyApp).

Dev Env:
        OSX 10.5.6
        Eclipse 3.3.2
        WOLips 3.3.5596
        using the 'woswitch.sh' script to build as WO 5.3

Server:
        OSX 10.4.x
        WO 5.3
        Apache

- Trying to launch an instance of the application on the server
through JavaMonitor fails - the light never turns green and the
Deaths increment up.
- The app runs successfully on the server when started at the
command line (MyApp.woa/MyApp).
- The server is currently successfully hosting a version of this app
(that can be launched using JavaMonitor) that was built using the
old Apple dev tools (XCode?) on 5.3.
- When I launch my WOLips version of the app from the command line
(without any switches), it runs in DirectConnect mode - this is
successful.
- The 'old' XCode version app on the server (that is launched with
JavaMonitor) is NOT running in direct connect mode (images, CSS,
etc. are being served via Apache).

Any ideas about what I can to
        1) diagnose the problem?
        2) fix the problem?

Let's start here:
http://www.gvcsitemaker.com/gvc.webobjects/faq&mode=single&recordID=19193&nextMode=list

Chuck


Thanks very much folks!  I've been banging my head against the wall
on this one!

DS


--
David Shaykewich
Senior Web Application Developer
UVic Online
University of Victoria
dshay...@uvic.ca
voice: 250.853.3233



--
Chuck Hill             Senior Consultant / VP Development

Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects







No virus found in this incoming message.
Checked by AVG - http://www.avg.com
Version: 8.0.176 / Virus Database: 270.10.8/1897 - Release Date: 1/22/2009 7:08 AM


--
Chuck Hill             Senior Consultant / VP Development

Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
http://www.global-village.net/products/practical_webobjects






_______________________________________________
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/jeffandmonica%40mac.com

This email sent to jeffandmon...@mac.com

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-deploy mailing list (Webobjects- dep...@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-deploy/jeffandmonica%40mac.com

This email sent to jeffandmon...@mac.com

_______________________________________________
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 arch...@mail-archive.com

Reply via email to