laptop and a wrench

Bogue

A single invalid GeoEvent sent to a feature service output prevents valid GeoEvents from updating the same feature service if data is submitted to the input connector as a batch.

Dernière publication: July 29, 2016 ArcGIS for Server
Numéro d’ID de bogue BUG-000094475
EnvoiFebruary 26, 2016
Dernière modificationJune 5, 2024
S’applique àArcGIS for Server
Version trouvée10.3.1
StatutKnown Limit

Informations supplémentaires

Both the 'Add a Feature' and the 'Update a Feature' GeoEvent outputs provide a property 'Maximum Features Per Transaction'. Change this property value from its default of 500 to 1 if you want to ensure that a transactional failure will not affect more than one event (presumably the event which causes Server to reject the add/update feature request). This assumes that the number of events being sent each second is small enough to accommodate the increased overhead of limiting transactions with the feature service to exactly one event record in each transaction. This is around 50 events per second assuming a transaction latency of 20 milliseconds per transaction.

Étapes pour reproduire

ID de bogue: BUG-000094475

Logiciel:

  • ArcGIS for Server

Recevoir une notification lorsque le statut d’un bogue change

Télécharger l’application Esri Support

En savoir plus sur ce sujet

Esri Community

Rechercher des informations associées

Training

Rechercher une formation sur ce sujet

ArcGIS Ideas

Explorer des pistes et donner un avis

Obtenir de l’aide auprès des experts ArcGIS

Contacter le support technique

Télécharger l’application Esri Support

Accéder aux options de téléchargement