I’m trying to carry out a WFS-T insert and update and I’m seeing deadlocks on the describeFeatureType request which look a lot like https://jira.codehaus.org/browse/GEOS-4854 which is marked as fixed in 2.2.x?
Does any one know if this is the same problem (come back from the dead?) or should I keep digging?
Ian
–
Ian Turton
On Mon, Sep 10, 2012 at 4:29 PM, Ian Turton <ijturton@anonymised.com> wrote:
I’m trying to carry out a WFS-T insert and update and I’m seeing deadlocks on the describeFeatureType request which look a lot like https://jira.codehaus.org/browse/GEOS-4854 which is marked as fixed in 2.2.x?
Does any one know if this is the same problem (come back from the dead?) or should I keep digging?
It was fixed in 2.1.x, but regressed in 2.2.x (unfortunately it’s not possible to test it with our current test harness,
it requires a GeoServer that’s running for good), but then I’ve fixed it again for 2.2-RC3
Cheers
Andrea
–
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
On 10 September 2012 15:41, Andrea Aime <andrea.aime@anonymised.com> wrote:
On Mon, Sep 10, 2012 at 4:29 PM, Ian Turton <ijturton@anonymised.com> wrote:
I’m trying to carry out a WFS-T insert and update and I’m seeing deadlocks on the describeFeatureType request which look a lot like https://jira.codehaus.org/browse/GEOS-4854 which is marked as fixed in 2.2.x?
Does any one know if this is the same problem (come back from the dead?) or should I keep digging?
It was fixed in 2.1.x, but regressed in 2.2.x (unfortunately it’s not possible to test it with our current test harness,
it requires a GeoServer that’s running for good), but then I’ve fixed it again for 2.2-RC3
The mystery deepens - with the latest master-war and a clean tomcat (7.0.30) I can’t make a describeFeatureType (1.0.0 or 1.1.0) at all from the demo page.
I’ve attached the log file but I can’t see anything obvious.
Ian
geoserver.log (67.4 KB)
On 10 September 2012 16:18, Ian Turton <ijturton@anonymised.com> wrote:
On 10 September 2012 15:41, Andrea Aime <andrea.aime@anonymised.com> wrote:
On Mon, Sep 10, 2012 at 4:29 PM, Ian Turton <ijturton@anonymised.com> wrote:
I’m trying to carry out a WFS-T insert and update and I’m seeing deadlocks on the describeFeatureType request which look a lot like https://jira.codehaus.org/browse/GEOS-4854 which is marked as fixed in 2.2.x?
Does any one know if this is the same problem (come back from the dead?) or should I keep digging?
It was fixed in 2.1.x, but regressed in 2.2.x (unfortunately it’s not possible to test it with our current test harness,
it requires a GeoServer that’s running for good), but then I’ve fixed it again for 2.2-RC3The mystery deepens - with the latest master-war and a clean tomcat (7.0.30) I can’t make a describeFeatureType (1.0.0 or 1.1.0) at all from the demo page.
I’ve attached the log file but I can’t see anything obvious.
However typing the url (http://localhost:8080/geoserver/topp/wfs?service=WFS&version=1.1.0&request=DescribeFeatureType&typeName=topp%3Astates ) does work so I’m at a loss to explain it.
Ian
On Mon, Sep 10, 2012 at 5:18 PM, Ian Turton <ijturton@anonymised.com> wrote:
On 10 September 2012 15:41, Andrea Aime <andrea.aime@anonymised.com> wrote:
On Mon, Sep 10, 2012 at 4:29 PM, Ian Turton <ijturton@anonymised.com> wrote:
I’m trying to carry out a WFS-T insert and update and I’m seeing deadlocks on the describeFeatureType request which look a lot like https://jira.codehaus.org/browse/GEOS-4854 which is marked as fixed in 2.2.x?
Does any one know if this is the same problem (come back from the dead?) or should I keep digging?
It was fixed in 2.1.x, but regressed in 2.2.x (unfortunately it’s not possible to test it with our current test harness,
it requires a GeoServer that’s running for good), but then I’ve fixed it again for 2.2-RC3The mystery deepens - with the latest master-war and a clean tomcat (7.0.30) I can’t make a describeFeatureType (1.0.0 or 1.1.0) at all from the demo page.
I’ve attached the log file but I can’t see anything obvious.
Hmm… gedit won’t open the log file at all, and “less” displays me something like:
topp:states
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@
^@^@^@^@^@^@^@^@^@^@^@^@^@
It seems there are some issues with the char encoding…
Cheers
Andrea
–
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it