2 Replies Latest reply on Jun 21, 2012 1:47 PM by arch9745

    problem connecting to jboss outside the virtual machine

    arch9745

      Hi,

      I have a windows 7 host system with vmware 8 and a guest system running oracle linux release 6 update 2 for x86_64 (64 bit). I installed JBoss-4.2.3.GA on the guest system. The install went though OK and the jboss page comes up fine inside the guest system. The problem is that it will not connect from anywhere outside the guest system.

       

      This is what was done:

      After installation, modified file /jboss-4.2.3.GA/server/default/deploy/jboss-web.deployer/server.xml
      <Connector port="8080" address="${jboss.bind.address}"
      changed to
      <Connector port="80" address="${192.168.1.62}"

       

      Started the jboss this way:
      /jboss-4.2.3.GA/bin/run.sh -c default -b 192.168.1.62

       

      The output shows that jboss starts and binds to the ip.

       

      On the guest system, access this and the jboss page comes up.
      http://192.168.1.62

       

      But doing this from outside the guest does not work. The jboss page does not come up.

       

      The guest system can ping the computers inside the network, and the other systems can ping the guest and host systems with no problems. The whole communication is inside the firewall, within the local network, so the firewall is not an issue here. We are using bridged networking with static ips for both the host and guest machines.

       

      Thanks to everyone who attempts to solve this.

        • 1. Re: problem connecting to jboss outside the virtual machine
          wdfink

          <Connector port="8080" address="${jboss.bind.address}"

          the ${...} is a expression and will be replaced.

          In your case ${jboss.bind.address} is replaced with 192.168.1.62 because of the -b start option.

          So change the port number but not the expression.

          • 2. Re: problem connecting to jboss outside the virtual machine
            arch9745

            Thanks for the reply. I did realize that was redundant, but did not seem to cause any harm. The problem turned out to be the  firewall built into Oracle Linux which I did not realize existed. The solution is to either turn off the firewall or open the needed ports. I opted to turn off the firewall like this:

             

            # /sbin/service iptables stop

            # chkconfig iptables off