camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stan Lewis <>
Subject Re: Probably stupid question about Camel MINA endpoint
Date Tue, 28 Jul 2009 18:28:01 GMT
Have you tried instead of the hostname?

On Tue, Jul 28, 2009 at 2:25 PM, Johnny2R<> wrote:
> OK, I got my HL7 listener application (Camel, MINA, HAPI, Spring) working
> nicely and today tried to deploy it on the live server. I was able to
> connect to it from an app on the server itself but not from elsewhere on the
> network, and I was left thinking it must be a firewall issue. But I'm
> wondering whether it may simply be an error in the URI, which I have defined
> thus:
>    <camel:camelContext>
>        <camel:endpoint id="hl7listener"
> uri="mina:tcp://localhost:8888?sync=true&amp;codec=hl7codec"/>
>    </camel:camelContext>
> Since returning to my office, I tried deploying the test app on a different
> server from the test client and ran into what is apparently the same problem
> as at the production site. However, replacing 'localhost' in the URI with
> the real address of the server machine means I can now connect to it. Am I
> right in now thinking that with 'localhost' in the URI, you can ONLY connect
> to it from the same machine? The only examples I've seen use 'localhost' so
> I hadn't really given it much thought. If this is the case, is there a way
> of specifying the URI which doesn't require me to 'hard code' the real
> server hostname in the applicationContext.xml? It surprises me if the above
> is the case, because in Tomcat, say, you never have to specify the actual
> server address in the config.
> --
> View this message in context:
> Sent from the Camel - Users mailing list archive at

View raw message