AnsweredAssumed Answered

Input Connector's getting stuck after a database lock

Question asked by nkoski_mnpower on Feb 1, 2019
Latest reply on Feb 5, 2019 by nkoski_mnpower

We have a table on our ORACLE database, named Order_Updates, which Geoevent is querying on a 1 minute interval using the "Poll an ArcGIS Server for Features." The table is inside of a feature service which is hosted on the GeoEvent's ArcGIS Server, so on the localhost, and it deletes the rows after it finishes its query.


The problem is that every night, at 8pm, our database does a Reconcile batch job to move all the updates from that day from Common to Default, which puts a lock on all the tables and features in that database. And every night after 8pm Geoevent is unable to query the table giving this error:



Error while retrieving features from service Cust_Order_Data. Error: Error accessing data store at https://localhost:6443/arcgis/. : 400 : Unable to complete operation..


This continues to appear until exactly midnight, which after the server seems to have no issues performing the input connector's query. I can help aid this process by manually restarting the input connector after which the connections are fine. I am thinking the reason why it works after midnight is that midnight is when Geoevent is set to do its daily backup, and something in that is effectively restarting the connector.


I understand that during the 5-10 minutes that the batch job is running, and the lock is placed on the table, that GeoEvent and the feature service will be unable to access it, but why is it that after the batch completes and the lock is removed that it does not automatically restore its connections? Is there some type of behavior with Feature Services that might cause this, or is it a GeoEvent problem?


Any input would be amazing because I cannot find any info online regarding this behavior. Right now, if we disable the batch job, the Connectors remain active, but that is not a long term solution.