Hi all, The Feb 20th patch does not aid the problem at all. I have randomly appearing dots and polylines too and a quick bit of debugging showed that I have nothing in the secondary nodes data at all, so the patch does not have any effect.
Furthermore, I think I have discovered the problem - the geocode requests are too quick and are hitting the Google Maps API limit (which is some number of requests every 1.7 seconds or something stupid). I changed the geocoder.getLatLng call into a geocoder.getLocations to get the request status - all the points that are randomly failing are returning the 620 error code - G_GEO_TOO_MANY_QUERIES. I don't understand, however, how there are too many queries as the DeferredLock is acquired before the getLatLng call and then only released in the callback meaning the request should be done and it is only possible for one at a time to occur at once - is this correct, or have I misunderstood the DeferredLock semantics? Maybe this information will help one of the developers fix the problem, as the Google Maps portlet is most useful and quite important to the large client to whom I've just rolled out Zenoss. Regards, Johan. -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=17479#17479 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
