1 Reply Latest reply on Aug 1, 2003 11:54 PM by Wolfgang Helbig

    changing jndi port in 3.2.1

    Marko Friedemann Newbie

      Hi there. I want to update my running configuration of 3.2.0beta with 3.2.1.
      Now I faced a rather lethal problem right at the start, because I need to change the jnp naming port. Under 3.2.0beta this is working like this:

      ,-- 3.2.0beta conf/jboss-service.xml --
      | <mbean code="org.jboss.naming.NamingService"
      | name="jboss:service=Naming">
      | 1199
      |
      `-------------

      A snippet of the resulting log is attached.

      If, however, I do the same to jboss-3.2.1:
      ,-- 3.2.1 conf/jboss-service.xml --
      | <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. -->
      | 1199
      |
      `-------------

      I get the NamingService listening on 1199 alright, BUT each and every attempt to register something at the later deployment stages goes to localhost:1099! And of course failes because of that. See the snippet of the second log attached.

      I simply dont know where the heck that 1099 comes from, does anyone have a hint on that?

      SNy23