Are your King Oracle feature sources using the KingFdoClass metadata table feature for cleaner class names?
If so, a leak was identified and plugged on that front. https://trac.osgeo.org/fdo/changeset/8279 This was leaking on every DescribeSchema request where the connection was configured with the KingFdoClass metadata table. The more rows in that table, the more leaks per request. - Jackie You wrote: Forgot to mention that once the memory starts to be consumed it's a run away event, meaning that it doesn't seem to stop until the services fail and have to be restarted. Thanks, David
_______________________________________________ mapguide-users mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/mapguide-users
