camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: camel-netty and camel-mina refuse connections unless IP is specified
Date Wed, 27 Jul 2011 17:00:37 GMT

You should use instead of localhost. I think they even log a
WARN about this.

On Wed, Jul 27, 2011 at 6:06 PM, Taariq Levack <> wrote:
> Hi
> This is possibly by design either by camel or by netty/mina, since the
> behaviour is consistent between these similar components.
> Neither netty nor mina accept connections from remote network locations.
> The code works on my machine, but from outside I get 'Connection refused'.
> If I use a plain old java SocketServer, or even run Tomcat on the same
> port, then I can connect.
> While this won't work...
> from("mina:tcp://localhost:5130")
> ...if I specify the IP address instead of localhost then it works fine
> from everywhere.
> This proves that there is no firewall or other network problem
> preventing the client from connecting, the same client works when the
> server binds to a specific IP address.
> But I didn't expect to need to know the IP for a consumer, we don't
> have to do this for http-based components, and I thought it should
> consume wherever it runs like SocketServer does where you only provide
> the port.
> Its so close to production now that I will document it to work this
> way and of course pass the IP from the props file and make sure the
> server uses a static IP.
> Just wondering if this how stuff works.
> Taariq

Claus Ibsen
Twitter: davsclaus, fusenews
Author of Camel in Action:

View raw message