Operating System: Mac OS
Platform: PC

There are couple of timer tasks in host tracker which use caches
provided by clustening services. If a container is deleted, then
the cache allocated to that container is also removed. Although
TimerTasks do get cancelled when container is deleted, but if it
happens during the execution of timer thread, then the task will
run to completion (even though it was cancelled) and may try to
access a cache which has already been deallocated.
The accessing of this deallocated cache will result in clustering
service exception which needs to be handled by timer tasks
Also adding toString methods to IPHostId and IPMacHostId for more
readable output when diplaying hosttracker data structures

Jason, Since your issue was reported 10 months ago and considering the push to migrate services to MD-SAL can you comment:
1) Are you still focused on AD-SAL development/usage?
2) What severity this issue is for you today.

If I don'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.

Closing for now till feedback is received (see Comment #2)

This bug is part of the project to Move all ADSAL associated component bugs to ADSAL