----------------------------------------------------------------
BEFORE YOU POST, search the faq at <http://java.apache.org/faq/>
WHEN YOU POST, include all relevant version numbers, log files,
and configuration files.  Don't make us guess your problem!!!
----------------------------------------------------------------

Gary Gurevich wrote:
> 
> 
> At 11:01 PM 3/13/00 -0800, you wrote:
> >Shopping my patch around. I've posted to new-httpd and to jserv-dev.
> >This should be enough coverage.
> 
> Cool stuff :)
> 
> >Thanks in advance for any help anyone can render. I'm not sure if the
> >socket
> >issue above
> >is a thread vs process issue, or an NT socket implementation vs Unix
> >socket implementation issue. If you have any questions, please email me
> >at either:
> 
> I think it is a thread/process issue as you suggest. Since each httpd runs
> in its own process space under Unix, a socket "pool" doesn't make sense.
> Each httpd process simply needs to initialize one re-useable socket, since

probably :-)

> each individual process handles only one request at a time. The static
> mod_jserv pool that you create is statically "shared" in a multi-threaded
> app, but not shared at all under Unix. 
will be working (partially) in Apache 2.0

I have no clue what's causing the
> errors exactly, but I'm guessing that the errors you're getting with
> Solaris are a result of having to initialize a new socket for each request
> in turn, resulting in a more obvious manifestation of any "boundary
> conition" problems inherent in the patch. Then once sockets are present in
> the unshared per-process scoreboards, there are no errors. The problem may
> be present under NT, but you would notice it at most once, since after the
> first request has been answered, the socket scoreboard has a socket
> available for all subsequent requests. I think this analysis is consistent
> with the fact that you find errors intermittently towards the beginning of
> your test, but not towards the end of your test (under Solaris).
> 
> But then again, I'm not a certified apache hacker, so I might be completely
> wrong :)
> 
> -Gary

John is right : there is an extra overhead opening & closing a TCP
socket for each hit.
Costin did work on this, so did I, something could happen soon (maybe
experimental only, never released ?).
Anyway, even a single line of code will be granted.

I disagree with the httpd.h hack need btw.

Jean-Luc


--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe:        [EMAIL PROTECTED]
To unsubscribe:      [EMAIL PROTECTED]
Archives and Other:  <http://java.apache.org/main/mail.html>
Problems?:           [EMAIL PROTECTED]

Reply via email to