MapServerIdentifyResults is ignoring the MaxRecordCount set in the map service config file. This works fine when the connection is through DCOM.
上次发布: August 25, 2014No Product Found
漏洞 ID 编号
NIM007675
已提交
March 28, 2007
上次修改时间
June 5, 2024
适用范围
No Product Found
找到的版本
9.2
修正版本
9.3
状态
Fixed
此漏洞已得到修复。 有关详细信息,请参阅“版本修复”和“其他信息”(如果适用)。
解决办法
The bug happens because we have a logic to test for esriIdentifyTopmost.esriIdentifyTopmost inherently means that we are really interested in the top most layer only.When we do the identify operation, we shall loop through all layers to exact all find results. However, if it is only the topmost layer that we are interested in, after collecting result for the first layer, we could just stop identifying.However, we test the top layer condition prior to testing whether the maxRecordCount has been reached. Hence in a situation where only we are interested in the topmost layer and there are more than maxRecordCount number of records there, the testing of maxRecordCount part is ignored.