漏洞
ArcGIS GeoEvent Server Java Virtual Machine (JVM) processes do not release memory after deleting GeoFences.
| 漏洞 ID 编号 | BUG-000105758 |
|---|---|
| 已提交 | June 10, 2017 |
| 上次修改时间 | June 5, 2024 |
| 适用范围 | ArcGIS GeoEvent Server |
| 找到的版本 | 10.4.1 |
| 操作系统 | Windows OS |
| 操作系统版本 | 2012 R2 |
| 状态 | Known Limit |
附加信息
Operations which pull data records, like complete geometries, into memory are intensive. Java's memory management anticipates this sort of memory usage and its default is to not scale down a JVM immediately after garbage collection simply because a block of memory is not immediately needed. Dynamic scaling requires instantiating a completely new JVM instance and copying the running state of the current JVM into the new instantiation before destroying the old JVM. This activity is itself resource intensive and represents a potential disruption to real-time processing activities. Future releases of Java are anticipated to offer additional strategies for memory allocation and management, but it is unlikely ArcGIS GeoEvent Server will be refactored to leverage an aggressive Java memory allocation / deallocation strategy. Best practice recommendation are to use Java's -Xms / -Xmx settings to establish a fixed memory allocation and disable dynamic JVM scaling. Esri recommends system architects follow principles of resource isolation and deploy ArcGIS Enterprise components such that system resources can be dedicated to specific functions (e.g. responding to map/feature service requests, geoprocessing, maintaining large volumes of feature record sets 'hot' in memory for the spatiotemporal big data store, adapting and processing data at velocity in real-time, etc.)重现步骤
漏洞 ID: BUG-000105758
软件:
- ArcGIS GeoEvent Server
当漏洞状态发生变化时获得通知
发现关于本主题的更多内容
搜索相关信息
查找与此主题相关的培训
探索想法并提供反馈
获取来自 ArcGIS 专家的帮助
下载 Esri 支持应用程序