tell me what controls the
config for IPv6 here?
Thanks
Adam
Adam Hardy on 23/05/08 15:47, wrote:
No, on the box that doesn't work, I get this:
[EMAIL PROTECTED]:~$ sudo ping6 ::1
Password:
PING ::1(::1) 56 data bytes
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
, time 1001ms
?
On Thu, May 22, 2008 at 12:29 PM, Adam Hardy [EMAIL PROTECTED]
wrote:
Tell you the truth, I can only assume IPv6 stuff is configured to the
debian etch defaults - although that might have changed between the date I
installed the no-pause-box and the date I installed the problem
Lists on 19/05/08 22:17, wrote:
just do two thread dumps during the freeze
kill -3 tomcat process id
sleep 5
kill -3 tomcat process id
the thread dump will identify where it is hanging, and it gets output to
std.out, by default to catalina.out
Filip
Adam Hardy wrote:
I've been trying to solve
) = 0
Jim Cox on 22/05/08 11:23, wrote:
I'd think it's more likely to be timing out while resolving a hostname via
DNS, but starting tomcat via strace should show you exactly where it is
pausing.
On Thu, May 22, 2008 at 5:08 AM, Adam Hardy [EMAIL PROTECTED]
wrote:
I'm still frustrated
you don't see
the pause? I wonder if it's a difference in IPv4/IPv6 configuration between
the boxes...
On Thu, May 22, 2008 at 8:24 AM, Adam Hardy [EMAIL PROTECTED]
wrote:
Found it! But I think my knowledge of linux system calls and kernel
functions is letting me down now. Presumably that is port
loopback address (?) which
times out, but the corresponding line from the no-pause box seems to do
the same without delay. Do you have IPv6 enabled on both boxes, i.e. does
the output from /sbin/ifconfig -a look similar?
On Thu, May 22, 2008 at 8:52 AM, Adam Hardy [EMAIL PROTECTED]
wrote:
I think
I've been trying to solve this problem for a couple of hours now and I can't see
any solution on google or in the archives.
I have tomcat 6.0.13 and java 1.5.0_12 running on debian linux 2.6, my own
installation, not the debian packages.
I stripped the tomcat config down to the bare minimum,
dump will identify where it is hanging, and it gets output to
std.out, by default to catalina.out
Filip
Adam Hardy wrote:
I've been trying to solve this problem for a couple of hours now and I
can't see any solution on google or in the archives.
I have tomcat 6.0.13 and java 1.5.0_12 running
