Steve: Did you ever track down what changed between versions? Was is just a
default value or something more significant in the query processing. --Steve
-Original Message-
From: Stephen Woodbridge [mailto:wood...@swoodbridge.com]
Sent: Wednesday, July 15, 2015 8:43 AM
To: Lime, Steve D
Hi Steve,
Thanks for asking. I put the details in:
https://github.com/mapserver/mapserver/issues/5120
I don't know what changed from 6.2 to 6.4 other than it seems that
all(many?) default values changed which changed the behavior significantly.
I was able to get things working by using a
On 7/14/2015 4:09 PM, Lime, Steve D (MNIT) wrote:
I think the map-query.maxfeatures is pretty much settable only
through WFS. If you're using the template driver output format you
can limit the number of features that way. You'd use the limit
property of the feature tag.
That said, it seems to
OK, not totally solved! Things are better by explicitly setting
TOLERANCE and TOLERANCEUNITS but I am still getting random hanging of
processes doing queries.
I'm wondering if this is related to apache 2.4 and the way it is setting
up cgi-bin processes. What is the best practice for
Ans not related to apache, I can still reproduce this at the
commandline, although it is harder to find a case that fails now that I
have set TOLERANCE and TOLERANCEUNITS.
Is there a way to limit the number of features like MAXFEATURES for
drawing, only for queries?
I see in the code
I think the map-query.maxfeatures is pretty much settable only through WFS. If
you're using the template driver output format you can limit the number of
features that way. You'd use the limit property of the feature tag.
That said, it seems to me that you'd want to use TOLERANCE 0 with
Ok, I think I have found a work around to my issue, now I just have to
update lots and lots of classes in lots of mapfiles and a dozen or so
ajax handlers to update to work around the issue.
I updated https://github.com/mapserver/mapserver/issues/5120
It looks like I can add PROCESSING
Thomas,
More information:
/u/software/mapserver-rel-6-4-2/maptemplate.c:4366
4366for(j=0; jlp-resultcache-numresults; j++) {
(gdb) p lp-resultcache-numresults
$7 = 2884991
this is clearly a bad value my guess is that it is not getting
initialized to zero and assumes it will get set
Thomas,
Here is the initial backtrace afte starting it and and ^C while it is
printing -9 lines:
#0 processLine (mapserv=0x609050, instr=0x7fffcc60 [value_0]\n,
stream=0x688460, mode=9)
at /u/software/mapserver-rel-6-4-2/maptemplate.c:3697
#1 0x77a2e9cc in
On 7/13/2015 9:06 AM, Daniel Morissette wrote:
Steve,
Can you run the query in Valgrind? It can be a quick way to catch memory
handling issues (buffer overflows or access to uninitialized memory)
which can sometimes lead to this kind of loops as a side-effect.
FYI, if you have more than 4
Steve,
Can you run the query in Valgrind? It can be a quick way to catch memory
handling issues (buffer overflows or access to uninitialized memory)
which can sometimes lead to this kind of loops as a side-effect.
FYI, if you have more than 4 bands in one of your images then you may
have
SOLVED: see below ...
According to the docs, the defaults are:
TOLERANCE 3
TOLERANCEUNITS pixels
and with:
QUERY_STRING='map=/maps/wms/bathymetry.mapmode=querylayers=model_querymapxy=-100.98125+41.58125'
How is zoom calculated?
LAYER
NAME model_query
STATUS on
TYPE raster
TILEINDEX
Or that could just be the number of pixels under the query point if
you are zoomed out far or with a large tolerance...
On 13 July 2015 at 17:01, Stephen Woodbridge wood...@swoodbridge.com wrote:
Thomas,
More information:
/u/software/mapserver-rel-6-4-2/maptemplate.c:4366
4366
Steve,
please include a backtrace from gdb where you believe the infinite
loop is happening.
--
thomas
On 13 July 2015 at 01:22, Stephen Woodbridge wood...@swoodbridge.com wrote:
I added gdalinfo on an actual raster file below. It turns out the -9 is
the NoData Value. I would be happy to
I added gdalinfo on an actual raster file below. It turns out the -9
is the NoData Value. I would be happy to just get this value back
(once), but I think something is broken and putting mapserver into an
infinite loop.
-Steve W
On 7/12/2015 7:14 PM, Stephen Woodbridge wrote:
Hi all,
I
Hi all,
I have run into a very strange problem doing a mapserver query. I'm
upgrading a system that was running fine. The details are below. I also
tried to put the template inside a CLASS ... END block that didn't help.
Can anyone else reproduce something like this?
Got any ideas on how to
16 matches
Mail list logo
