Bug#572048: Happens on new installations, too

[Josef Spillner (kuarepoti-dju.net)]

The SocketException on port 8005 has hit me as well on a freshly
debootstrapped squeeze system with tomcat6 (6.0.24-2, amd64) added on top
of it.
The previous versions worked fine in their respective squeeze
environments. Given that the system is always produced automatically,
configuration changes can be ruled out. This behaviour of tomcat6 is thus
clearly a regression.

However, it doesn't seem to be the fault of packaging metadata because the
stock upstream version also fails to run with the same
issue and an additional NoRouteToHostException, despite the network being
fine. Perhaps it's a Java issue? (using openjdk-6-jre 6b17-1.7-1)