0 Replies Latest reply on Feb 16, 2006 2:20 PM by tomson

    Configuring RmiPort of Naming service leads to the creation

    tomson

      Hi,
      I am using JBoss 3.0.1 and our Jboss is working behind a firewall. As per our security specs, any anonymous ports need to be made listening on constant port numbers. While I configured RmiPort of naming service to a static value, the naming service stub is exported with the new configured port (2021), but I observed that another dynamic port is getting created by the JBoss process and even could not make out a trace of this port. I think this port may be created by some JNDI proxy process. Not sure...

      Below is the snippet, done for configuring RmiPort.

      <.mbean code="org.jboss.naming.NamingService"
      name="jboss:service=Naming">
      <!-- The listening port for the bootstrap JNP service. Set this to -1
      to run the NamingService without the JNP invoker listening port.
      -->
      <.attribute name="Port">2020</attribute.>
      <.attribute name="RmiPort">2021</attribute.>
      </mbean.>
      Can any one please give some light on how to disable it or make it a static port.

      Pls help with any clues.....
      Thnx in advance
      Tomson