Bug report #21441
Multiple issues and deadlocks with WFS
|Category:||Web Services clients/WFS|
|Affected QGIS version:||3.7(master)||Regression?:||Yes|
|Operating System:||Easy fix?:||No|
|Pull Request or Patch supplied:||No||Resolution:|
|Crashes QGIS or corrupts data:||No||Copied to github as #:||29258|
I've tested several scenarios and they all works fine and fast with QGIS 2.18.
git checkout https://github.com/elpaso/qgis3-server-vagrant.git cd qgis3-server-vagrant vagrant up
There is a configured project in the resource/qgis folder: https://github.com/elpaso/qgis3-server-vagrant/tree/master/resources/qgis
- Timeout when loading the features layer "world" with all deployment methods (apache 8081, ngix 8080 and wgsi 8082), tested with ab concurrent and got no issues at all: fast and reliable
- Partial download of the features
- The a.m. vagrant has a HTTP Basic auth configuration username=username and password=password, but I tested also a configuration without HTTP auth and the issues are still there.
I've also observed deadlock in qgswfsrequest.cpp line 206 - waitCondition.wait( &waitConditionMutex ); when opening another WFS from metasearch catalog window.
#3 Updated by Jacob Madsen 9 months ago
Giovanni Manghi wrote:
I can confirm that WFS works in a very inconsistent way now on 3.4.5 and above.
I can confirm these issues as well. I've had to stick with QGIS 2.x so far, because since QGIS 3.0 WFS in QGIS is next to unusable. I really hope these issues can be fixed soon. I can confirm that these issues are not present in QGIS 2.18.