[NETCONF-515] Possible race condition in TxChain Created: 25/Feb/18 Updated: 25/Feb/18 Resolved: 25/Feb/18 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | Oxygen |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Medium |
| Reporter: | Anton Ivanov | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
closed and successfull most likely need to be guarded by a lock or at least declared volatile. This needs an inspection looking into how it is invoked to verify that it is necessary. |
| Comments |
| Comment by Anton Ivanov [ 25/Feb/18 ] |
|
Erroneously set as restconf, it is a netconf issue. The class in question is: ./netconf/sal-netconf-connector/src/main/java/org/opendaylight/netconf/sal/connect/netconf/sal/tx/TxChain.java |
| Comment by Tom Pantelis [ 25/Feb/18 ] |
|
They are guarded correctly as all the methods that access those fields are synchronized. |
| Comment by Anton Ivanov [ 25/Feb/18 ] |
|
We can close it. However, Jira does not allow me - it wants "check-in fix"
|