[Bug 541520] Re: Using incorrect JVM Garbage Collector
Jason Brittain
jason.brittain at mulesoft.com
Tue Mar 23 22:30:33 GMT 2010
Thierry:
There is part of this patch's change that may cause authbind to fail:
-# You may pass JVM startup parameters to Java here.
-#JAVA_OPTS="-Djava.awt.headless=true -Djava.net.preferIPv4Stack=true -Xmx128m"
+# You may pass JVM startup parameters to Java here. If unset, the default
+# options (-Djava.awt.headless=true -Xmx128m) will be used.
+#JAVA_OPTS="-Djava.awt.headless=true -Xmx128m"
Removing -Djava.net.preferIPv4Stack=true means that the JVM's network
stack might default to IPv6, and in that case authbind will (seemingly
mysteriously) fail. Authbind works only with IPv4. I think few users
use IPv6 today. It might eventually get popular, and if it does, it
would be a good idea if we're not always making software that defaults
to IPv4. But, I think the default should be IPv4, especially when
certain JDK bugs are encountered only when the JDK's startup switches do
not specify IPv4. So, I'm proposing we add back the
-Djava.net.preferIPv4Stack=true startup switch.
--
Using incorrect JVM Garbage Collector
https://bugs.launchpad.net/bugs/541520
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to tomcat6 in ubuntu.
More information about the Ubuntu-server-bugs
mailing list