[jboss-jira] [JBoss JIRA] Commented: (JBREM-730) JNDIDetector should use rebind() instead of bind() to add new local detection messages

[Ron Sigal (JIRA)]

    [ http://jira.jboss.com/jira/browse/JBREM-730?page=comments#action_12357556 ] 
            
Ron Sigal commented on JBREM-730:
---------------------------------

org.jboss.test.remoting.detection.jndi.startup.JNDIDetectorTestCase fails because it expects essentially immediate addition of the test server to the NetworkRegistry.  Doing a clean detection on the first heartbeat and then AbstractDetector.detect() on the second heartbeat delays the addition of the server to the NetworkRegistry.  The problem is solved by calling AbstractDetector.detect() during the same heartbeat as the clean detect.  The effect of the change is that now, when JNDIDetector starts, it does a clean detect on all of the servers it finds in the JNDI registry, and then adds the valid servers to the NetworkRegistry.

> JNDIDetector should use rebind() instead of bind() to add new local detection messages
> --------------------------------------------------------------------------------------
>
>                 Key: JBREM-730
>                 URL: http://jira.jboss.com/jira/browse/JBREM-730
>             Project: JBoss Remoting
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.4.0.Beta1 (Pinto)
>            Reporter: Ron Sigal
>         Assigned To: Ron Sigal
>             Fix For: 2.4.0.Beta1 (Pinto)
>
>
> Currently, JNDIDetector.registerDetectionMsg() is using javax.naming.Context.bind() to add a new local detection message to the JNDI server, which means it can't overwrite a detection message that already exists.  It should call Context.rebind() instead.

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