Which OS do you use? The ejb3 connector component of JBoss seems to have a bug of ignoring the '-b 0.0.0.0' option. Instead of '0.0.0.0', it tries to choose one (maybe the primary one?) from the IP addresses bound to the machine's network interfaces. And if it cannot find any valid IP address, it uses 127.0.0.1 (and its default port 3873).
That said, if you are running the JBoss server on Windows, you need to make sure that the machine is connected to the network and has an IP address BEFORE you start JBoss server (As far as I know, Windows by default remove IP address from the network interface when it is not connected to the network). Otherwise, you are likely to get the error in the following scenario. 1) You start JBoss server with '-b 0.0.0.0' option when the Windows machine is not connected to the network and does not have an IP address other than 127.0.0.1. 2) The EJB3 connector component chooses '127.0.0.1' and listens at '127.0.0.1:3873'. 3) Then you connect the Windows machine to the network to test EJB3 remote client. Now the machine gets an IP address, which is too late for the JBoss EJB3 component. 4) Your EJB3 remote client receives from the server '127.0.0.1:3873' as an entry point, to which it tries to connect. But, since there is no JBoss server running at 127.0.0.1 (the localhost for the client), you get the error which you described in your post. Hope this helps. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4146208#4146208 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4146208 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
