<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 19:52:51 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>OpenDaylight JIRA</title>
    <link>https://jira.opendaylight.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.20.10</version>
        <build-number>820010</build-number>
        <build-date>22-06-2022</build-date>
    </build-info>


<item>
            <title>[CONTROLLER-370] Handle uncaught exceptions from Clustering Services in HostTracker</title>
                <link>https://jira.opendaylight.org/browse/CONTROLLER-370</link>
                <project id="10113" key="CONTROLLER">controller</project>
                    <description>&lt;p&gt;Handle uncaught exceptions from Clustering Services in HostTracker&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: Mac OS&lt;br/&gt;
Platform: PC&lt;/p&gt;</environment>
        <key id="24924">CONTROLLER-370</key>
            <summary>Handle uncaught exceptions from Clustering Services in HostTracker</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                                <status id="5" iconUrl="https://jira.opendaylight.org/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10001">Won&apos;t Do</resolution>
                                        <assignee username="mark.mozolewski@hp.com">Mark Mozolewski</assignee>
                                    <reporter username="yisye@cisco.com">Jason Ye</reporter>
                        <labels>
                    </labels>
                <created>Tue, 22 Apr 2014 18:19:45 +0000</created>
                <updated>Mon, 4 May 2015 23:54:44 +0000</updated>
                            <resolved>Mon, 4 May 2015 23:54:44 +0000</resolved>
                                    <version>0.4.0</version>
                                                    <component>adsal</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="48111" author="yisye@cisco.com" created="Tue, 22 Apr 2014 18:22:47 +0000"  >&lt;p&gt;There are couple of timer tasks in host tracker which use caches&lt;br/&gt;
provided by clustening services. If a container is deleted, then&lt;br/&gt;
the cache allocated to that container is also removed. Although&lt;br/&gt;
TimerTasks do get cancelled when container is deleted, but if it&lt;br/&gt;
happens during the execution of timer thread, then the task will&lt;br/&gt;
run to completion (even though it was cancelled) and may try to&lt;br/&gt;
access a cache which has already been deallocated.&lt;br/&gt;
The accessing of this deallocated cache will result in clustering&lt;br/&gt;
service exception which needs to be handled by timer tasks&lt;br/&gt;
Also adding toString methods to IPHostId and IPMacHostId for more&lt;br/&gt;
readable output when diplaying hosttracker data structures&lt;/p&gt;</comment>
                            <comment id="48112" author="mark.mozolewski@hp.com" created="Fri, 6 Feb 2015 20:02:17 +0000"  >&lt;p&gt;Jason, Since your issue was reported 10 months ago and considering the push to migrate services to MD-SAL can you comment:&lt;br/&gt;
1) Are you still focused on AD-SAL development/usage?&lt;br/&gt;
2) What severity this issue is for you today.&lt;/p&gt;


&lt;p&gt;If I don&apos;t hear back in 1 week (by 2/13/15) I will close this issue given ODL is focusing on AD-SAL development. Of course feel free to re-open it if you do not respond till after that time.&lt;/p&gt;</comment>
                            <comment id="48113" author="mark.mozolewski@hp.com" created="Thu, 12 Feb 2015 17:01:25 +0000"  >&lt;p&gt;Closing for now till feedback is received (see Comment #2)&lt;/p&gt;</comment>
                            <comment id="48114" author="carolsand@gmail.com" created="Mon, 4 May 2015 23:54:44 +0000"  >&lt;p&gt;This bug is part of the project to Move all ADSAL associated component bugs to ADSAL&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_11400" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10208" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>External issue ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>814</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10201" key="com.atlassian.jira.plugin.system.customfieldtypes:url">
                        <customfieldname>External issue URL</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[https://bugs.opendaylight.org/show_bug.cgi?id=814]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i02jzb:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>