[mapguide-trac] #1070: WFS responses are truncated at 16mb

[MapGuide Open Source]

#1070: WFS responses are truncated at 16mb
-----------------------------+----------------------------------------------
   Reporter:  ksgeograf      |       Owner:                                                           
       Type:  defect         |      Status:  new                                                      
   Priority:  medium         |   Milestone:                                                           
  Component:  WFS Interface  |     Version:  2.2.0                                                    
   Severity:  major          |    Keywords:  WFS Sheboygan 16777216 0x1000000 truncated xml GetFeature
External_id:                 |  
-----------------------------+----------------------------------------------

Comment(by jng):

 Some investigative notes.

 I think the problem starts
 [http://trac.osgeo.org/mapguide/browser/trunk/MgDev/Web/src/HttpHandler/HttpWfsGetFeature.cpp#L104
 here]

 It is funnelling the WFS response from the server Feature Service
 [http://trac.osgeo.org/mapguide/browser/trunk/MgDev/Web/src/HttpHandler/HttpWfsGetFeature.cpp#L279
 here] first to a string, then into an in-memory feature set

 That in-memory feature set is then funnelled in to a
 [http://trac.osgeo.org/mapguide/browser/trunk/MgDev/Web/src/HttpHandler/ResponseStream.h#L55
 MgHttpResponseStream], whose backing store is MgByte which had (until
 recently) a 16mb storage limit (now 64mb, but still a limit)

 There seems to be many in-memory projections of the original data before
 it reaches to the Apache/ISAPI response handler

 So a full read of Sheboygan Parcels is probably spiking the memory usage
 due to all these (possibly unnecessary) projections of data, with the
 truncation due to the size limit of MgByte that the response stream is
 using

-- 
Ticket URL: <http://trac.osgeo.org/mapguide/ticket/1070#comment:4>
MapGuide Open Source <http://mapguide.osgeo.org/>
MapGuide Open Source Internals