WFS responses are truncated at 16mb
|Reported by:||ksgeograf||Owned by:|
|Severity:||major||Keywords:||WFS Sheboygan 16777216 0x1000000 truncated xml GetFeature|
Attempting to read the Sheboygan parcels via WFS fails completely. The query string I used is this:
You may have to replace "TYPENAME" with the correct random namespace.
When the request is issued through a browser the mgserver.exe starts running at 100% CPU. After a little while the w3wp.exe start running instead, and consuming a large amount of memory. At some point the process starts sending the data, but truncated at 1677216 (0x1000000) bytes.
There are two problems here: 1) The data should not be character truncated, as that results in broken xml 2) The data should not be collected fully in each process, but rather streamed onto the client, resulting in less memory overhead and faster response times.
Change History (5)
comment:1 by , 12 years ago
|Component:||General → WFS Interface|
|Summary:||WFS is inefficient and breaks for largers datasets → WFS responses are truncated at 16mb|
|Version:||2.1.0 → 2.2.0|