Hi,
SimpleFeatureTypes is a singleton object which maintains some
information about the the FeatureTypes being used. It should not be
GCed. I'm unsure why the RegexParsers are hanging around; I'll have
to think about that.
In general, if as long there is not an increase in instances or
sizes of those classes, I don't think there is a reason to be
worried.
Thanks,
Jim
On 03/09/2015 11:53 PM, 焦小超 wrote:
Hi,
When i opended the jvisualvm profile on query client
node and accumulo tablet server node, I found that some
object instance, such as SimpleFeatureTypes and
scala.util.parsing.combinator.RegexParsers, survived all the
time， their tenure continue to rise (PS: I set the JVM param
-XX:MaxTenuringThreshold=10), even through CMS gc has
ran several times.
I think its the cause of the above-mentioned problems.
In the client, i closed the iterator after every query, code
like this :
...................
FeatureSource featureSource =
dataStore.getFeatureSource(simpleFeatureTypeName);
FeatureIterator featureItr =
featureSource.getFeatures(query).features();
int n = 0;
while (featureItr.hasNext()) {
Feature feature = featureItr.next();
++n;
}
featureItr.close();
....................
so, i guess somewhere in geomesa query maybe cause mem
leak?
_______________________________________________
geomesa-users mailing list
geomesa-users@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
http://www.locationtech.org/mailman/listinfo/geomesa-users
|
