Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't WFS getFeature, nqeury, WMS Getfeatureinfo w/MapServer 6.0.1 and ArcSDE #3977

Closed
mapserver-bot opened this issue Apr 4, 2012 · 10 comments
Assignees

Comments

@mapserver-bot
Copy link

Reporter: myopic73
Date: 2011/08/02 - 07:11
Trac URL: http://trac.osgeo.org/mapserver/ticket/3977
Steve Lime asked me to add the ticket, Subject: Re: RE: Can't WFS getFeature w/MapServer 6.0.1

Yes, it did. The problem was that the GetFeatureInfo code in 6
does two layer open/close processes. Or, at least it tries to.
It fails on the second one because the code tries to reset the
connection which has already been cleared before it does the
layer open. Now that it doesn't fail with the reset, the second
layer open succeeds and the query is processed.

Interestingly, the problem itself has been around for a while
(see http://osgeo-org.1803224.n2.nabble.com/error-while-closing-
sde-layer-td5464449.html in re: MapServer 5.6.3). It's only
become apparent in these OGC queries in MapServer 6 because the
code for the queries have changed so much and it's peppered with
these connection resets before doing any layer open. They
weren't doing that before. And, apparently, most of that code
was tested with Shapefiles, so the failures in the SDE
connections wouldn't have shown up. Having said that, I've also
found a similar problem that exhibits itself in certain
circumstances with the Shapefiles. The MapServer developers are
aware of that one too.

in mapsde.c's msSDELayerFreeItemInfo to handle the SDE problems.

see thread for possible resolution..
http://osgeo-org.1803224.n2.nabble.com/Can-t-WFS-getFeature-w-MapServer-6-0-1-td6600286.html

@mapserver-bot
Copy link
Author

Author: sdlime
Date: 2011/08/09 - 08:05
I've patched branch-6-0 with what I hope is the correct fix. It's basically what was suggested earlier. The msSDELayerFreeItemInfo() was doing more work than it should compared to the other drivers so I pulled the extra code too.

Changes are in 9b5f9bd (r12031), anyway you can test on your end?

Steve

myopic73, can you refresh my memory on the similar shapefile issue?

@mapserver-bot
Copy link
Author

Author: sholl
Date: 2011/08/09 - 09:26
Steve,

I patched your fix from 9b5f9bd (r12031) against trunk (applies clean) and tested.

Same result, truncated GetCaps with WMS 1.3.0, 1.1.1, 1.1.0, only 1.0.0 comes out correct. Perhaps this is a help to find the reason?!

TIA

Stephan

@mapserver-bot
Copy link
Author

Author: myOpenLayersUName
Date: 2011/08/19 - 18:30
Steve,

I have just used the proposed patch to build a new MapServer 6.0.1 executable. I am able to successfully perform a WFS getFeature request against data in SDE when the request has a spatial filter defined AND a maxFeatures parameter limitation...which was what I couldn't do when this whole thing started.

In re: "can you refresh my memory on the similar shapefile issue?" It's the same problem. I can't make a successful WFS getFeature request that has a spatial filter defined AND a maxFeatures parameter limitation when I'm using a Shapefile either. The request will correctly respond with a maxFeatures parameter OR the spatial filter defined, but not both.

Cheers,
jtm

@mapserver-bot
Copy link
Author

Author: sdlime
Date: 2011/09/05 - 16:54
I know the issue (check a new thread started on mapserver-dev) with regards to maxFeatures and hope to patch 6.0 and trunk very soon with a fix. I'll post the ticket for these changes here ASAP...

Steve

@mapserver-bot
Copy link
Author

Author: sdlime
Date: 2011/09/06 - 14:54
See also #4011... Steve

@mapserver-bot
Copy link
Author

Author: jmckenna
Date: 2011/10/04 - 16:45
Stephan: I have hit this truncated getcapabilities response again (on Windows). Should we open a new ticket for this? (we'll probably have to create a small test package so devs can replicate)

@mapserver-bot
Copy link
Author

Author: sholl
Date: 2011/10/05 - 09:08
Jeff,

Replying to [comment:8 jmckenna]:

Stephan: I have hit this truncated getcapabilities response again (on Windows). Should we open a new ticket for this? (we'll probably have to create a small test package so devs can replicate)

Yes, seems reasonable. I cannot create a Testopackage since my SDE-datasets are not available. If this applies also on not-SDE-features, I am happy to create a small shapefile-driven testcase. But I am sure it needs SDE to reproduce it.

Are you willing to create a new ticket though?

Best

Stephan

@mapserver-bot
Copy link
Author

Author: jmckenna
Date: 2011/10/05 - 18:41
Stephan: yesterday I hit the exact same issue, using PostGIS, and I filed a new ticket #4039. My problem is that this issue happens on a client's machine, and I cannot duplicate locally with PostGIS.

There's a problem somewhere here...but we just need to be able to create a small testcase so the devs can tackle it. :(

@tbonfort
Copy link
Member

tbonfort commented Jul 3, 2013

I doubt #4039 is related. Removing the 6.0.4 milestone. @sdlime please reassign a valid milestone (or maybe close?)

@jratike80
Copy link

Since MS 7.0 native ESRI SDE layers are no longer supported (see #5068).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants