0 Replies Latest reply on Oct 7, 2005 3:15 PM by Ryan Thompson

    InvokerLocator port returned always seems to be default

    Ryan Thompson Newbie

      Being relatively new to JBoss, I am wondering if anyone has seen something similar and can set me right in either what I am doing, or if this might be a known issue. I have followed the numerous instructions on the web on how to get multiple servers running on the same machine. All seems well in that aspect. Server A is using the ports-default from the sample bindings file and Server B using ports-01. The only other configuration difference is the InvokerLocator port, 3873 for server A, and 3874 for Server B.

      The issue is when both are running and I try to invoke a method on Server B, it is invoked on Server A. Both servers have identical code deployed. The only difference is the java.naming.provider.url(included the ports) that is passed in, the Datasource used to connect to the DB, and the InvokerLocator port. They report listening on the expected NS ports, Server A being the default of 1099 and Server B being 1199. It almost seems like the InvokerLocator port always is returned as the default of 3873.

      If I start just Server B, I can list all the names, but If I try to invoke a method on a object after looking it up, I get a org.jboss.remoting.CannotConnectException

      Netstat -a shows the server listening on port 3874

      Am I wrong in assuming that the LocatorInvoker port is obtained from the server after a Context is created using the appropriate values for INTIAL_CONTEXT_FACTORY(org.jnp.interfaces.NamingContextFactory), PROVIDER_URL(localhost:1199 or jnp://localhost:1199 or jnp://127.0.0.1:1199, tried them all as well as my actual ip), and URL_PKG_PREFIXES(org.jboss.naming:org.jnp.interfaces)

      I also would like to know if there is a way to force this port on the client side.

      Any help would be greatly appreciated, we currently have a workaround by requiring a machine for each server, but that is not an optimal final solution. Thanks again.