I really don't like that Oracle knew about this and released anyway
(even if it were only hours prior to the release) -- without making
-XX:-UseLoopPredicate
the default.
It's better not to release on time than to release something that
customers don't trust.
Having to add JVM options just to get a JVM to work correctly is a
non-starter. That's the sort of thing I expect from IBM JVMs -- and
detest them for. The default mode of the JVM should be correct and
stable -- with -XX:+UseLoopPredicate, etc, allowing those most desperate
for speed to live dangerously on their own time.
On 7/29/2011 5:05 PM, Mark Derricutt wrote:
Yes, but you can work around it by using:
-XX:-UseLoopPredicate
I'm getting tired already of seeing many sites ranting about this bug without
mentioning the work around described in the actual Oracle bug tickets.
The tests that actually uncovered the problems were only written last month:
https://issues.apache.org/jira/browse/LUCENE-3079
I've not looked at the tests/patches yet but I'm curious as to what they're
doing that managed to uncover this problem, and just how likely it is to hit in
normal day-to-day code that no other tests fails/hit it.
Mark
On 30/07/2011, at 1:10 AM, Michael Barker wrote:
It's annoying, I was hoping to drop it into our CI environment next week...
--
You received this message because you are subscribed to the Google Groups "The Java
Posse" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/javaposse?hl=en.
