Hi
I just wanted to update this thread with recent experiences. Also, my
customer has asked my to look at this for the next 3 days while I'm
on site to try to solve the issue of Apache returning 503 errors to
the browser. The problem seems to be Apache receiving socket errors
instantaneously back from 4D Client Web server. The measured error
rate is about 0.05 %, however there are occassional reports from
users that they get 503 errors in the browser and the problem is
reproducible.
SCENARIO:
Apache fronted 4D Client 2004 + Active 4D. Running on Windows 2003
Server
4D Server database server
On 13 May 2009, at 10:39, Peter Schumacher wrote:
wouldn't it help to create more web processes "on stock" and keep
them running? Just create 2000 processes and let them run. In the
idle state they don't consume anything.
We tried using SET DATABASE PARAMETER(Client Minimum Web Process) set
to 2000, however this didn't appear to improve the number of socket
errors measurable.
LISTENERS v WEB PROCESSES
I'm not knowledgeable enough about low level TCP comms to understand
this distinction and thereby know what to try. The "processes"
created by the SET DATABASE PARAMETER(Client Minimum Web Process) are
not visible in runtime explorer, whereas the ones creates in reponse
to an actual request are. Does that mean we are actually setting the
number of "listeners" by using this command ?
I remember when using ITK in the old day's, you could actually set
the number of listeners explicitly. It's not clear to me what the
equivalent is in 4D. We've also been thinking of looking at Rob
Laveauxs NTK, in particular the bullet point that says..
"... high performance, non blocking sockets"
If anyone can shed light, particularly on the distinction between
"processes" and "listeners" and socket handling in general, if would
be welcomed.
Regards
Peter
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
