Asynchronous configuration of connectors through restconf failing due to No transaction found for session

When configuring netconf connectors with controller-config loopback connection through restconf asynchronously, the messages sent to the netconf server can interfere with each other.

Since a configuration consists of lock-edit-commit-unlock, if mulitple configurations are being sent asynchronously through one session the operations can interfere and 2 commits can be called after each other for example.
This results in a failure with "No transaction found for session ".