It was AWS security groups. Bit me. AWS VLAN != Regular VLAN
On Fri, Mar 8, 2013 at 2:12 PM, Vince Stewart <stewart.vi...@gmail.com> wrote: > if this is a newly installed system with linux in each virtual machine, > make sure you have registered the IP address (192.168.x.x) in \etc\hosts > files. > > > On Sat, Mar 9, 2013 at 8:42 AM, Zippy Zeppoli <zippyzepp...@gmail.com>wrote: > >> So, I have a tomcat7 cluster on AWS with a cluster configuration that >> works on my local VirtualBox cluster. >> >> Specs: >> - Same config. >> - Firewall turned off on all hosts. >> - unicast instead of multicast >> >> the following commands time out: >> nc -zv member1 8080 >> nc -zv member1 4110 >> >> They are listening however: >> tcp 0 0 0.0.0.0:4110 0.0.0.0:* >> LISTEN >> tcp 0 0 0.0.0.0:8080 0.0.0.0:* >> LISTEN >> >> tcpdump shows over and over SYN's but no replies on all members: >> 18:57:23.762712 IP member1: 52548 > 192.168.10.10.g2tag: Flags [S], >> seq 215397535, win 14600, options [mss 1460,sackOK,TS val 159216257 >> ecr 0,nop,wscale 7], length 0 >> >> >> Connecting to any other port from one member to another works fine, >> for example ssh. >> >> So I can't figure out why network communication works between all >> hosts, tomcat is listening, but trying to connect to the listening >> port fails. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: users-h...@tomcat.apache.org >> >> > > > -- > Vince Stewart --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org