Bug
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.
| Bug ID Number | BUG-000094475 |
|---|---|
| Submitted | February 26, 2016 |
| Last Modified | June 5, 2024 |
| Applies to | ArcGIS for Server |
| Version found | 10.3.1 |
| Status | Known Limit |
Additional Information
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.Steps to Reproduce
Bug ID: BUG-000094475
Software:
- ArcGIS for Server
Get notified when the status of a bug changes
Discover more on this topic
Search for related information
Find training related to this topic
Explore ideas and give feedback
Get help from ArcGIS experts
Download the Esri Support App