[jboss-jira] [JBoss JIRA] Updated: (JBCOMMON-10) org.jboss.net.sockets.DefaultSocketFactory does not consider bindAddress in equality/hashCode

Scott M Stark (JIRA) jira-events at jboss.com
Sun Sep 24 08:27:01 EDT 2006


     [ http://jira.jboss.com/jira/browse/JBCOMMON-10?page=all ]

Scott M Stark updated JBCOMMON-10:
----------------------------------

    Affects Version/s: 2.0.0.GA
                       1.0.0.CR1
                           (was: 1.0.0.GA)

> org.jboss.net.sockets.DefaultSocketFactory does not consider bindAddress in equality/hashCode
> ---------------------------------------------------------------------------------------------
>
>                 Key: JBCOMMON-10
>                 URL: http://jira.jboss.com/jira/browse/JBCOMMON-10
>             Project: JBoss Common
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 2.0.0.GA, 1.0.0.CR1
>            Reporter: Scott M Stark
>         Assigned To: Scott M Stark
>             Fix For: 1.0.0.GA, 2.0.1.GA
>
>
> At least the sun rmi implementation decides on creation of a listening port based on uniqueness of the server socket factory associated with the stub. The org.jboss.net.sockets.DefaultSocketFactory is not considering the bindAddress setting, and so it cannot be used to export the same object multiple times on different interfaces. The DefaultSocketFactory needs to consider the bindAddress in equals and hashCode.

-- 
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

        



More information about the jboss-jira mailing list