Win a copy of Murach's Python Programming this week in the Jython/Python forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic

Cannot bind remote object on port other that 1099  RSS feed

 
alex bv
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
On Win Nt, I first start the rmiregistry on a non-default port, for example
start rmiregistry 1522
Then I'm trying to bind a UnicastRemoteObject in the standard way, and I get a java.rmi.ConnectException: Connection refused to host. I do use the SecurityManager and grant all permissions etc.
This exception is actually the same one as what I get if I do not start the RMI registry at all, but in my case I've checked for listening on the specified port using netstat. If I use port 1099, everything works just fine. Anybody knows why that might happen??
 
Ken Krebs
Ranch Hand
Posts: 451
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Alex,
Welcome to JavaRanch. It would be easier to help if you post some of the code you're using to do the binding. To make it easier to read, bracket it in UBB "Code" code (see the buttons below the post data entry text area).
[ February 25, 2004: Message edited by: Ken Krebs ]
 
Chris Shepherd
Ranch Hand
Posts: 286
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
make sure you include the port number in your rebind and lookup statements. ALso check to make sure you don't have that port blocked for some reason.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!