1. 2 minute polling interval is pretty low. I would suggest 5-15 minutes 2. Make sure you have enough file descriptors. 65k is required. If `# ulimit -n` shows 1024 or 4k, it's too low. This is normally the root cause of a proxy error. Having a short refresh interval is probably make the problem worse, as you are generating lots of connections.

Hi Michael, Thanks for the quick response. 1. Should I update FD limit at Machine level or at Gluu Contrainer level or both? command Output of Machine Level & Gluu container level: [root@sso ~]# ulimit -Hn 4096 [root@sso ~]# ulimit -Sn 1024 And, when I vi(i.e., open) the file at 'Machine Level' "vi /etc/security/limits.conf" there is not limit set. However, within 'Gluu Container' when i vi the file, i could see below limits: ldap soft nofile 131072 ldap hard nofile 262144 apache soft nofile 131072 apache hard nofile 262144 jetty soft nofile 131072 jetty hard nofile 262144 2. Output of "cat /proc/sys/fs/file-max" is 383654. is this fine or should i reduce to 65K? 3. In file /etc/pam.d/login I should add "session required pam_limits.so", but not sure whether at Machine level or gluu container level or at both? Also, can you tell me what is the purpose of adding above line? will there be any restriction when i login to machine via SSH? Kindly help me to resolve this. Thanks

Tejesh, Along with ulimit, make sure you have enough memory allocations for `identity`, `oxauth` and `idp`. They are in /etc/defaults/ inside container.

Hi, I have modifed all the settings as above. But still i'm getting proxy error frequently. Kindly help to resolve this issue. Thanks