3 Replies Latest reply on Dec 10, 2007 2:29 PM by aidndev

    Not able to access web service via IP

    aidndev

      Hi,

      We are using JBoss-4.2.1.GA for deploying web services. When I access the web service using the GUI on local machine (localhost:8080 or IP:8080, both) it is working fine.

      But when I try to access the server using IP:8080/ from a remote machine (over the network), it is not working. I have put a sysout as the first line in the called method, and it is not getting printed on console. The browser shows the "looking up IP" in the status bar and then "Done", without any action, while there is no exception or anything on server console.

      I am using -b option to start the server.

      Can anybody help me with this?

        • 1. Re: Not able to access web service via IP
          jaikiran

          Are you able to ping the JBoss server using this IP from your remote machine? Also, does

          telnet xxx.xxx.xxx.xxx 1099


          where xxx.xxx.xxx.xxx is the IP of your JBoss server, work from the remote machine?

          And what is the exact command that you use to start JBoss?

          • 2. Re: Not able to access web service via IP
            aidndev

            I can see the JBoss console, and can see wsdl's for our webservices.

            I have added the following part to run.bat:

             -Djava.rmi.server.hostname=<External IP> -Djava.rmi.server.useLocalHostname=true
            

            because the server is behind router.

            1. If I call "run.bat" directly, it starts the webservices on localhost (127.0.0.1:8080).

            2. If I call "run.bat -b <Internal IP>", I can see JBoss console and wsdl's from remote machine, but cannot access any webservice methods.

            3. If I call "run.bat -b <Internal IP>", I get exception saying that the ports are already in use (they are not) and server does not start properly.

            Can you tell me what I am doing wrong?

            • 3. Re: Not able to access web service via IP
              aidndev

              Sorry, read the third point as "run.bat -b <External IP>".

              Also, all the results are from remote machine. It works fine on the server machine, even if I use external IP to connect to server using GUI.