Ususally out of the box it's port 1099. In server.log if you look for 1099 or whatever port the jnp server is supposed to bind to you should see the address/location. Can you post the entire stacktrace for the error it throws at you? Off the top of my head it could be a binding problem - if you bind jboss to a particular domain, it'll generally only listen for that address. If it binds to 127.0.0.1, I think it'll bind to all addresses.
1099 didnt work. My machine has several jboss instances. My domain server starts like this:
And the configuration for port-01 in bindings-jboss-beans.xml is defined as follows:
<!-- The ports-01 bindings are obtained by taking the base bindings and adding 100 to each port value -->
<bean name="Ports01Bindings" class="org.jboss.services.binding.impl.ServiceBindingSet">
<!-- The name of the set -->
<!-- Default host name -->
<!-- The port offset -->
<!-- Set of bindings to which the "offset by X" approach can't be applied -->
Since the offset is changed to 1716, I thought the jndi port is 1099+1716=2815, but when I do the context lookup for 2815, it fails
If you go to jmx-console for the jboss instance you're running (using the correct ports offset by your bindings), the click on
1) the link "jboss" on the left hand side
2) then the link "service=Naming" on the right side of the page
It'll take you to the naming server configurations. Scroll down to the row named "Port" and you'll see "The listening port for the bootstrap JNP service. Set this to -1 to run the NamingService without the JNP invoker listening port." That row will tell you what port jnp is listening to.
Thanks antonio, I could figure out the problem....