[Geoserver-users] Problem with QGis and WFS-T

GeoServer GeoServer User
1

I tried to use Qgis to add/modify features of a geoserver WFS-T layer.

When I save the layer the operation timeouts.

The qgis error is similar to the one found here:

http://gis.stackexchange.com/questions/115471/qgis-wfs-error-could-not-commit-changes-to-layer

Provider errors: empty response

Qgis network log is similar to:

Network request http://*******.com:**/geoserver/****/wfs?SERVICE=WFS&VERSION=1.0.0&SRSNAME=EPSG:3308 timed out

The problem could be related to http://jira.codehaus.org/browse/GEOS-6059

After the error Qgis stops loading the wfs layer (any layer from that geoserver) and I have to restart geoserver to be able to load a layer in Qgis again.

1st question: how come that a call from qgis "kills" something in geoserver WFS service?

2nd question: is there a solution to the qgis problem (I know, better to ask that to the qgis people)

Trying to understand what was wrong in the qgis call (update of a feature or new feature added) I used netTool. This program has a tunnel feature that acts as a MITM between an application and a remote server.
So I changed the wfs address in qgis from:
http://mywebsite:8080/geoserver/wfs to http://localhost:7000/geoserver/wfs and set netTool to tunnel to http://mywebsite:8080
I updated a feature value, saved and to my great surprise everything worked fine. How is that possible?
NetTool changes something in the qgis call (POST) to the server that doesn't stop WFS from working correctly. Or is there something else?

Thank you
  maxx

p.s. I'm (still) using Boundless Opengeo suite 4.1 version of geoserver (2.5 SNAPSHOT)
Qgis is version 2.6 installed on slackware 14.1

2

Il 01/20/2015 09:00 PM, emmexx scrisse:

I tried to use Qgis to add/modify features of a geoserver WFS-T layer.

When I save the layer the operation timeouts.

On the qgis bug tracker system I was suggested to try to connect to an osgeo live DVD.

I modified some feature using wfs in qgis and saved without errors.

So the problem is my geoserver. :frowning:

I created a new simple table in postgis, added a layer in geoserver and tried to modify a value of one record using qgis and wfs.
Same problem: qgis timeouts and I can't use it anymore to make a wfs connection to geoserver until I restart geoserver.
I can't connect to wfs using the layer preview tool too.

At the end of this message I copy what geoserver logged while using qgis, adding the layer (to qgis) and commiting.

Since I'm using the boundless version of geoserver, I know not much help can be given here.

I wonder if it is possible to go from boundless geoserver version to the standard version without much pain and keeping alla data and settings.
Has anybody done this and can give advice or just tell me if it can be done?

thank you
   maxx

2015-01-24 05:48:12,064 INFO [geoserver.wfs] -
Request: getServiceInfo
2015-01-24 05:48:12,068 INFO [geoserver.wfs] -
Request: getCapabilities
     acceptVersions:
         version[0] = 1.0.0
     baseUrl = http://example.com:8080/geoserver/
     service = WFS
