MapGuide exhausts FDO connections during Fusion selection
|Reported by:||jbirch||Owned by:||trevorwekel|
|Cc:||greenmapsanmiguel, jng, tomfukushima, brucedechant, pagameba||External ID:|
After Andy's most recent email to the -internals list I spent some time trying to figure this out. I'd like to confirm that it was pretty easy for me to duplicate this problem in my environment:
- Edit serverconfig.ini, setting DataConnectionPoolSize to 20
- Restart MapGuide
- Zoom in and start selecting
When I reach some small number of selections (15-20), no further operations work.
This is REALLY bizarre that the DataConnectionPoolSize affects this problem because I have the SDF provided excluded from connection pooling. (same as Andy indicated).
Just to try my hunch, I went through and changed all of my Fusion app's:
$map = new MgMap(); $map->Create($resourceService, $resourceID, $mapTitle); $map = new MgMap(); $map->Open($resourceService, $mapName); $map->Save($resourceService);
to the newer:
$map = new MgMap($siteConnection); $map->Create($resourceID, $mapTitle); $map = new MgMap($siteConnection); $map->Open($mapName); $map->Save();
This had absolutely no effect on the problem. So much for hunches.
I'm convinced that it's a problem inside of MapGuide that Fusion just happens to be exercising with its different selection methodology. I am also convinced that this is a regression; the exact same map and application running on a 2.0.x server do not exhibit this behaviour.
This is going to be a HUGE issue for anyone using Fusion. I'm at the end of things I can do to investigate this; I think it needs some internal uber-coder attention...