Does a custom RMISocketFactory made to use fixed server ports influence Naming.lookup call
posted 4 years ago
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.