Details
-
Bug
-
Status: Resolved
-
Resolution: Duplicate
-
None
-
None
-
None
-
Operating System: All
Platform: All
-
5237
Description
If a netconf mountpoint transaction is submitted and application needs to start subsequent transaction, the only way to do it is from a callback to submit future.
However application callback might be invoked before internal callback in sal-netconf-connector, which invokes unlock RPC. There's no guaranteed ordering. That's why sal-netconf-connector needs to invoke unlock before applications have a chance to start next transaction.
Attachments
Issue Links
- is duplicated by
-
NETCONF-141 Unlock transaction right after it's committed
- Resolved