Done (#568823). As I say I'm still not convinced about the CMS collector
as a default, but I'll follow up later if I become more passionate about
it. :)
--
Using incorrect JVM Garbage Collector
https://bugs.launchpad.net/bugs/541520
You received this bug notification because you are a member of
This bug being closed, could we move this (interesting) discussion to a
new bug report, something like further refining of Tomcat's JVM default
parameters ? I'm all open to improvement in that area, but i'm far from
being a Tomcat memory expert or someone that knows how it's used by most
people,
The point that we know something the JVM can't know, eg, that this JVM
is running a web server, is fair. I'm still not convinced that
specifying the CMS collector is the right application of this knowledge,
and I'm new to Ubuntu (from a contributor standpoint, anyway) so I don't
know what the
I'm OK with moving the -Xmx128M parameter out onto one of the comment
lines as this is a commonly known and understood parameter. Most google
(bing?) searches will advise you to adjusting this parameter when you
come upon memory problems.
If we want to ensure that we don't assign
Folks -- sorry for chiming in here after the train has apparently left
the station :)
I've been working on optimizing my Tomcat configuration for the past
couple days, and this optimization has mostly centered around the
garbage collector. I'm concerned that specifying the CMS collector is
Gabriel: It's certainly alright to still discuss this. It's a
complex issue, with (I think) only very rough solutions.
I agree that the JVM authors are saying that if you cannot know
in advance very much about how the Java program is going to be
using the JVM, and if you cannot know about the
This bug was fixed in the package tomcat6 - 6.0.24-2ubuntu1
---
tomcat6 (6.0.24-2ubuntu1) lucid; urgency=low
[ Thierry Carrez ]
* Uploading what 6.0.24-5 should be (upload is blocked in Debian due to
current infrastructure issues), in order to meet Beta2Freeze.
[ Niels
It should not break because authbind is special-cased in the init
script:
Init script sets:
JAVA_OPTS=-Djava.awt.headless=true -Xmx128m
Then sources the defaults file, which may or may not override JAVA_OPTS
Then if authbind is set, it does:
JAVA_OPTS=$JAVA_OPTS -Djava.net.preferIPv4Stack=true
Ahh, yes. That's true. I now remember that I made sure to enable that switch
whenever
authbind is enabled. But, also, I seem to remember some past issues that were
fixed by
setting -Djava.net.preferIPv4Stack=true by default.. though I can't find any of
those in the
ASF Tomcat bugzilla at the
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
** Changed in: tomcat6 (Ubuntu)
Importance: Low = Medium
** Changed in: tomcat6 (Ubuntu)
Status: Confirmed = In Progress
** Changed in: tomcat6 (Ubuntu)
Assignee: (unassigned) = Thierry Carrez (ttx)
--
Using incorrect JVM Garbage Collector
https://bugs.launchpad.net/bugs/541520
Here is the patch I'll apply as soon as maven-repo-helper gets synced,
just in case Debian wants to apply it before :)
** Attachment added: proposed-patch
http://launchpadlibrarian.net/41623441/proposed-patch
--
Using incorrect JVM Garbage Collector
https://bugs.launchpad.net/bugs/541520
You
Which version is this for?
Regards
chuck
** Changed in: tomcat6 (Ubuntu)
Importance: Undecided = Low
** Changed in: tomcat6 (Ubuntu)
Status: New = Incomplete
--
Using incorrect JVM Garbage Collector
https://bugs.launchpad.net/bugs/541520
You received this bug notification because
I think this is valid for any 6.0.x versions. I asked Jason Brittain for
advice on how much this is desirable in the default install.
** Changed in: tomcat6 (Ubuntu)
Status: Incomplete = Confirmed
--
Using incorrect JVM Garbage Collector
https://bugs.launchpad.net/bugs/541520
You
My short opinion is: Yes, it does make sense to use the CMS GC for
Tomcat by default.
Aaron: Thanks very much for the link to Sun's Hotspot memory management
white paper, and for the suggestion to use CMS by default. I have seen
quite a few production Tomcat environment config files over the
** Patch added: Improved tomcat6 file
http://launchpadlibrarian.net/41253077/tomcat6
--
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.
** Tags added: patch
--
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.
--
Ubuntu-server-bugs mailing list
17 matches
Mail list logo
