MapGuide FeatureReaders not being closed properly?

[jbirch]

There are a few cases where I believe an MgFeature is being opened and not being closed properly.

---

1) I believe that for:

trunk/layers/MapGuide/php/Query.php

There is an MgFeatureReader being opened on line 199 which is being closed on line 268.

However, on line 261, I believe that a second MgFeatureReader is being opened using the same variable name without closing the initial MgFeatureReader first, and that this second reader is never closed.

2) It looks to me that in the file

trunk/widgets/Search/Search.php

The MgFeatureReader called $features is only closed in the exception handling logic, not in the normal code stream.

3) In:

trunk/widgets/SelectWithin/SelectWithin.php

On line 109, it appears that an MgFeatureReader called $featureReader is opened but not closed.

---

I believe that these may be the (partial?) cause of a problem I am having with running out of connections.

[greenmapsanmiguel]

close feature readers in query.php and search.php

[pagameba]

thanks for the report and patches. I've applied the patch for search.php and a slightly modified version of the patch for query.php.

[jbirch]

The feature reader in SelectWithin widget still isn't closed.

[jbirch]

In query.php:

• the feature reader opened on line 199 will not be closed if an exception is thrown from the try on line 216
• the feature reader on line 256 is not closed (I think r1874 caused a regression here)

[pagameba]

ok, trying again and paying more attention to what I am doing (note this bug did not specifically mention SelectWithin but I will look at that one too).

[pagameba]

fixed in svn trunk. In query.php, the feature reader opened on line 199 will be closed after the catch statement on line 254. But the other problem is valid.

[jbirch]

Read point 3 in the initial ticket :) It wasn't fixed in the patch though.

[pagameba]

Opps, my bad! Fortunately I fixed the right one anyway :)