/usr/sbin/ipconfig waitall is already part of the default startup
script for wotaskd and JavaMonitor but it didn't work on Snow Leopard
for some reason.
Did some more research and seems like using the Network Reachability
Framework API can be used for this and other launchd Daemons.
(http://developer.apple.com/mac/library/documentation/Networking/Conceptual/SystemConfigFrameworks/SC_ReachConnect/SC_ReachConnect.html#/
/apple_ref/doc/uid/TP40001065-CH204-BHAFBAHI)
I wrote a quick Objective C script to determine the reachability of my
local machine. I called this from the startup scripts and it seemed
to work. I'm specifically using kSCNetworkFlagsReachable .
M
On Aug 2, 2010, at 10:00 PM, D Tim Cummings wrote:
We had a similar problem with Tomcat starting before network was
ready. We solved the problem by putting
/usr/sbin/ipconfig waitall
in the tomcat startup script. This might help here, and be a bit
more reliable than just sleeping for 15 seconds.
Tim
On 03/08/2010, at 9:22 AM, Tusker wrote:
Turns out that it was the launchd launch daemon. It was starting
wotaskd and JavaMonitor before setting up the network for the
machine resulting in weird behavior. Adding sleep 15 to the
wotaskd and JavaMonitor init script solved the problem. I'm
looking into a better way of doing this. Tried but that did not
work.
Thanks everyone for your help/suggestions.
M.
On Jul 29, 2010, at 7:42 AM, Chuck Hill wrote:
On Jul 28, 2010, at 9:57 PM, Tusker wrote:
I looked at the SpawnofWotaskd.log further:
Something even more weird further up in the logs
Jul 28 18:04:59 N/A[N/A] (ERXNSLogLog4jBridge.java:43) WARN
NSLog - WOApplication Error: Failed to rename previously
existing WOOutputPath file: /Library/WebObjects/Logs/testpp-1
.....
Jul 28 18:04:59 N/A[N/A] (ERXNSLogLog4jBridge.java:46) DEBUG
NSLog - WOAdaptorURL=http://localhost/cgi-bin/WebObjects
....
Jul 28 18:04:59 N/A[N/A] (ERXNSLogLog4jBridge.java:46) DEBUG
NSLog - com.webobjects.pid = 3140
I set the HTTP Adaptor to my other server in JavaMonitor, not
localhost. Is WOAdaptorURL set correctly above.
I prefer it to have a FQDN for deployment boxes.
Well, that what I did. I entered the FQDN for my server where
the WOAdaptor sits. I did this in JavaMonitor. But WOAdaptorURL
still points to http://localhost/cgi-bin/WebObjects in the logs.
Could this be the problem?
I don't think so. What is this getting set to in the additional
args of the app?
Chuck
--
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-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/tim%40triptera.com.au
This email sent to t...@triptera.com.au
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
