I am seeing the same problem with a home grown application running on Oracle's jvm:
$ java -version java version "1.7.0_03" Java(TM) SE Runtime Environment (build 1.7.0_03-b04) Java HotSpot(TM) 64-Bit Server VM (build 22.1-b02, mixed mode)
Would this bug affect jvm's other than openjdk (the reporter of this bug and both duplicates are using openjdk 1.6)?
I am seeing the same problem with a home grown application running on Oracle's jvm:
$ java -version
java version "1.7.0_03"
Java(TM) SE Runtime Environment (build 1.7.0_03-b04)
Java HotSpot(TM) 64-Bit Server VM (build 22.1-b02, mixed mode)
Would this bug affect jvm's other than openjdk (the reporter of this bug and both duplicates are using openjdk 1.6)?