logs.tar
|
Duplicate |
|||
| duplicates |
|
DOMForwardedWriteTransaction infinite... | Resolved |
[MDSAL-79] Controller stop fails Created: 16/Apr/15 Updated: 09/Mar/18 Resolved: 23/Feb/18 |
|
| Status: | Resolved |
| Project: | mdsal |
| Component/s: | DOM runtime |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Abhishek Kumar | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Attachments: |
logs.tar
|
||||||||
| Issue Links: |
|
||||||||
| External issue ID: | 3007 | ||||||||
| Description |
|
Started controller and installed netconf connector and BGP features. Left controller running for a few min then tried to stop. It didnt stop. Left it in this state over-night. The process was still up next day. Analysis of thread dumps reveals that DOMForwardedWriteTransaction.cancel() never returns. do { Future is always null, hence this call never returns. Thread dumps and logs are attached. |
| Comments |
| Comment by Abhishek Kumar [ 16/Apr/15 ] |
|
Attachment logs.tar has been added with description: Log and thread dumps |
| Comment by Robert Varga [ 27/Oct/16 ] |
|
Is this still repreducible with Boron/Carbon? |