I don't know what's going on, but we're intermittently running into
the same issue at
http://broadband.com/map. We opened a ticket with
Google on Friday and haven't been able to resolve the issue yet.
The trouble seems to have started on Wednesday or Thursday. About 30%
of the time any of the KML layers will fail to load.
Our map connects with up to four KMZ files hosted on Amazon S3. We've
run load testing against the KMZ files directly and see 0% failure and
very fast response. If we copy the callback URL that the googleapi
creates to talk to the KmlOverlayService into a browser and refresh we
see it flip back and forth from actual data to the 500 server error
page.
I'll update when I have more info.
-- Stephen
On Apr 5, 12:34 pm, Tony <
ton.anh...@gmail.com> wrote:
> Hi there, there doesn't seem to be many threads/posts on people having
> this issue, but I hope someone has an answer.
>
> I have a KMZ file that is generated on the fly. A typical KMZ file
> that is generated will have approximately 16 Placemarks. Each
> Placemark will contain a MultiGeometry element, then a single Polygon
> element. The Polygon element will have a bunch of children elements,
> and the only one I think worth mentioning would be the "coordinates"
> one. Each coordinates element contains roughly ~1500 coordinates in
> total. The file size of the KMZ is under 500KB usually. And I don't
> think I exceed any of the limits stated onhttp://
code.google.com/apis/kml/documentation/mapsSupport.html.
>
> When I go to create the layer using this KMZ file generator location,
> the layer will sometimes not display on my map. If I look in FireBug,
> I'll be able to see the request to KmlOverlayService failing and
> stating a500InternalServerError. If I then copy the Location for
> that request and visit it in a new window, the page will load a bunch
> of text which I assume means it's working since it doesn't give me a500error anymore. If I now hard refresh my map's web page, the KMZ
> layer will load perfectly fine.
>
> Cliffs:
> KMZ file seems to be under the limits, but generates a500error
> intermittently when loading the layer.
> When500error occurs, accessing KmlOverlayService directly will load