Hi Stipe, Scenario: set up an smsbox doing an http GET to (1) a gwlib based application that takes a non-zero time to respond (max-messages > 0), or alternatively (2) issues its own http call to cgi-bin/sendsms (max-messages = 0). The application uses http api functions from the gwlib to listen for MOs coming from the smsbox. The main point to patching would be to prevent the PANIC / crash which comes in 2 flavors - either 'attempting to destroy locked mutex' or the OS (SuSE 8.2, 9.0, 9.1) complains about the open file limit (1024). In the (1) case, the smsbox also exhibits some strange behavior and won't dispatch to the application anymore after a while. Even more so than the PANICs, this is the feature that ultimately makes the whole setup unusable for production, since the process (smsbox) doesn't quite crash, it just stops forwarding traffic.
Ilan On Tuesday 08 March 2005 00:51, Stipe Tolj wrote: > Ilan Aelion wrote: > > Hi all, > > > > I encountered some problems using gwlib httpd features. In particular, > > gwlib will PANIC when the open file limit is exceeded, which is not > > acceptable for many applications. > > can you please point out under which scenarios this is determined? > > > Here's a patch that seems to help. > > > > And here's the question: I've added a few retries with a sleep in between > > in put_port_request in http.c. > > > > * Is there really a point in retrying? > > * Is there really a point in sleeping? > > * would it be better to just skip failed requests immediately without > > retrying? > > retry'ing on the server side? > > what is the scenario of the patch? receiving HTTP clients "before" having > port_collection dict filled with the required keys and hence unable to > serve the request? > > At least this is how I "read" the patch. > > Stipe > > mailto:stolj_{at}_wapme.de > ------------------------------------------------------------------- > Wapme Systems AG > > Vogelsanger Weg 80 > 40470 Düsseldorf, NRW, Germany > > phone: +49.211.74845.0 > fax: +49.211.74845.299 > > mailto:info_{at}_wapme-systems.de > http://www.wapme-systems.de/ > -------------------------------------------------------------------
