Ticket #1662 (closed defect: fixed)
Memory-Leaks with TomCat/Oracle/Connection-Pool
|Reported by:||umn-ms@…||Owned by:||unicoletti|
|Component:||Input - Native Oracle Spatial Support||Version:||unspecified|
Description (last modified by dmorissette) (diff)
I made experiences with using Connection-Pooling of Oracle-Connections inside Java/Tomcat. Testenvironment: Mapserver 4.6.2; Suse-Linux; Tomcat 4.1.31; Sun-Java 1.4.2 Simulating 5 Browsers, which produce maps, query features, make selections, query-legend-pics frequently. - Big memory leak: Between the first 5 requests and the next 100 requests the Tomcat-process became about 400MB bigger. (I use "top" for watching memory-footprint.) - Cleaning the Connection-Pool "by hand". This means: Opening the function msConnPoolCloseUnreferenced in mappool.c for use in Java and call it after every request. - After this I still have memory leaks: About 100MB for 30.000 requests. (I also made a test: 25.000 requests without Connection pooling. Memory increased and decreased as expected in this case.) My Post on the list was: http://mapserver.gis.umn.edu/bugs/show_bug.cgi?id=1661 The follow ups in the user-list are containing a small discussion on dealing this issue.
Note: See TracTickets for help on using tickets.