2015-01-24 05:48:16,020 INFO [geoserver.wfs] -
Request: getServiceInfo
2015-01-24 05:48:16,021 INFO [geoserver.wfs] -
Request: describeFeatureType
     service = WFS
     version = 1.0.0
     baseUrl = http://example.com:8080/geoserver/
     typeName[0] = {http://myserver.com}testlayer
     outputFormat = XMLSCHEMA
2015-01-24 05:48:16,384 INFO [geoserver.wfs] -
Request: getServiceInfo
2015-01-24 05:48:16,395 INFO [geoserver.wfs] -
Request: getFeature
     service = WFS
     version = 1.0.0
     baseUrl = http://example.com:8080/geoserver/
     query[0]:
         srsName = EPSG:4326
         typeName[0] = {http://myserver.com}testlayer
     maxFeatures = 1
     outputFormat = GML2
     resultType = results
2015-01-24 05:48:16,707 INFO [geoserver.wfs] -
Request: getServiceInfo
2015-01-24 05:48:16,710 INFO [geoserver.wfs] -
Request: getFeature
     service = WFS
     version = 1.0.0
     baseUrl = http://example.com:8080/geoserver/
     query[0]:
         srsName = EPSG:4326
         typeName[0] = {http://myserver.com}testlayer
     outputFormat = GML2
     resultType = results
2015-01-24 05:48:17,090 INFO [geoserver.wfs] -
Request: getServiceInfo
2015-01-24 05:48:17,095 INFO [geoserver.wfs] -
Request: getCapabilities
     acceptVersions:
         version[0] = 1.0.0
     baseUrl = http://example.com:8080/geoserver/
     service = WFS
2015-01-24 05:49:19,130 INFO [geoserver.wfs] -
Request: getServiceInfo
2015-01-24 05:49:19,279 INFO [geoserver.wfs] -
Request: getServiceInfo
2015-01-24 05:49:19,280 INFO [geoserver.wfs] -
Request: describeFeatureType
     service = WFS
     version = 1.0.0
     baseUrl = http://example.com:8080/geoserver/
     typeName[0] = {http://myserver.com}testlayer
     outputFormat = XMLSCHEMA
2015-01-24 05:52:39,538 INFO [geoserver.wfs] -
Request: getServiceInfo
2015-01-24 05:52:39,575 INFO [geoserver.wfs] -
Request: getCapabilities
     acceptVersions:
         version[0] = 1.0.0
     baseUrl = http://example.com:8080/geoserver/
     service = WFS
2015-01-24 05:52:45,391 INFO [geoserver.wfs] -
Request: getServiceInfo
2015-01-24 05:52:45,392 INFO [geoserver.wfs] -
Request: describeFeatureType
     service = WFS
     version = 1.0.0
     baseUrl = http://example.com:8080/geoserver/
     typeName[0] = {http://myserver.com}layer2
     outputFormat = XMLSCHEMA

3

On Sat, Jan 24, 2015 at 12:11 PM, emmexx <emmexx@anonymised.com> wrote:

Since I'm using the boundless version of geoserver, I know not much help
can be given here.

Probably none, you should ask Boundless for support

Cheers
Andrea

--

GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.

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 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

-------------------------------------------------------

4

Il 01/20/2015 09:00 PM, emmexx scrisse:

p.s. I'm (still) using Boundless Opengeo suite 4.1 version of geoserver
(2.5 SNAPSHOT)
Qgis is version 2.6 installed on slackware 14.1

I upgraded opengeosuite to 4.5 and geoserver 2.6.

The problem are stille there. I can't use qgis to update features and attributes.

bye
  maxx

5

On Sun, Feb 22, 2015 at 11:23 PM, emmexx <emmexx@anonymised.com> wrote:

Il 01/20/2015 09:00 PM, emmexx scrisse:
> p.s. I'm (still) using Boundless Opengeo suite 4.1 version of geoserver
> (2.5 SNAPSHOT)
> Qgis is version 2.6 installed on slackware 14.1

I upgraded opengeosuite to 4.5 and geoserver 2.6.

The problem are stille there. I can't use qgis to update features and
attributes.

Until you report issues against the opengeosuite version of GeoServer
you'll probably receive no help here, the way to go is to contact your
Boundless representatives.

A suggestion: take a recent standard GeoServer release (one downloaded from
geoserver.org),
repeat the test, if it fails, enable the request logging in web.xml,
and then open a ticket with all the details to reproduce, like a sample of
your data, the request that fails, and so on

Cheers
Andrea

--

GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.

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 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

-------------------------------------------------------

6

Il 02/23/2015 08:11 AM, Andrea Aime scrisse:

Until you report issues against the opengeosuite version of GeoServer
you'll probably receive no help here, the way to go is to contact your
Boundless representatives.

I was reporting it in case that happens to other people.
I don't have a Boundless representative, unfortunately when I setup opengeo I misunderstood the relationship between them and the geoserver developers. My fault, of course.

A suggestion: take a recent standard GeoServer release (one downloaded
from geoserver.org <http://geoserver.org>),
repeat the test, if it fails, enable the request logging in web.xml,
and then open a ticket with all the details to reproduce, like a sample of
your data, the request that fails, and so on

Is it possible to run the 2 instances of geoserver on the same server? It's a production server, I'd rather prefer not to stop serving data.
I'd like to make the tests on the same server because I'm not sure the problem is with the boundless geoserver package (why should they do that?) but with some configuration of the server.

Thank you
  maxx

7

Il 02/23/2015 08:11 AM, Andrea Aime scrisse:

A suggestion: take a recent standard GeoServer release (one downloaded
from geoserver.org <http://geoserver.org>),
repeat the test, if it fails, enable the request logging in web.xml,
and then open a ticket with all the details to reproduce, like a sample of
your data, the request that fails, and so on

I made some experiment to find out what is the problem using qgis and geoserver. The behaviour is erratic so I need some help to understand what to check.

1st experiment:
I used the aws elastic beanstalk service to install geoserver 2.6.2.
In Qgis I loaded the Tasmania road layer and I could insert new features, update geometries and attributes. The problem is that qgis always reports errors committing but sometimes data are saved, sometimes not, sometimes features are lost.
For example last week I made many test updates and usually got a qgis error but data were saved almost always.
Today I can't update anything. I get a qgis error when I commit and data are not saved (I tried 10 times changing one attribute o adding nodes, moving lines).
Ok, this can be a qgis problem.

2nd experiment
I tried to get free of the boundless version of geoserver.
I created a new aws ami instance, installed tomcat7 and the war version of geoserver 2.6.2.
Again in qgis I added the Tasmania road layer, moved a node of a line, committed, get a qgis empty response error and from now on WFS stops responding. I have to restart tomcat in order to use again wfs.
I used the Demo requests tool and I get no answer when making wfs requests.
So this is not a qgis problem.

The default error log reports nothing.

I attach the geoserver log after select the development one.
The following are the operations I did in qgis that are reported in the log:
- connect to geoserver
- add the Tasmania Layer
- move a node and change the type attribute value
- commit (I get a qgis error)
- remove the layer from qgis
- add the layer: I get an error message and the layer is not added
- I open the geoserver web Demo Requests page
- select WFS_getFeatureBBOX-1.0.xml
- submit (the popup open with the text Loading..... and stays there)

If I can give other info or make other tests, just ask me.

Thank you
  maxx

geoserverami.log (58.9 KB)

8

Just a quick update, since boundless was mentioned.

Kevin has been looking at http://jira.codehaus.org/browse/GEOS-6059 and seems to have found an hard deadlock internal to GeoServer. I have been waiting for him to start a discussion on geoserver-devel :slight_smile:

Larry has found a workaround on the QGIS side and will look at getting that included in QGIS 2.8.1.

Note that this is nothing to do with opengeo suite, the issue is strictly a problem with GeoServer and deadlock with the schema cache :frowning:

···

On 20 January 2015 at 12:00, emmexx <emmexx@anonymised.com> wrote:

I tried to use Qgis to add/modify features of a geoserver WFS-T layer.

When I save the layer the operation timeouts.

The qgis error is similar to the one found here:

http://gis.stackexchange.com/questions/115471/qgis-wfs-error-could-not-commit-changes-to-layer

Provider errors: empty response

Qgis network log is similar to:

Network request
http://***.com:**/geoserver//wfs?SERVICE=WFS&VERSION=1.0.0&SRSNAME=EPSG:3308
timed out

The problem could be related to http://jira.codehaus.org/browse/GEOS-6059

After the error Qgis stops loading the wfs layer (any layer from that
geoserver) and I have to restart geoserver to be able to load a layer in
Qgis again.

1st question: how come that a call from qgis “kills” something in
geoserver WFS service?

2nd question: is there a solution to the qgis problem (I know, better to
ask that to the qgis people)

Trying to understand what was wrong in the qgis call (update of a
feature or new feature added) I used netTool. This program has a tunnel
feature that acts as a MITM between an application and a remote server.
So I changed the wfs address in qgis from:
http://mywebsite:8080/geoserver/wfs to
http://localhost:7000/geoserver/wfs and set netTool to tunnel to
http://mywebsite:8080
I updated a feature value, saved and to my great surprise everything
worked fine. How is that possible?
NetTool changes something in the qgis call (POST) to the server that
doesn’t stop WFS from working correctly. Or is there something else?

Thank you
maxx

p.s. I’m (still) using Boundless Opengeo suite 4.1 version of geoserver
(2.5 SNAPSHOT)
Qgis is version 2.6 installed on slackware 14.1

New Year. New Location. New Benefits. New Data Center in Ashburn, VA.
GigeNET is offering a free month of service with a new server in Ashburn.
Choose from 2 high performing configs, both with 100TB of bandwidth.
Higher redundancy.Lower latency.Increased capacity.Completely compliant.
http://p.sf.net/sfu/gigenet

Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

–
Jody Garnett

9

As per other email, please add your experience to http://jira.codehaus.org/browse/GEOS-6059 .

Some quick fixes:

  • If you are on windows ensure that your hosts file is configured correctly (for any tests involving localhost)
  • If you are hiding behind a proxy be sure to adjust the base url setting

The common thread here is that GeoServer needs to be able to “detect” when Transaction request document references a schema defined by DescribeFeatureType. It needs to be sure to resolve that “internally” rather than via HTTP.

···

On 3 March 2015 at 03:35, emmexx <emmexx@…6749…> wrote:

Il 02/23/2015 08:11 AM, Andrea Aime scrisse:

A suggestion: take a recent standard GeoServer release (one downloaded
from geoserver.org <http://geoserver.org>),
repeat the test, if it fails, enable the request logging in web.xml,
and then open a ticket with all the details to reproduce, like a sample of
your data, the request that fails, and so on

I made some experiment to find out what is the problem using qgis and geoserver. The behaviour is erratic so I need some help to understand what to check.

1st experiment:
I used the aws elastic beanstalk service to install geoserver 2.6.2.
In Qgis I loaded the Tasmania road layer and I could insert new features, update geometries and attributes. The problem is that qgis always reports errors committing but sometimes data are saved, sometimes not, sometimes features are lost.
For example last week I made many test updates and usually got a qgis error but data were saved almost always.
Today I can’t update anything. I get a qgis error when I commit and data are not saved (I tried 10 times changing one attribute o adding nodes, moving lines).
Ok, this can be a qgis problem.

2nd experiment
I tried to get free of the boundless version of geoserver.
I created a new aws ami instance, installed tomcat7 and the war version of geoserver 2.6.2.
Again in qgis I added the Tasmania road layer, moved a node of a line, committed, get a qgis empty response error and from now on WFS stops responding. I have to restart tomcat in order to use again wfs.
I used the Demo requests tool and I get no answer when making wfs requests.
So this is not a qgis problem.

The default error log reports nothing.

I attach the geoserver log after select the development one.
The following are the operations I did in qgis that are reported in the log:

  • connect to geoserver
  • add the Tasmania Layer
  • move a node and change the type attribute value
  • commit (I get a qgis error)
  • remove the layer from qgis
  • add the layer: I get an error message and the layer is not added
  • I open the geoserver web Demo Requests page
  • select WFS_getFeatureBBOX-1.0.xml
  • submit (the popup open with the text Loading… and stays there)

If I can give other info or make other tests, just ask me.

Thank you
maxx

Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/

Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

–
Jody Garnett

10

Hello Jody, Maxx and Andrea,

thank you very much for your thoroughly investigation concerning this QGIS - GeoServer WFS-T issue.
I have trouble with GeoServer WFS-T and QGIS too.
Even though I can edit (move) an existing geometry of an imported WFS-T and save my changes in QGIS. But I cannot save changes of feature attributes in QGIS for existing geometries. I can add new geometries for GeoServer WFS-T in QGIS and save them. But when I add new geometries for any GeoServer WFS-T in QGIS and try to add feature attributes too, the attributes are apparently saved without an error in QGIS but attributes are not saved in the PostgreSQL/PostGIS database. When I close QGIS the changes and adding of attributes get lost.

I use a common GeoServer 2.5.1 installation with tomcat7 7.0.52-1ubuntu0.1, Apache 2.4.7-1ubuntu4.1 running on Ubuntu 14.04 LTS. QGIS vers. is 2.8.1.

Thank you very much for your support.

Izabella

···

On 3 March 2015 at 21:16, Jody Garnett <jody.garnett@anonymised.com> wrote:

As per other email, please add your experience to http://jira.codehaus.org/browse/GEOS-6059 .

Some quick fixes:

  • If you are on windows ensure that your hosts file is configured correctly (for any tests involving localhost)
  • If you are hiding behind a proxy be sure to adjust the base url setting

The common thread here is that GeoServer needs to be able to “detect” when Transaction request document references a schema defined by DescribeFeatureType. It needs to be sure to resolve that “internally” rather than via HTTP.

Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/

Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

–
Jody Garnett

On 3 March 2015 at 03:35, emmexx <emmexx@anonymised.com> wrote:

Il 02/23/2015 08:11 AM, Andrea Aime scrisse:

A suggestion: take a recent standard GeoServer release (one downloaded
from geoserver.org <http://geoserver.org>),
repeat the test, if it fails, enable the request logging in web.xml,
and then open a ticket with all the details to reproduce, like a sample of
your data, the request that fails, and so on

I made some experiment to find out what is the problem using qgis and geoserver. The behaviour is erratic so I need some help to understand what to check.

1st experiment:
I used the aws elastic beanstalk service to install geoserver 2.6.2.
In Qgis I loaded the Tasmania road layer and I could insert new features, update geometries and attributes. The problem is that qgis always reports errors committing but sometimes data are saved, sometimes not, sometimes features are lost.
For example last week I made many test updates and usually got a qgis error but data were saved almost always.
Today I can’t update anything. I get a qgis error when I commit and data are not saved (I tried 10 times changing one attribute o adding nodes, moving lines).
Ok, this can be a qgis problem.

2nd experiment
I tried to get free of the boundless version of geoserver.
I created a new aws ami instance, installed tomcat7 and the war version of geoserver 2.6.2.
Again in qgis I added the Tasmania road layer, moved a node of a line, committed, get a qgis empty response error and from now on WFS stops responding. I have to restart tomcat in order to use again wfs.
I used the Demo requests tool and I get no answer when making wfs requests.
So this is not a qgis problem.

The default error log reports nothing.

I attach the geoserver log after select the development one.
The following are the operations I did in qgis that are reported in the log:

  • connect to geoserver
  • add the Tasmania Layer
  • move a node and change the type attribute value
  • commit (I get a qgis error)
  • remove the layer from qgis
  • add the layer: I get an error message and the layer is not added
  • I open the geoserver web Demo Requests page
  • select WFS_getFeatureBBOX-1.0.xml
  • submit (the popup open with the text Loading… and stays there)

If I can give other info or make other tests, just ask me.

Thank you
maxx

Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/

Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

11

At the moment I’m thinking a reasonable solution would be to start by just adding ‘localhost’ to the list of reflexive hostnames. That will fix the common failure case on Windows.

To handle other cases, when making a request for an external featureType, we could remember it, and then watch for WFS requests coming in with that hostname. If that happens, add the hostname to the list of self referential hostnames, roll back (maybe return a special error message?) then start on the internal path.

Allowing the admin to manually control the list of self referential hostnames might also be an idea.

···

On 3 March 2015 at 13:45, Izabella Mancini <izabellamancini0789@…84…> wrote:

Hello Jody, Maxx and Andrea,

thank you very much for your thoroughly investigation concerning this QGIS - GeoServer WFS-T issue.
I have trouble with GeoServer WFS-T and QGIS too.
Even though I can edit (move) an existing geometry of an imported WFS-T and save my changes in QGIS. But I cannot save changes of feature attributes in QGIS for existing geometries. I can add new geometries for GeoServer WFS-T in QGIS and save them. But when I add new geometries for any GeoServer WFS-T in QGIS and try to add feature attributes too, the attributes are apparently saved without an error in QGIS but attributes are not saved in the PostgreSQL/PostGIS database. When I close QGIS the changes and adding of attributes get lost.

I use a common GeoServer 2.5.1 installation with tomcat7 7.0.52-1ubuntu0.1, Apache 2.4.7-1ubuntu4.1 running on Ubuntu 14.04 LTS. QGIS vers. is 2.8.1.

Thank you very much for your support.

Izabella

Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/

Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

–

On 3 March 2015 at 21:16, Jody Garnett <jody.garnett@anonymised.com> wrote:

As per other email, please add your experience to http://jira.codehaus.org/browse/GEOS-6059 .

Some quick fixes:

  • If you are on windows ensure that your hosts file is configured correctly (for any tests involving localhost)
  • If you are hiding behind a proxy be sure to adjust the base url setting

The common thread here is that GeoServer needs to be able to “detect” when Transaction request document references a schema defined by DescribeFeatureType. It needs to be sure to resolve that “internally” rather than via HTTP.

Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/

Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

–
Jody Garnett

On 3 March 2015 at 03:35, emmexx <emmexx@anonymised.com> wrote:

Il 02/23/2015 08:11 AM, Andrea Aime scrisse:

A suggestion: take a recent standard GeoServer release (one downloaded
from geoserver.org <http://geoserver.org>),
repeat the test, if it fails, enable the request logging in web.xml,
and then open a ticket with all the details to reproduce, like a sample of
your data, the request that fails, and so on

I made some experiment to find out what is the problem using qgis and geoserver. The behaviour is erratic so I need some help to understand what to check.

1st experiment:
I used the aws elastic beanstalk service to install geoserver 2.6.2.
In Qgis I loaded the Tasmania road layer and I could insert new features, update geometries and attributes. The problem is that qgis always reports errors committing but sometimes data are saved, sometimes not, sometimes features are lost.
For example last week I made many test updates and usually got a qgis error but data were saved almost always.
Today I can’t update anything. I get a qgis error when I commit and data are not saved (I tried 10 times changing one attribute o adding nodes, moving lines).
Ok, this can be a qgis problem.

2nd experiment
I tried to get free of the boundless version of geoserver.
I created a new aws ami instance, installed tomcat7 and the war version of geoserver 2.6.2.
Again in qgis I added the Tasmania road layer, moved a node of a line, committed, get a qgis empty response error and from now on WFS stops responding. I have to restart tomcat in order to use again wfs.
I used the Demo requests tool and I get no answer when making wfs requests.
So this is not a qgis problem.

The default error log reports nothing.

I attach the geoserver log after select the development one.
The following are the operations I did in qgis that are reported in the log:

  • connect to geoserver
  • add the Tasmania Layer
  • move a node and change the type attribute value
  • commit (I get a qgis error)
  • remove the layer from qgis
  • add the layer: I get an error message and the layer is not added
  • I open the geoserver web Demo Requests page
  • select WFS_getFeatureBBOX-1.0.xml
  • submit (the popup open with the text Loading… and stays there)

If I can give other info or make other tests, just ask me.

Thank you
maxx

Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/

Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Kevin Smith

Software Engineer | Boundless

ksmith@anonymised.com

+1-778-785-7459

@boundlessgeo

http://boundlessgeo.com/

12

We should probably move this conversation over to geoserver-devel :slight_smile:

Isabella:

  • are you running on windows? If so please update your hosts and test again…
  • Are you running with a proxy? If so fill in that global setting …
  • Try filling in the global proxy setting with the same server name that QGIS is using during the request

It would also really help Kevin if you were in position to test a geoserver nightly build.

Part of the “deal” of the geoserver-users list (or any user list) is supporting the development team with test data, testing of release candidates and volunteers to test the nightly builds :slight_smile:

···

On 3 March 2015 at 13:58, Kevin Smith <ksmith@anonymised.com> wrote:

At the moment I’m thinking a reasonable solution would be to start by just adding ‘localhost’ to the list of reflexive hostnames. That will fix the common failure case on Windows.

To handle other cases, when making a request for an external featureType, we could remember it, and then watch for WFS requests coming in with that hostname. If that happens, add the hostname to the list of self referential hostnames, roll back (maybe return a special error message?) then start on the internal path.

Allowing the admin to manually control the list of self referential hostnames might also be an idea.

–
Jody Garnett

On 3 March 2015 at 13:45, Izabella Mancini <izabellamancini0789@anonymised.com> wrote:

Hello Jody, Maxx and Andrea,

thank you very much for your thoroughly investigation concerning this QGIS - GeoServer WFS-T issue.
I have trouble with GeoServer WFS-T and QGIS too.
Even though I can edit (move) an existing geometry of an imported WFS-T and save my changes in QGIS. But I cannot save changes of feature attributes in QGIS for existing geometries. I can add new geometries for GeoServer WFS-T in QGIS and save them. But when I add new geometries for any GeoServer WFS-T in QGIS and try to add feature attributes too, the attributes are apparently saved without an error in QGIS but attributes are not saved in the PostgreSQL/PostGIS database. When I close QGIS the changes and adding of attributes get lost.

I use a common GeoServer 2.5.1 installation with tomcat7 7.0.52-1ubuntu0.1, Apache 2.4.7-1ubuntu4.1 running on Ubuntu 14.04 LTS. QGIS vers. is 2.8.1.

Thank you very much for your support.

Izabella

Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/

Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

–

Kevin Smith

Software Engineer | Boundless

ksmith@anonymised.com

+1-778-785-7459

@boundlessgeo

On 3 March 2015 at 21:16, Jody Garnett <jody.garnett@anonymised.com.> wrote:

As per other email, please add your experience to http://jira.codehaus.org/browse/GEOS-6059 .

Some quick fixes:

  • If you are on windows ensure that your hosts file is configured correctly (for any tests involving localhost)
  • If you are hiding behind a proxy be sure to adjust the base url setting

The common thread here is that GeoServer needs to be able to “detect” when Transaction request document references a schema defined by DescribeFeatureType. It needs to be sure to resolve that “internally” rather than via HTTP.

Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/

Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

–
Jody Garnett

On 3 March 2015 at 03:35, emmexx <emmexx@anonymised.com> wrote:

Il 02/23/2015 08:11 AM, Andrea Aime scrisse:

A suggestion: take a recent standard GeoServer release (one downloaded
from geoserver.org <http://geoserver.org>),
repeat the test, if it fails, enable the request logging in web.xml,
and then open a ticket with all the details to reproduce, like a sample of
your data, the request that fails, and so on

I made some experiment to find out what is the problem using qgis and geoserver. The behaviour is erratic so I need some help to understand what to check.

1st experiment:
I used the aws elastic beanstalk service to install geoserver 2.6.2.
In Qgis I loaded the Tasmania road layer and I could insert new features, update geometries and attributes. The problem is that qgis always reports errors committing but sometimes data are saved, sometimes not, sometimes features are lost.
For example last week I made many test updates and usually got a qgis error but data were saved almost always.
Today I can’t update anything. I get a qgis error when I commit and data are not saved (I tried 10 times changing one attribute o adding nodes, moving lines).
Ok, this can be a qgis problem.

2nd experiment
I tried to get free of the boundless version of geoserver.
I created a new aws ami instance, installed tomcat7 and the war version of geoserver 2.6.2.
Again in qgis I added the Tasmania road layer, moved a node of a line, committed, get a qgis empty response error and from now on WFS stops responding. I have to restart tomcat in order to use again wfs.
I used the Demo requests tool and I get no answer when making wfs requests.
So this is not a qgis problem.

The default error log reports nothing.

I attach the geoserver log after select the development one.
The following are the operations I did in qgis that are reported in the log:

  • connect to geoserver
  • add the Tasmania Layer
  • move a node and change the type attribute value
  • commit (I get a qgis error)
  • remove the layer from qgis
  • add the layer: I get an error message and the layer is not added
  • I open the geoserver web Demo Requests page
  • select WFS_getFeatureBBOX-1.0.xml
  • submit (the popup open with the text Loading… and stays there)

If I can give other info or make other tests, just ask me.

Thank you
maxx

Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/

Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

13

Il 03/03/2015 09:16 PM, Jody Garnett scrisse:

As per other email, please add your experience to
http://jira.codehaus.org/browse/GEOS-6059 .

I did it.

Some quick fixes:
- If you are on windows ensure that your hosts file is configured
correctly (for any tests involving localhost)
- If you are hiding behind a proxy be sure to adjust the base url setting

The common thread here is that GeoServer needs to be able to "detect"
when Transaction request document references a schema defined by
DescribeFeatureType. It needs to be sure to resolve that "internally"
rather than via HTTP.

I undestand what you mean but I'm not sure how can I practically accomplish that.
I use an AWS AMI Linux server and I don't use a proxy, but the aws network has his own quirks, I can't change settings at will.
If I understand correctly geoserver reads the client requests and if there's the server address in it, it can't match it to the server address where it is running.
The hostname of the aws server is different from the public dns name, so I can't change it.
Can I change some other setting in the server or in geoserver?

Thank you
  maxx

14

I’ve got a patch put together that allows additional reflexive hostnames to be specified via a system property. It’s a workaround rather than a solution but it might help you.

https://github.com/smithkm/geoserver/commit/4d900caea99f63c4f0a7e674e713dee502ce85ff

By default it adds localhost. It also adds some DEGUG and INFO level logging to help diagnose the issue.

You’d have to cherry-pick onto the appropriate branch and build the wfs module.

I’ll prep a pull request when it’s ready and do backports. Hopefully I’ll have put together a more reliable solution that can detect any reflexive request automatically, but that looks like it will require changes in GeoTools.

···

On 5 March 2015 at 01:02, emmexx <emmexx@anonymised.com> wrote:

Il 03/03/2015 09:16 PM, Jody Garnett scrisse:

As per other email, please add your experience to
http://jira.codehaus.org/browse/GEOS-6059 .

I did it.

Some quick fixes:

  • If you are on windows ensure that your hosts file is configured
    correctly (for any tests involving localhost)
  • If you are hiding behind a proxy be sure to adjust the base url setting

The common thread here is that GeoServer needs to be able to “detect”
when Transaction request document references a schema defined by
DescribeFeatureType. It needs to be sure to resolve that “internally”
rather than via HTTP.

I undestand what you mean but I’m not sure how can I practically
accomplish that.
I use an AWS AMI Linux server and I don’t use a proxy, but the aws
network has his own quirks, I can’t change settings at will.
If I understand correctly geoserver reads the client requests and if
there’s the server address in it, it can’t match it to the server
address where it is running.
The hostname of the aws server is different from the public dns name, so
I can’t change it.
Can I change some other setting in the server or in geoserver?

Thank you
maxx

Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/

Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

–

Kevin Smith

Software Engineer | Boundless

ksmith@anonymised.com

+1-778-785-7459

@boundlessgeo

http://boundlessgeo.com/

15

Il 03/05/2015 07:22 PM, Kevin Smith scrisse:

I've got a patch put together that allows additional reflexive hostnames
to be specified via a system property. It's a workaround rather than a
solution but it might help you.

I tried to use your workaround and I have some questions.
Should I ask them here, on the development list or on jira.

Thank you

   maxx

16

Il 03/05/2015 07:22 PM, Kevin Smith scrisse:

I've got a patch put together that allows additional reflexive hostnames
to be specified via a system property. It's a workaround rather than a
solution but it might help you.

I installed the latest master but I wonder if all my problems came from my failure to undestand the suggestions given here or on jira about the proxy settings.

I didn't understand there's such a parameter in the global settings so I always let it blank.

Now I put the public url of the aws server in Proxy Base URL and all problems disappeared. No wfs locking, no editing problems on commit.
I tried on a test server using the latest master.

What I'd like to know is if everything is solved because of the patch or because I set Proxy Base URL or both.
I need to know that before modifying/upgrading my production server.

Thank you
  maxx

17

Il 03/13/2015 11:32 AM, emmexx scrisse:

What I'd like to know is if everything is solved because of the patch or
because I set Proxy Base URL or both.
I need to know that before modifying/upgrading my production server.

FYI

I tried to set the Proxy Base URL global parameter on my production server (2.6) but it did not work out.

So I dumped my postgresql db and restored it on another AWS server where I installed geoserver master.
Everything works as expected, the only difference is that with Proxy Base URL set updating is faster (2 features are updated almost instantly, without proxy base 4-5 seconds).

bye
  maxx

18

I have the latest Geoserver 2.7.2 and latest Qgis at the time of my writing
2.10.1-Pisa

this worked for me

in geoserver admin global settings

add a proxy base url to be base url of your geoserver i used

http://localhost:8080/geoserver

save the details

suddenly no more errors from QGIS all working

--
View this message in context: http://osgeo-org.1560.x6.nabble.com/Problem-with-QGis-and-WFS-T-tp5182677p5224221.html
Sent from the GeoServer - User mailing list archive at Nabble.com.