Error on GFI when >1 dataset loaded in map view about comt-ui HOT 7 CLOSED

@kknee Did you click on the Error link in the legend?

It should be able to drill through all active layers. If the Error kill doesn't help, please post the layers you used.

from comt-ui.

Error link appears to have data, this is what I'm using:
inundation_tropical_UND_ADCIRC_Hurricane_Rita_3D_final_run_with_waves
inundation_tropical_UND_ADCIRC_Hurricane_Rita_2D_final_run_with_waves

from comt-ui.

What variable?

from comt-ui.

Zeta, e.g.: http://comt.sura.org:8080/wms/datasets/inundation_tropical_UND_ADCIRC_Hurricane_Rita_2D_final_run_with_waves/?LAYERS=zeta&TRANSPARENT=TRUE&STYLES=pcolor_average_jet_None_None_grid_False&FORMAT=image%2Fpng&TIME=2005-09-18T00%3A00%3A00%2F2005-09-30T00%3A00%3A00&SERVICE=WMS&VERSION=1.1.1&REQUEST=GetFeatureInfo&SRS=EPSG%3A3857&INFO_FORMAT=text%2Fjavascript&QUERY_LAYERS=zeta&BBOX=-12458135.05991%2C1587466.943362%2C-7321566.759861%2C4092155.485862&WIDTH=1050&HEIGHT=512&X=497&Y=169&callback=foo&callback=jQuery1111037143145804293454_1406581098693&_=1406581098705

from comt-ui.

At least one was timing out. Since you are firing 2 requests simultaneously, I guess the backend starts sweating. I just ran it, and query 1 took 50 sec while query 2 took just over 60 sec.

You want me to up the timeout from its current 30 sec? A disadvantage to this is that the UI will have to wait for the full timeout to report queries that really bomb (due to an internal error).

from comt-ui.

Does increasing it really solve the problem? What if the user has more than 2 layers loaded? Is there some way to stagger the requests?

from comt-ui.

I think we should ask the services guys what they think. I doubt staggering or daisy chaining will help any, and will a user really want to wait a minute or longer for the final result, anyway?

from comt-ui.