Can't access Jetty endpoint deployed on remote JBoss Fuse ESB

[ksimpson]

Scenario:

     - JBoss Fuse ESB installed on remote RHEL6 VM, with no firewall and all ports open

     - Installed bundle with Camel routes, including a Jetty acceptor endpoint (i.e. used in a Camel 'from(...)')

          - Jetty endpoint is configured with the uri --> jetty:http://0.0.0.0/foo/FooService

After dropping bundle in ESB_HOME/deploy, the Camel context starts the routes successfully.  I can curl the Jetty endpoint from that machine and get a response, but trying to curl or soapui invoke from my local desktop hangs and then fails with ConnectionTimeOut errors.

How can Jetty endpoint be exposed remotely when there's no firewall and all ports are open (per 'iptables')?

Thanks in advance,

Kevan

[ffang]

Hi,

0.0.0.0 should bind all available network interface on your remote machine, but from your description, somehow it only bind to localhost|127.0.0.1 so only accessible from local machine, could you use

jetty:http://external.ip.address/foo/FooService

instead to see if it helps?

Also, you can try to access other network service(for example start a tomcat on remote machine and see if you can access it from your local machine) from that remote machine to see if it works, this can determine if your DNS correct or if there's really no firewall between them.

Freeman

[ksimpson]

Thanks for the quick response!  I tried deploying an updated bundle using the IP I get from pinging the VM's DNS from my desktop machine, but no luck.  Not sure the correct way to obtain a public IP, so I curl'd whatismyip-dot-com from the VM and read the HTML response.  That IP is different, but I can't even ping that IP.

I downloaded and started Tomcat 7 but I can't access that remotely either.  I even tried disabling my local firewall (window$) and still no connection.

I can try flushing the iptables, but otherwise not sure what else I can do.  Suggestions?

UPDATE:  After flushing the iptables, I was able to access the deployed bundle's service.  From that, I'll conclude that the ports must be opened with updated iptable configuration.  I will mark this post as answered.