1 Reply Latest reply on May 20, 2005 12:09 AM by Scott Stark

    4.0.2 J2EE Remote Clients JNPing over 1099 Getting HA'd by t

    xavierpayne2 Newbie

      We recently upgraded from JBoss 4.0.1AS to 4.0.2AS and I believe we came across a bug.

      I have triple checked that we have all the correct jars in our remote j2ee clients classpath but for some reason the JBoss clustering dispatcher seems to be HA'ing JNP calls using 1099. According to the docs and the behavior of 4.0.1 I though client calls were only supposed to be HA'd if jnp port 1100 is used.

      The situation is this... We have several jboss 4.0.2 servers on the same subnet running the "all" configuration. The jboss cluster service has its "bind_addr" attribute set to localhost.

      In my clients I can provide a jnp that is total garbage like "jnp://AS3q43qw:1099

      and successfully hit one of the servers.

      As a work around I have added the following to the environment of my clients InitialContext:

      ("jnp.disableDiscovery", "true")

      Is this a bug or has the default behavoir of 1099 intentionaly changed?