Bug#561930: libcommons-dbcp-java: Connection pooling causes exception after change to net.ipv6.bindv6only
Alan Chandler
alan at chandlerfamily.org.uk
Mon Dec 21 10:47:36 UTC 2009
Package: libcommons-dbcp-java
Version: 1.3~svn828639-1
Severity: important
I am not sure it is this package this is at fault, and I have reported a similar bug against tomcat, but
since the change to /etc/sysctl.d to set net.ipv6.bindv6only=1 connection pooling caused an exception when
attempting to run a webapp which used it. I changed net.ipv6.bindv6only to 0 and the application started working
again
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (800, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.31-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages libcommons-dbcp-java depends on:
ii libcommons-collections-java 2.1.1-9 A set of abstract data type interf
ii libcommons-pool-java 1.5.4-1 pooling implementation for Java ob
ii sun-java6-jre [java2-runtime- 6-17-1 Sun Java(TM) Runtime Environment (
libcommons-dbcp-java recommends no packages.
Versions of packages libcommons-dbcp-java suggests:
pn glassfish-javaee <none> (no description available)
-- no debconf information
More information about the pkg-java-maintainers
mailing list