Hi jackie
Adding to the exclude list, does solve the problem, but the benefits (I
assume there must be) of having the connection pools are lost.
What I did instead was to add to the: DataConnectionPoolSizeCustom =
OSGeo.OGR:50
It seems that the somewhere in the system is an upper limit of open
Add the OGR provider to the DataConnectionPoolExcludedProviders setting in
serverconfig.ini
- Jackie
--
View this message in context:
http://osgeo-org.1560.n6.nabble.com/FDO-OGR-provider-stops-working-with-many-layers-tp4358864p4669906.html
Sent from the MapGuide Users mailing list archive at
That's the thing, the problem is both on MGOS2.2 and AIMS2012. perhaps the
issue belongs in the FDO forum then. It seems that the ORG provider does not
close files (perhaps to be able to access them quickly again), and that the
ORG provider then have some build in maximum or Windows has some
What about disabling connection pooling for the OGR provider?
Or what about splitting up the directory of TAB files into separate
directories?
- Jackie
--
View this message in context:
http://osgeo-org.1560.n6.nabble.com/FDO-OGR-provider-stops-working-with-many-layers-tp4358864p4639920.html
does it happen with both ajax and fusion viewers?
On Wed, Mar 21, 2012 at 8:00 PM, Jackie Ng jumpinjac...@gmail.com wrote:
What about disabling connection pooling for the OGR provider?
Or what about splitting up the directory of TAB files into separate
directories?
- Jackie
--
View this
Hi jackie
How do I disable connection pooling for the OGR provider?
The mapinfo files are already in a lot of different directories.
I made a small FDO test application. This is what the application do:
Loop trough all directories and files
for each *.TAB file
TRY
Open the file using FDO
I finally had some time to test this.
I have now tested on AIMS2012 and MGOS2.2. Both fail after about 100 to 180
layers in a map. It seems like some buffer/file handle problem since it
always fails at the same layer but if you delete a few layers from the map,
it fails at another layer.
MapInfo
given this occurs in AIMS2012, I would suggest raising this with
Autodesk Support
On Wed, Mar 21, 2012 at 12:56 AM, Hans Milling h...@geograf.dk wrote:
I finally had some time to test this.
I have now tested on AIMS2012 and MGOS2.2. Both fail after about 100 to 180
layers in a map. It seems
These are all MapInfo TAB files
Hans...
--
View this message in context:
http://osgeo-org.1560.n6.nabble.com/FDO-OGR-provider-stops-working-with-many-layers-tp4358864p4361824.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
___
On Fri, Feb 3, 2012 at 14:54, Hans Milling h...@geograf.dk wrote:
These are all MapInfo TAB files
I suggest you to try to launch the utility ogrinfo on each file .TAB
to see if OGR reports any error.
ogrinfo is an utility build on top of OGR lib that try to open the
file and reports some info
10 matches
Mail list logo
