...even increasing the log verbosity to ALL didn't helped. There's
still this huge gap completely undocumented in the logs.
So I think I have to go the thread dump road: unfortunately I don't
have idea about how to get thorough it.
Here's what I experimented with... I found three jsvc processes
ru
>> The interfaces are OK.
>
> The behavior indicates that may not be the case.
OK. But since I can ping them and the server answers promptly when
it's finally up - same for other servers bound to all the interfaces,
by the way: apache on the public interface, exim on localhost: all of
them works p
> From: Lucio Capuani [mailto:louis.capu...@gmail.com]
> Subject: Re: Same (virtual) machines, very different behaviour
>
> The interfaces are OK.
The behavior indicates that may not be the case.
> Moreover, Tomcat should only bind itself on
> 127.0.0.1, so no other int
Lucio Capuani wrote:
> Thank you for the tip.
> The interfaces are OK. Moreover, Tomcat should only bind itself on
> 127.0.0.1, so no other interface is involved. Anyhow, I can telnet
> tomcat on localhost at it's port 8009 after the socket is finally
> opened. I can also ping localhost
>
> I even
Thank you for the tip.
The interfaces are OK. Moreover, Tomcat should only bind itself on
127.0.0.1, so no other interface is involved. Anyhow, I can telnet
tomcat on localhost at it's port 8009 after the socket is finally
opened. I can also ping localhost
I even tcpdumped all the traffic occuring
Lucio Capuani wrote:
Hello everybody and thanks for caring.
I have an instance of Tomcat running into two Xen virtual machines.
I have cloned one of the two virtual machines and I changed the IP
address of the original.
Not saying that this is necessarily the cause, but are you 100% sure
