× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Interesting. Jeffrey Day also asked about the ThreadsPerChild setting.

I have had a quick check and it seems that on IBMs recommendation (it was something they changed when trying to diagnose matters) they have the following settings:

MaxCGIJobs 100
ThreadsPerChild 100

Prior to that the defaults were in place.


-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Nathan Andelin
Sent: 07 January 2011 16:06
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] Summing up the Icebreak discussion

Kevin,

In the case that I referred to earlier, we set ThreadsPerChild to 3000, and over
a period of time the CGI jobs grow. We use a dispatcher architecture similar to
yours.

-Nathan


----- Original Message ----
From: Kevin Turner <kevin.turner@xxxxxxxxxxxxxxx>
To: Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>
Sent: Fri, January 7, 2011 1:35:16 AM
Subject: Re: [WEB400] Summing up the Icebreak discussion

Hi Nathan

Some installations run with the despatcher (the data queue isolating the CGI
stuff from the Apache thread) and some do not. In this case they do not - the
programs are all running in the thread. They are going to switch to use the
despatcher this month to see if it improves matters.

The odd thing is that it will behave for a week or so and then suddenly start to
issue thread failure messages to the QSYSOPR message queue. Sometimes that just
stops and other times it escalates until the server just crashes completely and
has to be restarted. I am sorry I haven't got the job log messages to hand, but
they are occurring in the bowels of the Apache software somewhere. It all sounds
like some sort of memory leak issue, but we haven't isolated one in the
application yet. IBM were not much help either.

"1-2 thousand CGI server jobs". Wow! No, nothing of that magnitude. They have
max out at just over a 1000 concurrent sessions during the day - about 3-400
call centre agents I guess, each with an average of 2 sessions (some more).
Those sessions are usually served by a 100 or so CGI threads - could be more but
certainly not a 1-2 thousand. That is an enormous number - are they running
persistent CGI?

Cheers
Kevin



--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.


NOTICE: The information in this electronic mail transmission is intended by CoralTree Systems Ltd for the use of the named individuals or entity to which it is directed and may contain information that is privileged or otherwise confidential. If you have received this electronic mail transmission in error, please delete it from your system without copying or forwarding it, and notify the sender of the error by reply email or by telephone, so that the sender's address records can be corrected.



--------------------------------------------------------------------------------


CoralTree Systems Limited
25 Barnes Wallis Road
Segensworth East, Fareham
PO15 5TT

Company Registration Number 5021022.
Registered Office:
12-14 Carlton Place
Southampton, UK
SO15 2EA
VAT Registration Number 834 1020 74.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.