geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anita Kulshreshtha <>
Subject Re: svn commit: r527746 - in /geronimo/server/trunk: assemblies/geronimo-boilerplate-minimal/src/main/resources/var/config/ modules/geronimo-deploy-tool/src/main/java/org/apache/geronimo/deployment/ modules/geronimo-deploy-tool/src/main/java/org/apache/ger...
Date Thu, 12 Apr 2007 13:17:33 GMT

>  From our IRC conversation, it sounds like port 1099 needs to call to
> LocateRegistry.createRegistry(port)
> Assume the following server instances on the same box:
> Server instance A with RMIRegistryService port set to 1079
> Server instance B with RMIRegistryService port set to 1089
> Server instance C with RMIRegistryService port defaulted to 1099
> Server A is started. The server will start listening on port 1079,  
> but will also temporarily start a server socket on port 1099.
> Server C is started. The server will start listening on port 1099.
> Server B cannot start. It get's an error trying to bind to port 1099.
> Is that accurate?
    This is correct. This is why no instance can use a
RMIRegistryService port set to 1099. IIUC, 1099 must be available to
all instances to start a temporary server socket.

> As I mentioned earlier on IRC, I think we need to change the default 
> port back to 1099. We can then work on getting this problem
> resolved...

   I have reverted back to 1099 in rev 527918.


Need Mail bonding?
Go to the Yahoo! Mail Q&A for great tips from Yahoo! Answers users.

View raw message