Hi, I'm also effected by this bug. I get exactly the same error as eyck after I upgraded from Debian lenny (libapache2-mod-jk 1:1.2.26-2+lenny1) to sqeeze (libapache2-mod-jk 1:1.2.30-1).
My system is: Debian: 6.0 Kernel: 2.6.26-2-amd64 libc6: 2.11.2-10 apache2: 2.2.16-6 tomcat6: 6.0.28-9 The system is not running in any VM. Tomcat is still accessible from port 8080, but not via apache and mod_jk, although port 8009 is enabled in the servers.xml and # lsof -i -n | grep 8009 java 12870 tomcat6 245u IPv6 86597097 0t0 TCP *:8009 (LISTEN) tells me that it is listening on 8009 via IPv6. Since Nelson also mentioned that he could reproduce the problem with tomcat listening on an IPv6 socket, I'm wondering if the bug is IPv6 related. Here is my worker configuration: == /etc/libapache2-mod-jk/workers.properties == workers.tomcat_home=/usr/share/tomcat6 workers.java_home=/usr/lib/jvm/java-6-sun ps=/ worker.list=ajp13_worker worker.ajp13_worker.port=8009 worker.ajp13_worker.host=127.0.0.1 worker.ajp13_worker.type=ajp13 worker.ajp13_worker.lbfactor=1 worker.loadbalancer.type=lb worker.loadbalancer.balance_workers=ajp13_worker For now I'm going back to the lenny version. Regards, Stefan __ This is the maintainer address of Debian's Java team <http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers>. Please use debian-j...@lists.debian.org for discussions and questions.