Java's 'tnameserv' takes 3+ minutes to be “Ready”, why?

Question

I\'m trying to help a dev of an app I\'d like to use trouble shoot a problem utilizing Corba Server on Linux. I narrowed down the problem to tnameserv taking o

Answer 1

I found this using the google (LL Zamenhof's birthday today btw). I would turn on some wireshark tracing and see if you can see anything there. Though I would expect to see stuff in the strace if there was network activity. Too bad it's not open source.

Answer 2

Turns out the problem was a firewall issue. Wireshark didn't show anything useful because the firewall was dropping a certain packet. Although I looked at my firewall logs quite a few times to make sure this wasn't the case, turns out I wasn't looking in the right place. I overlooked the fact that this 'tnameserv' was IPv6 aware (as it was binding to :::23423) and a cursory glance of my firewall script showed that I was logging IPv6 related packets to a different location than my IPv4 packets. This was not an oversight but had to be done because ip6tables does not currently support the -j ULOG target.

Long story short, allowing loopback for IPv6 fixed the issue and 'tnameserv' returns "Ready" almost instantly.

Answer 3

Check your DNS-settings. You may time out waiting for an answer several times.