BUG-000112027 for ArcGIS GeoEvent Server

Bug ID Number	BUG-000112027
Submitted	February 28, 2018
Last Modified	February 12, 2025
Applies to	ArcGIS GeoEvent Server
Version found	10.6
Operating System	Windows OS
Operating System Version	10.0
Status	Will Not Be Addressed

Additional Information

When re-configuring the nodes (e.g. inputs, outputs, filters, processors) participating in a GeoEvent Service - even for seemingly benign changes like renaming an input or output node - consider coping the input or output and making changes to the copy. Then, to incorporate the copy into the GeoEvent Service, edit the GeoEvent Service to remove the "old" node, insert the new node, and publish the changes. Event data will still be flowing while the service is being edited. Event processing will not be interrupted until the administrator clicks 'Publish' -- at which point all running instances of all nodes are destroyed, new instances are created, and new event routing flows are established between the newly created instances of each node. The destruction/construction of node instances occurs very quickly, but administrators should understand that there is some non-zero period of time, every time a GeoEvent Service is published, that the service is being rebuilt and event data which might be received by an input will not be processed. Event records received while a GeoEvent Service is being published will effectively be lost. As a best practice it is recommended that administrators do not delete inputs or outputs which are part of a currently running or configured GeoEvent Service. Doing so invalidates the service's topology. This is depicted in the GeoEvent Manager web application with a hollow red box replacing the missing (deleted) input or output. The topology error can be corrected by deleting the node displayed in red and publishing the changes to the GeoEvent Service. However, be aware that a service which was in an 'Error' state publishes to a 'Stopped' state. You will have to click to 'Start' the GeoEvent Service after publishing changes to fix topology errors introduced by when nodes which currently part of a service's configuration are deleted.

Workaround

Carrying out the standard workflow of either editing the original output connector or creating a new output connector with a different name, avoids this issue and allows the GeoEvent Service & output connector to work as intended.