Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "Middleware issues and solutions"

From EGIWiki
Jump to navigation Jump to search
Line 19: Line 19:
|}
|}


= CREAM =
...
= VOMS =
= VOMS =
== VOMS server fails with high number of VOs ==
== VOMS server fails with high number of VOs ==
Line 39: Line 41:
GGUS ticket  
GGUS ticket  
[https://ggus.eu/tech/ticket_show.php?ticket=72136 #72136]
[https://ggus.eu/tech/ticket_show.php?ticket=72136 #72136]
= WMS =

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

CREAM

...

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

WMS