N A M I N G  

Chapter  

4 

4. Naming 

How to find your Objects in JBoss by Scott Stark 

JBoss provides an implementation of the 1.2.1 Java Naming and Directory Interface (JNDI) 

in the JBossNS module. Configuration of the JBossNS service is done through the attributes 

of the org.jboss.naming.NamingService MBean. The configurable attributes for the 

NamingService are as follows: 

Port: The jnp protocol listening port for the NamingService. If not specified default is 

1099, the same as the RMI registry default port. 

RmiPort: The RMI port on which the RMI Naming implementation will be exported. 

If not specified the default is 0 which means use any available port. 

BindAddress: the specific address the NamingService listens on. This can be used 

on a multi homed host for a java.net.ServerSocket that will only accept connect 

requests on one of its addresses. 

Backlog: The maximum queue length for incoming connection indications (a request 

to connect) is set to the backlog parameter. If a connection indication arrives when the 

queue is full, the connection is refused. 

ClientSocketFactory: An optional custom java.rmi.server.RMIClientSocketFactory 

implementation class name. If not specified the default RMIClientSocketFactory is 

used. 

ServerSocketFactory: An optional custom 

java.rmi.server.RMIServerSocketFactory implementation class name. If not specified 

the default RMIServerSocketFactory is used. 

JNPServerSocketFactory, An optional custom javax.net.ServerSocketFactory 

implementation class name. This is the factory for the ServerSocket used to bootstrap the 

download of the JBossNS Naming interface. If not specified the 

javax.net.ServerSocketFactory.getDefault() method value is used. 

34