[mapguide-trac] #675: HttpServerConnection.RenderRuntimeMap() fails...

[MapGuide Open Source]

#675: HttpServerConnection.RenderRuntimeMap() fails...
---------------------+------------------------------------------------------
 Reporter:  MaksimS  |         Owner:  ksgeograf
     Type:  defect   |        Status:  new      
 Priority:  low      |     Milestone:           
Component:  Maestro  |       Version:           
 Severity:  major    |    Resolution:           
 Keywords:           |   External_id:           
---------------------+------------------------------------------------------
Comment (by MaksimS):

 Parameters are correct, I checked them multiple times.

 Deploying Fiddler gave me some insight into what's happening beneath, but
 didn't pinpoint the source of an error. The only thing that's really
 strange is that it actually never reaches GETMAPIMAGE operation -
 described exception is being thrown following series of GETRESOURCEDATA
 and GETRESOURCECONTENT ops. As per inspector, the last valid GET is:

 {{{
 GET
 /mapguide2009/mapagent/mapagent.fcgi?OPERATION=GETRESOURCEDATA&VERSION=1.0.0&SESSION=
 c3d9fba6-ffff-ffff-8000-
 00215a501f4d_en_7F0000010AF20AF10AF0&FORMAT=text%2fxml&LOCALE=en&RESOURCEID=Session%
 3ac3d9fba6-ffff-ffff-8000-
 00215a501f4d_en_7F0000010AF20AF10AF0%2f%2fPLAN.Map&DATANAME=LayerGroupData
 HTTP/1.1
 Host: proliant
 User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; SLCC1)
 }}}

 After that follows a POST:

 {{{
 POST /mapguide2009/mapagent/mapagent.fcgi HTTP/1.1
 Content-Type: multipart/form-data;
 boundary=---------------------8cad4b5fc35d432
 Host: proliant
 Content-Length: 1236
 Expect: 100-continue
 User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0; SLCC1)
 }}}

 ... and I see no POST parameters anywhere (?). That's the point where
 exception is being thrown.


 One thing I noticed, though - while getting RuntimeMap object
 DESCRIBEFEATURESCHEMA operation is being issued (data requested) multiple
 times, although it returns just the very same named feature source schema.
 Named schemas should be internally cached in memory on Meastro API side,
 there's really no need to request for it's contents multiple times during
 a single session (i.e. DESCRIBEFEATURESCHEMA returns 104 KB of data in my
 case).

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