First, thanks for taking the time to dig into this, we appreciate the help. Indeed there<br>were large changes between 5.6 and 6.0 due to some overall changes in the parser<br>and query handling. I wouldn't have thought they would introduce any issues specific<br>
to a particular driver though. <br><br>It may be that the SDE code needs to simply be made more robust. If I supply a patch<br>that does that can you test?<br><br>Steve<br><br><div class="gmail_quote">On Thu, Jul 21, 2011 at 12:00 PM, myOpenLayersUName <span dir="ltr"><<a href="mailto:joanne.mcgraw@sympatico.ca">joanne.mcgraw@sympatico.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">I've done some additional debugging and have learned that the mapwfs.c's<br>
msWFSGetFeature has changed significantly between 5.6.3 and 6.0.1. In<br>
particular, the problem seems to be starting at line 2457 in the 6.0.1 code<br>
(1248 in 5.6.3). At that point, a call to msOWSGetLayerExtent is made and<br>
part of that process creates and frees a connection to SDE. That is the<br>
first connection that is identified in the above posts (and in Michelle<br>
Douvil's post discussing her GDB findings).<br>
<br>
The second SDE connection is not made in 6.0.1 because, at line 2500 (still<br>
in mapwfs.c's), there is a call to msQueryByRect(map) which did not happen<br>
in 5.6.3. In that function (msQueryByRect), at line 1024, there is a<br>
msLayerClose(lp) call that ultimately takes us to the msSDELayerFreeItemInfo<br>
where the layer->layerinfo (and therefore the sde variable at line 2116) is<br>
already null because of the previous close (in the msOWSGetLayerExtent<br>
process) and so the "if (sde->basedefs)" condition gives a segmentation<br>
fault because it's trying to access a property in an object that doesn't<br>
exist.<br>
<br>
I really don't know anything about any of this code but know that what I<br>
describe is definitely what is happening as far as I can observe. I am<br>
hoping that someone who knows more about the code can identify whether there<br>
is a problem with the source code related to all this. And, if so, should I<br>
be putting something in the DEV forum about this?<br>
<font color="#888888"><br>
<br>
--<br>
View this message in context: <a href="http://osgeo-org.1803224.n2.nabble.com/Can-t-WFS-getFeature-w-MapServer-6-0-1-tp6600286p6607659.html" target="_blank">http://osgeo-org.1803224.n2.nabble.com/Can-t-WFS-getFeature-w-MapServer-6-0-1-tp6600286p6607659.html</a><br>
</font><div><div></div><div class="h5">Sent from the Mapserver - User mailing list archive at Nabble.com.<br>
_______________________________________________<br>
mapserver-users mailing list<br>
<a href="mailto:mapserver-users@lists.osgeo.org">mapserver-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/mapserver-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapserver-users</a><br>
</div></div></blockquote></div><br>