[EP-tech] IRStats and EPrints 3.3

Timothy Miles-Board tmb at ecs.soton.ac.uk
Tue Dec 4 13:35:49 GMT 2012


I have found a bug with IRStats 1.x when used with EPrints 3.3.x

There is a memory cycle in the DatabaseInterface object which means that 
those objects are never destroyed, and hence the object's database 
connection is held open indefinitely (until it times out). If enough 
IRStats requests are made in a short space of time this could use up all 
the available MySQL connections.

This small patch fixes the issue:

Note this only applies to IRStats 1.x running under EPrints 3.3.x



Timothy Miles-Board
EPrints Services
School of Electronics and Computer Science
University of Southampton, UK
+44 (0)23 8059 3980     tmb at ecs.soton.ac.uk
Consultancy - Training - Hosting

More information about the Eprints-tech mailing list