Hi Daniel. On Tue, Nov 20, 2012 at 1:55 PM, Daniel Mikusa <dmik...@vmware.com> wrote: > On Nov 20, 2012, at 5:53 AM, Stephen Nelson-Smith wrote: > I've encountered this with Tomcat clustering on CentOS in the past. Tomcat's > default configuration for the cluster receiver will automatically look up the > address to listen. It does this by calling > "java.net.InetAddress.getLocalHost().getHostAddress()" [1]. > > I can't remember exactly why this was failing for me on CentOS, but I'm > almost certain it was due to a problem with /etc/hosts. I'd suggest taking a > look at that file and making sure it contains the right entries.
Thanks for the validation - that's pretty much exactly where my deductions have led me. I didn't build these machines, so I can't speak for the validity of the config - will report. > Otherwise, you can override the default Tomcat setting for the cluster > receiver's address attribute, which is "auto" and specify the address > manually. That should workaround the problem. Thanks a lot! S. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
