By using this website, you agree to our Terms of Use (click here)
Taking a stab in the dark here, but curious if anyone else has encountered this behavior.
We have an instance of Acumatica 2017 R2 (Build 17.210.0034) running, with a couple of SSIS packages that read from Acumatica OData feeds to populate a data warehouse. The job that runs these SSIS packages runs in the 2-3AM time frame every morning, and they use the official Microsoft OData Data Source connector (SQL 2016) to perform the query. We have a service account set up inside Acumatica to perform the queries.
The behavior we're seeing is that when the OData queries are made, the service account user registers a connection, and that connection persists even after the operation is complete (presumably until a TTL expires or timeout occurs). There's no provision that we're aware of to issue a formal "logout" command when dealing with OData, in order to close the connection.
Has anyone experienced similar behavior to this? Any tips on ensuring that OData connections don't linger?
Very interesting. I never considered this before. Just curious, where are you seeing the connections continuing to live, in SQL or in the Acumatica application?
I think you're going to need Engineering on this which means that you'll have to create a case with support.