[Smartfrog-checkins] [Smartfrog.org-JIRA] Resolved: (SFOS-302) Anubis comms transport threads do not terminate correctly

[Paul M. (JIRA) <ji...@sm...>]

     [ http://jira.smartfrog.org/jira/browse/SFOS-302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Murray resolved SFOS-302.
------------------------------

    Resolution: Fixed

The termiantion sequence was not completing due to a bug in the IntervalExec code. A notify() was being called outside a synchronized block causing an IllegalMonitorStateException to be thrown. This exception was being caught by SmartFrog in terminateNotifying() and logged at IGNORE level, so there was no indication that anything was going wrong (see SFOS-926 about logging at IGNORE level).

This bug has been fixed. Also reviewed all termination code for threads and found that the non-blocking coms code didn't have any termination code. Fixed that too. 

Changed thread names to common format as part of the cleanup.

> Anubis comms transport threads do not terminate correctly
> ---------------------------------------------------------
>
>                 Key: SFOS-302
>                 URL: http://jira.smartfrog.org/jira/browse/SFOS-302
>             Project: SmartFrog
>          Issue Type: Bug
>          Components: _service_Anubis
>            Reporter: Paul Murray
>            Assignee: Paul Murray
>            Priority: Minor
>
> When the Anubis components are terminated the threads running the communication transport are left hanging around inactive. Need to go over termination and fix. 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.smartfrog.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira