Re: MacOSX 10.3 Server deployement

If it was only that easy... ;-)

We've got wotaskd madness on Mac OS X Server 10.2.? (current version)  
with WO 5.1.3. Grrr... I've tried next to anything now. Today we've  
just bought an Sun server... but I've got my doubts that it will work  
better there. :-(

Damn! I wanted one of those new Xserve G5s! Too bad.

-Will

On Friday, January 9, 2004, at 01:35 PM, Stephan Fürnrohr wrote:

> Hi, there!
>
> We had similar problems on several new G5 deployment machines. But not  
> only with 10.3, we also had this problems on all Systems with Jaguar  
> and Java  VM 1.4.1 installed.
>
> So - after we saw the possible coherence between 1.4.1 an wotakd's  
> madness (after some bitter hours of investigation ;-)
> I tried to force wotaskd to run with Java VM 1.3.1. This seemed to  
> help! Wotaskd is runnig calm and steady as before....no more open  
> connections, no more "too many open files"....
>
> You can force wotaskd to user Java VM 1.3.1 by changing the first line  
> in the file
> /System/Library/WebObjects/JavaApplications/wotaskd.woa/Contents/ 
> MacOS/MacOSClassPath.txt
> from
> # JVM              == java
> to
> # JVM ==  
> /System/Library/Frameworks/JavaVM.framework/Versions/1.3.1/Commands/ 
> java
>
> Ciao,
> Stephan
>
>
>
> Am 07.01.2004 um 08:44 Uhr schrieb Will Scheidegger:
>
>> You're the greatest! I've been pulling my hair over this for the last  
>> two Months, searching the archives, asking the list, reading the docs  
>> and could not figure out how to resolve this problem. WOTASKD really  
>> _is_ broken. Our deployment is terribly unreliable. We now even began  
>> to play around with two Solaris servers, hoping that this would lead  
>> to a more stable deployment.
>>
>> So same here: Apple, are you listening? We're in the process of  
>> kicking out MacOS X in favor of Solaris! What a shame, especially  
>> since I would be very eager to get my hands on one of those new slick  
>> G5 XServes. Oh well, Apple is busy changing my iLife, no time for  
>> "toys" like WO.
>>
>> -Will
>>
>> On Tuesday, January 6, 2004, at 04:41 PM, Mark Fisher wrote:
>>
>>> Pierre,
>>>
>>> I have the same problems you describe but my hardware environment is  
>>> a bit different.  I run a cluster of XServers:  One  
>>> webserver/application server, One database server and two dedicated  
>>> WebObjects application servers.
>>>
>>> Before the change to 10.3 I had one application distributed to three  
>>> of the servers running over 20 instances on each server.  Now (with  
>>> the upgrade to 10.3) I'm running 10 instances on each server.
>>>
>>> I have been able to trace the problem down to WOTASKD - over time it  
>>> opens too many TCP ports to the running instances and finally gets  
>>> stuck with a "Too many files open" error - check your  
>>> /var/log/webobjects.log for that message.
>>>
>>> I was able to work around the problem by writing a CRON task the  
>>> counts the number of open TCP connections from WOTASKD and restarts  
>>> WOTASKD when the number grows larger than 240 (the crash/hang occurs  
>>> when your reach 255 TCP connections)
>>>
>>> Here is the line I use to identify the open TCP connections (note;  
>>> you will have to adjust your port range if you changed the default  
>>> or you have more instances running than I do):
>>>
>>> 	sudo lsof -i tcp:2001-2050 -P
>>>
>>> Here is the line I use to restart WOTASKD (I had to fix the startup  
>>> script too)
>>>
>>> 	sudo SystemStarter restart 'WebObjects Services'
>>>
>>> I run this script every 10 min in a CRON job:
>>>
>>> #!/bin/sh
>>> #
>>> # Restart WOTASKD when it has too many TCP connections open
>>> #
>>> # by Mark Fisher 11/28/03
>>> # must be run as "root"
>>> #
>>> maxprocs=240
>>> PROCESSLIST=`sudo lsof -i tcp:2001-2050 -P`
>>> i=0
>>> for process in $PROCESSLIST
>>> do
>>> 	i=$((i+i))
>>> done
>>> if [ $i -gt $maxprocs ] ;then
>>> 	echo "Restarting WOTASKD"
>>> 	`SystemStarter restart 'WebObjects Services'`
>>> fi
>>> echo ""
>>> # end shell script
>>>
>>> This solves the problem for now but I really, really wish I knew the  
>>> cause of the problem - Is WOTASKD *really* that broken in 10.3?  I  
>>> wonder how many others out there are having the same trouble getting  
>>> 10.3 Server & WebObjects working reliably.
>>>
>>> If *ANYONE* (Apple are you listening) has any more information on  
>>> this problem I would like to hear from you.
>>>
>>> Thanks in advance,
>>>
>>>
>>> Mark FIsher
>>> Chief Software Engineer,
>>> 	Learning Quest, Inc.
>>>
>
> _______________________________________________
> WebObjects-dev mailing list
> [email protected]
> http://www.omnigroup.com/mailman/listinfo/webobjects-dev