Netty Amazon Ec2

[Nicholas Hagen]

Wouldn't it be better to just bind to new InetSocketAddress(999) so that it accepts connections on any valid IP of the end device (ie: you can accept connections on both the elastic ip, localhost, and any other private IPs bound to that device).    That' s typically what I do.

Nick

=================================
Nicholas Hagen
Z|NET Development, LLC
www.znetdevelopment.com
=================================

On Nov 26, 2009, at 12:17 PM, manish_iitg wrote:

> 
> Hello,
> 
> I solved the problem. 
> 
> The problem was 
> 
> bootstrap.bind(new InetSocketAddress("127.0.0.1", 999)); in my server...
> 
> but actually it should bind to the private ip of the instance. in my case
> 
> 
> bootstrap.bind(new InetSocketAddress("10.210.xxx.xxx", 999)); 
> 
> 
> 
> 
> 
> manish_iitg wrote:
>> 
>> Hello,
>> 
>> Has any one deplyed netty based server on ec2. I am facing a problem that,
>> when i bind my netty based server on port 10001 it is not accessible from
>> another ec2 instance.  I know this is not a problem in netty, but of ec2
>> configuration but if anyone faced this problem before and solved it let me
>> know.
>> 
>> 
>> Thanks
>> Manish
>> 
> 
> -- 
> View this message in context: http://n2.nabble.com/Netty-Amazon-Ec2-tp4070802p4072231.html
> Sent from the Netty User Group mailing list archive at Nabble.com.
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-users