id summary reporter owner description type status priority milestone component version severity resolution keywords cc external_id 1051 MapGuide exhausts FDO connections during Fusion selection jbirch trevorwekel "This problem was initially [http://n2.nabble.com/MapGuide-runs-out-of-FDO-connections-under-Fusion-MGOS-2.1-Beta-td3281668.html#a3281668 surfaced on the Users mailing list], and has been traced down a few false paths. ( #1039 , [/fusion/ticket/229 Fusion #229] ) After Andy's most [http://n2.nabble.com/FW%3A--mapguide-users--MapGuide-runs-out-of-FDO-connections-under-Fusion-MGOS-2.1-Beta-td3287689.html#a3336162 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... " defect closed high 2.1 Feature Service 2.1.0 blocker fixed greenmapsanmiguel jng tomfukushima brucedechant pagameba