I'm guessing that or something very much like it is the problem. But I don't think I have the courage to try it at this point since it's currently running with localhost. Maybe in about a month, or if it stops working again I'll try it with all WOHosts and setting all to domain names instead of localhost.
I wish there were a canonical, well documented way to set this stuff that worked every time, so I'm going to take a first cut. The list below I think represents some very common deployment "problem child" entries, but I certainly at this time haven't found a magic answer that always works for me for the things in red, with the biggest overall questions being: Use localhost/don't use localhost Use IP Addresses or domain names Use WOHost properties/Don't use WOHost properties Note that if you do use domain names, they must be reverse lookup'able, so that the 'host ip' and 'host domain' commands match up e.g. $host netbrackets1.netbrackets.com netbrackets1.netbrackets.com has address 208.52.168.238 $ host 208.52.168.238 238.168.52.208.in-addr.arpa domain name pointer netbrackets1.netbrackets.com. With that said, here is my first attempt at the canonical list of deployment problem children: /Library/WebObjects/JavaApplications/wotaskd.woa/Contents/Resources/Properties: WOHost=[IP/Domain/localhost/don't use WOHost] /Library/WebObjects/JavaApplications/JavaMonitor/Contents/Resources/Properties: WOHost=[IP/Domain/localhost/don't use WOHost] JavaMonitor Site HTTP Adaptor URL: http://[IP/Domain/localhost]/cgi-bin/WebObjects JavaMonitor Hosts Host name (Status says available so wotaskd daemon is running): [IP/Domain/localhost] /System/Library/WebObjects/Adaptors/Apache2.2/apache.conf: WebObjectsConfig [IP/Domain/localhost]:1085 10 httpd.conf "problem" entries: ServerName [IP/Domain/localhost]:80 DocumentRoot "/Library/WebServer/Documents" <Directory /> Options FollowSymLinks AllowOverride None # Order deny,allow # Deny from all </Directory> ScriptAliasMatch ^/cgi-bin/((?!(?i:webobjects)).*$) "/Library/WebServer/CGI-Executables/$1" Include /System/Library/WebObjects/Adaptors/Apache2.2/apache.conf apache.conf "problem" entries: LoadModule WebObjects_module /System/Library/WebObjects/Adaptors/Apache2.2/mod_WebObjects.so WebObjectsDocumentRoot /Library/WebServer/Documents WebObjectsAlias /cgi-bin/WebObjects WebObjectsConfig [IP/Domain/localhost]:1085 10 Additional Arguments "magic" entry in Javamonitor: .... -WOHost [IP/Domain/localhost/don't use WOHost] On Mar 4, 2014, at 11:30 AM, Chuck Hill <ch...@global-village.net> wrote: > The random results and lack of WOHost settings suggest that the apps are > starting while networking is getting finalized. I’d try adding WOHost to > everything (apps, JavaMonitor, wotaskd). > > Chuck > > > On 2014-03-04, 7:56 AM, "Jeff Schmitz" wrote: > > Definitely random. Every reboot is an adventure :-) > > Here's the host info. I think it looks good. > host netbrackets1.netbrackets.com > netbrackets1.netbrackets.com has address 208.52.168.238 > > host 208.52.168.238 > 238.168.52.208.in-addr.arpa domain name > > I'll have to try starting the app from the command line later but all is > working right now so I'm pretty sure the app itself starts fine. Per the logs > It was actually getting started by javamonitor without error but javamonitor > didn't know it. > > Sent from my iPhone > > On Mar 4, 2014, at 9:01 AM, Aaron Rosenzweig <aa...@chatnbike.com> wrote: > >> Hi Jeff, >> >> I wonder if you are having NSLOOKUP trouble. >> >> If the DNS isn’t just right, WO can get easily confused and probably will >> cause sporadic problems like you are experiencing. >> >> Right? If I understand it correctly things are failing somewhat randomly. >> It’s not like they never work, they sometimes do. That smells of DNS >> trouble. >> >> In particular: >> >> "Check that the machine is properly identified in the DNS including the >> reverse lookup." >> AARON ROSENZWEIG / Chat 'n Bike >> e: aa...@chatnbike.com t: (301) 956-2319 >> >> On Mar 4, 2014, at 4:44 AM, Jeffrey Schmitz <j...@netbrackets.com> wrote: >> >>> JavaMonitor started the instances, and they start fine with no errors. >>> >>> Is there some way I can get this working without javamonitor knowing it's >>> running at least temporarily? The app is up and running according to the >>> log at least. >>> >>> >>> On Mar 4, 2014, at 3:08 AM, Alexander Spohr <a...@freeport.de> wrote: >>> >>>> >>>> Am 04.03.2014 um 09:30 schrieb Jeffrey Schmitz <j...@netbrackets.com>: >>>> >>>>> port = 2003; runningState = "DEAD" >>>> >>>> Who started the instances? >>>> Are they on the right port? >>>> >>> >>> _______________________________________________ >>> 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: >>> https://lists.apple.com/mailman/options/webobjects-dev/aaron%40chatnbike.com >>> >>> This email sent to aa...@chatnbike.com >>
_______________________________________________ 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: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
