The overseas organisation that contacted me is having a problem with their WO 
app.
It is running on a Dual 500 MHz PPC G4 with 1GB RAM and running Tiger Server 
10.4.11.
The backend DB is under Oracle on a Sun server.

The current problem is that the httpd root task gets into a situation where it 
keeps spawning www tasks. 
It initially starts of with 5 of them. At some point in time there are a 
multitude of them and 
the system slows down to the point of having to be re-booted.

I have now received the source code for the WO app. It turns out to be an Xcode 
project. 
My present environment is Snow Leopard 10.6.7 and Xcode 3.2.6 on an Intel Mac 
Pro (2009 Nehalem 2xQuad Core) etc.

Leopard was last the OS X version where Apple provided WO support. I do have 
Leopard 10.5.8 as a bootable partition.
Also Xcode is installed and I can install whatever WO stuff is needed from the 
dvd. I have also DL'd WO 5.4.3 but not installed it yet.

I also have available a G4 PPC 867MHz machine which I can setup as a web server 
if this is needed.
(It runs Tiger 10.4.11 but not Server version. Server is available to me and I 
can setup a separate partition as a test environment)

Browsing around in the Xcode project I see a folder named GCRI.eomodeld 
containing a lot of .fspec and .plist files.
Then a whole bunch of other folders containing .java source files. 
And a folder named Web Components containing other folders in which are .api, 
.wo, .html, .wod, and .woo files.

Finally there is a single target named GCRI made up of two sub targets named 
Application Server and Web Server

Please advise me as to the best debugging path to follow to diagnose the 
spawning issue.

Thanks for your advice and

respect....

Peter _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to