[TSDR-9] TSDR inventory and poller thread are sleeping mode,after uninstallation of TSDR components Created: 08/Jun/15 Updated: 12/Feb/16 Resolved: 12/Feb/16 |
|
| Status: | Resolved |
| Project: | tsdr |
| Component/s: | General |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Vasanthan Balasubramaniyan | Assignee: | Sharon Aicler |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| External issue ID: | 3617 | ||||||||
| Description |
|
Environment: Problem: Step to Reproduce: Still you can see tsdr threads doesnot terminated.Waited morethan 10 minutes,doesn't terminated for this same. --Attached YourKit thread monitors (after Uninstall of TSDR components) Note: |
| Comments |
| Comment by Vasanthan Balasubramaniyan [ 08/Jun/15 ] |
|
Attachment TSDR_H2_Uninstall.jpg has been added with description: TSDR-H2-Uninstall thread |
| Comment by Vasanthan Balasubramaniyan [ 08/Jun/15 ] |
|
Attachment TSDR_HBase_Uninstall.jpg has been added with description: TSDR-Hbase Uninstall thread |
| Comment by Sharon Aicler [ 17/Jun/15 ] |
|
Added the shutdown method to the close method in the module + made sure there is no lag until the threads are shutdown. |
| Comment by Vasanthan Balasubramaniyan [ 22/Jun/15 ] |
|
Still issue visible on RC2 Build (both H2 & HBase Datastore) |
| Comment by Sharon Aicler [ 23/Jan/16 ] |
|
The callback "close" in the AutoClosable interface in the module is not being executed when the feature is uninstalled. This is a framework wide issue in ODL... |
| Comment by YuLing Chen [ 08/Feb/16 ] |
|
Today in my testing environment, I was able to both set and retrieve the polling interval from both snmp and openflow stas collector. The following are URLs for both snmp and OF stats collector: |
| Comment by yuling chen [ 12/Feb/16 ] |
|
There's an existing bug in config subsystem that causes the observed behavior. If that bug is fixed, this issue will be gone too. Therefore, this is a duplicate bug. |