Forums Register Login

What is the second TCP port when using RMI?

+Pie Number of slices to send: Send
Hi guys,

I'm testing a RMI client/server application over the internet and I'm a bit confused about the ports (especially the second port) RMI is using...

I've got the following scenario:

The RMI server is on my root server with a public IP address without NATting. My client is behind a router at home. So far everything is working fine. The RMI registry on the server side is using the desired port i specified by creating the registry with the following command:


At the moment everything is working!!! The problem is that RMI opens up a second TCP port on the server side and this port seems to change anytime the server application is started. And these ports don't seem to be reserved ports for a special application (the last two times i had 2652 and 2317 for example). This is very unsatisfying because i have to change this second port on my firewall each time the server application is restarted

Unfortunately I couldn't find any useful hints on the web what exactly this second port does or is and in particular why it is changing dynamically! Can anyone tell me please what this port is and perhaps how I can specify a fixed number for it!

Thanks in advance!
Marco
+Pie Number of slices to send: Send
Now I've managed to figure out the problem by myself...

One TCP port is for the RMI registry and of course another one is needed for the actual RMI communication between server and client

I wasn't able to specify the port for RMI communication because my server implementation extended "UnicastRemoteObject".
Instead by using it's possible now to specify the desired port for RMI calls.

Just in case someone else experiences the same problems...

Marco
[ October 24, 2007: Message edited by: Marco Ehrentreich ]
Amateurs built google. Professionals built the titanic. We can't find the guy that built this tiny ad:
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com


reply
reply
This thread has been viewed 4229 times.
Similar Threads
Running RMI registry on ramdon port
question for mark
port details
NX: network client access
RMI registry service timeout
More...

All times above are in ranch (not your local) time.
The current ranch time is
Mar 28, 2024 05:22:07.