不具合
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 Support アプリのダウンロード