This is not fixed in trunk. Remoting configuration like host, port etc is now specific to the transport (see config). The old jndi server was assuming to use the same old host attribute for its own server (which no longer exists). The jndi server host/port config is now separate - we can't really assume that they're the same anyway. Also I renamed the "Main" bean to "JNDIServer" to make it clearer what it is. Since we allow system property substitution, the user could use ${host.name} (or whatever it is called these days) to use the same host value for jndi server and transport config if they wanted. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4173245#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...