File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Sockets and Internet Protocols and the fly likes Does a custom RMISocketFactory made to use fixed server ports influence Naming.lookup call Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Java » Sockets and Internet Protocols
Bookmark "Does a custom RMISocketFactory made to use fixed server ports influence Naming.lookup call" Watch "Does a custom RMISocketFactory made to use fixed server ports influence Naming.lookup call" New topic
Author

Does a custom RMISocketFactory made to use fixed server ports influence Naming.lookup call

Som Bhattacharyya
Greenhorn

Joined: Dec 11, 2010
Posts: 5
i have a requirement to fix the server and client ports being used by our RMI app.
i understand that fixing the client port is a bad option as it would obviously cause performance issues.

So i am working on fixing the ports being used on the server side.
Till now i have created a custom RMI SocketFactory that uses a 10 port range(7000-7010) for working.
Now when i use the application i do see the range being used over the network.
However , apart from the ports defined in the CustomRMISocketFactory there are other ports that i still see in the network traces.

From the debug that i have done i see that these ports are being generated right after the Naming.lookup(<String>) call.
It is apparent that there would be one port used on the server side where the registy is running.(port 9011)
But i cannot understand what is causing the other ports being used.(These ports are randomly selected and keep changing).

Please do let me know if anyone can guide me in the correct path.

Thanks a lot !
Som
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Does a custom RMISocketFactory made to use fixed server ports influence Naming.lookup call
 
Similar Threads
Port Range for W.A.S. Communication
NX: network client access
RMI Testing
NX: RMI check available port or host number
NX: validation of the IP or HostName