There was a problem. It was starting the WO services before the networking had fully initialized, IIRC. Cliff Tuel posted some wait logic for one of the scripts, but I don't recall what or where or where to find it now. Ah, right. Google. Here:
didn't 10.4 have an issue with starting wo / apache in the wrong order ?
try stopping webserver, then stop wo, then start webserver, then start wo. or the other way round, it's been a while since i played with a 10.4 server :-)
simon
On 8 June 2010 19:42, <email@hidden> wrote:
Hi,
When I reboot a 10.4.11 server, wotaskd and monitor? start, but wotaskd can't start my webapp. The symptoms are it seems like it is trying to start, and womonitor shows that it is trying. The app's log file showed it loaded once, and then the log ends. Of course, it does not start, and I have to restart wotaskd, then I can start the app.
Now I noticed the plist for womonitor did not have the key Disabled set to <false/>, but womonitor always seemed to be running. ( I fixed the womonitor plist.)
From what Mr. Google showed me, I may need to have a -WOHost parameter. I have 2 ethernet ports; en0, which is not configured, and en1, which is configured. Maybe it tries on en0?
Also, the /System/Library/WebObjects/Adaptors/Apache/apache.conf may need to be changed, as per the below info. If /System/Library/WebObjects/Adaptors/Apache/apache.conf is set at the factory default of "localhost" and one has 2 ip interfaces, how does it know which ip address to use?
There is also the option of setting a /Library/WebObjects/Configuration/WOConfig.xml file with the application name, port, host, etc. That may help.
Does anybody have any experience in this?
Thanks in advance.
Google showed me the following:
1/ Update the Adaptor configuration file located in :
/System/Library/WebObjects/Adaptors/Apache/apache.conf
by changing the WebObjectsConfig line from http://localhost:1085 to
http://1.2.3.4:1085 using the real IP of the computer
This problem was detected by logging the WOAdaptor comportement. To
start the log do :
sudo touch /tmp/logWebObjects
after that it's possible to look at the WebObjects.log in /tmp/
2/ In System/Library/LaunchDaemons/ on :
com.apple.womonitor.plist and com.apple.wotaskd.plist
I have added a new Parameter -WOHost=1.2.3.4 using the same IP than
in the apache.conf file
3/ when I created my host in JavaMonitor I've done it with the same
IP than above
4/ When I created an Application I've added the -WOHost=1.2.3.4 in
the "Additional Arguments" textarea for the "New Instance Defaults"
for the Application
--
email@hidden
_______________________________________________
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
_______________________________________________
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
Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.