On Thu, 6 May 2010 17:42:32 -0700 Marcel Dan <[email protected]> wrote:

> I'm running i386 4.7 current (as of last week)  with jdk 1.6
> installed from cvs/ports.
> 
> I found the error.
> 
> 06.05.10 17:24:22 ERROR util.PerformanceMonitor - Error creating
> snapshot: java.lang.UnsupportedOperationException: Thread CPU Time
> Measurement is not supported.
> at sun.management.ThreadImpl.getThreadCpuTime(ThreadImpl.java:196)
> at
> com.devexperts.tos.util.JvmStateSnapshot.getCurrentCpuTimes
> (JvmStateSnapshot.java:45) at
> com.devexperts.tos.ui.user.util.PerformanceMonitor.createSnapshot
> (PerformanceMonitor.java:292) at
> com.devexperts.tos.ui.user.util.PerformanceMonitor.run
> (PerformanceMonitor.java:495)
> 
> I will keep working on it and post any successful results.


You should report this upstream to ToS, but ya, wait until next week
since they'll be hellishly busy with the crash/rectification. Though
previously ToS made false claims about supported java versions, now
they don't make any claims at all. Just Lovely.

I only found one outstanding and confirmed bug in the specific class
mentioned in your error message:

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6933325

It may, or may not, be related to your problem, but the bug report does
mention authentication.

As reported, the above bug effects 1.5 and 1.6, (specifically
jdk-1.6.0_18-b07) but there's no mention if the bug is in the current
jdk-1.6.0_21, or if it is present in the current openjdk-6-src-b19 (not
in ports, but "openjdk" is a different beast than "jdk").

If the problem is caused by a bug in java itself like the one above,
then you're totally hosed.

Our jdk 1.6 version in ports is jdk-1.6.0_03-b05 from Sep 2007, so it's
a few years old but according to the infamous marketing claims of their
"right once, ruin everywhere" motto, it should work.

Our openjdk 1.7 port *might* work for you (i386 or amd64), but realize
1.7 is a work in progress and Kurt Miller (kurt@) had to put a ton of
effort into openjdk 1.7 to make it run. The easy way to look at is, the
jdk-1.6 port has 22 patches and the openjdk-1.7 port has 308 patches.

I just started building 1.6 from ports on -current to look at this a bit
deeper, but my initial guess is the version we have in the ports tree
is too old for something fancy they're trying to do.

-- 
The OpenBSD Journal - http://www.undeadly.org

Reply via email to