Yes, I use this field to set a timestamp (an int). And I'm not using the
special constructor, so I must be using the default precision step.
Java version : 1.6.0_24
mpire@seafcmr16:~$ java -version
java version "1.6.0_24"
Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
Java HotSpot(TM) 64-Bit
Hi,
Can you try 1.6.0_29 or disable hotspot by using "-Xint" JVM startup flag
(just to test, I know, it's slow then)? Are you *not* using
"-XX:+AggressiveOpts" as JVM parameter?
The JVM bug which may lead to this is a sign-flip bug:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5091921 (s
This is difficult to repro. I'm not using any JVM flags. It does seem
that the following code could never call NumericUtils.intToPrefixCoded
with a shift > 31 (or shift < 0) so I tend to agree this must be a JVM
bug. Looking through all logs I have for December, I only found one
instance of this is
