Difference between revisions of "Middleware issues and solutions"
Jump to navigation
Jump to search
Line 15: | Line 15: | ||
| VOMS | | VOMS | ||
| July 17, 2011 | | July 17, 2011 | ||
| [https://wiki.egi.eu/wiki/Middleware_issues_and_solutions#VOMS_server_fails_with_high_number_of_VOs VOMS server fails with high number of VOs | | [https://wiki.egi.eu/wiki/Middleware_issues_and_solutions#VOMS_server_fails_with_high_number_of_VOs VOMS server fails with high number of VOs] | ||
|- | |- | ||
|} | |} |
Revision as of 09:08, 27 September 2011
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
Documentation menu: | Home • | Manuals • | Procedures • | Training • | Other • | Contact ► | For: | VO managers • | Administrators |
Purpose of this page is to document recurring middleware issues with broad impact and the respective solutions and/or workarounds.
This page is maintained by the Distributed Middleware Support Unit of EGI.
Distribution | Affected Product | Date | Title |
EMI | VOMS | July 17, 2011 | VOMS server fails with high number of VOs |
VOMS
VOMS server fails with high number of VOs
VOMS server of gLite 3.2 is more memory greedy, it starts failing when configured to serve more than 10 (approx.) VOs.
Change -XX:MaxPermSize parameter of CATALINA_OPTS to the value of at least 512m in /etc/tomcat5/tomcat5.conf
CATALINA_OPTS="-Xmx1508M -server -Dsun.net.client.defaultReadTimeout=240000 -XX:MaxPermSize=512m"
and add
* soft nofile 2048 * hard nofile 2048
into /etc/security/limits.conf.
GGUS ticket #72136