Multiple issues and deadlocks with WFS

[qgib]

Author Name: Alessandro Pasotti (@elpaso)
Original Redmine Issue: 21441
Affected QGIS version: 3.7(master)
Redmine category:web_services_clients/wfs
Assignee: Nyall Dawson

---

I've tested several scenarios and they all works fine and fast with QGIS 2.18.

to reproduce:

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

Issues:

• 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.

---

Related issue(s): #27626 (relates)
Redmine related issue(s): 19801

---

[qgib]

Author Name: Alessandro Pasotti (@elpaso)

---

btw, 3.4 has the same issues

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

I can confirm that WFS works in a very inconsistent way now on 3.4.5 and above.

---

• priority_id was changed from Normal to High

[qgib]

Author Name: Jacob Madsen (Jacob Madsen)

---

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.

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

• relates was configured as WFS not working at all #27626

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

see also #27626

[qgib]

Author Name: Giovanni Manghi (@gioman)

---

We made some test with a service (mapserver is the backend) that do not need authentication.
The real difference seems depends on the "enable paging" option, if not used things seems to work as expected.

[qgib]

Author Name: Nyall Dawson (@nyalldawson)

---

Caused by 0addae5 - changing READ_BUFFER_SIZE_HINT to 0 (unlimited) fixes the issue (likely at resurrecting the original issue fixed by that commit (which I can't track -- it has the incorrect issue number of #11930, I suspect there's a missing digit here).

[qgib]

Author Name: Nyall Dawson (@nyalldawson)

---

• assigned_to_id was configured as Nyall Dawson

[qgib]

Author Name: Alessandro Pasotti (@elpaso)

---

I can confirm that reverting 0addae5 fixes this issue.