Apache max AJP connections over IDP 3.4.4

Miguel Salinas Vivancos msalinas at bcn.sia.es
Tue Nov 5 08:52:30 EST 2019

Thank you Scott, I thought that was one of the causes: one of the components behind the Apache was closing some of the transactions.
So, if that's the case, the Apache threads would be in TIME_WAIT or CLOSE_WAIT and therefore, until some threads will be released, no other requests will be pass to the IDP, am I wrong?

Thank you

Miguel Salinas Vivancos
Identity Management Integrator 
Tel.: +34 639 198 154 - mail:msalinas at bcn.sia.es

Grupo SIA
Citypark, Edificio Atenas, Ctra. Hospitalet 147. 08940 Cornellá de Llobregat - Barcelona
www.sia.es  - Twitter: @SIA_es  - LinkedIn: Grupo SIA

-----Mensaje original-----
De: users [mailto:users-bounces at shibboleth.net] En nombre de Cantor, Scott
Enviado el: martes, 5 de noviembre de 2019 14:43
Para: Shib Users
Asunto: Re: Apache max AJP connections over IDP 3.4.4

On 11/5/19, 4:12 AM, "users on behalf of Miguel Salinas Vivancos" <users-bounces at shibboleth.net on behalf of msalinas at bcn.sia.es> wrote:

> We believe that somehow, apache is unable to process all the request so they are not getting to Shibboleth.

There's no chance 500 a minute would be a challenge for a vanilla Apache without other problems (or the IdP itself), but back-ends failing to keep up and finish requests promptly would backlog requests and tie up threads.

-- Scott

For Consortium Member technical support, see https://wiki.shibboleth.net/confluence/x/coFAAg
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net

More information about the users mailing list