JBoss Profiler can't be activated!!

[jtcnz]

I'm using JBoss Profiler 1.0 RC3 on JBoss 4.0.3SP1 AS based on JDK1.4.2_17
All set up procedures have been done. Both front-end and JMS agent can be accessed.

BUT when I click the "invoke" button of "void activete()" in console to run profiler, the result is"the page cannot be displayed". An error happens and terminates the JBoss server.

Error INFO:

JBoss Profiler: Initializing DataGathering
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# Internal Error (50415241.................235), pid=3556, tid=5924
#
# Java VM HotSpot<TM> 1.4.2_17
#.......

Any idea to solve this problem?
Any similar experience to share?

(sorry to post this again)

Thanks

[peterj]

This is a JVM crash which should be reported to the Sun JVM team. Good luck in getting it fixed since 1.4.2 is no longer supported. But they might be able to tell you if the issue is with an OS component such as a driver. You might want to make sure that the drivers for all your hardware are at the latest levels.

[jtcnz]

Thanks Peter

Yes. This probably relates to the OS components, because with the same configuration, the profiler can be activated on my Win XP prof. OS but Win 2003 server with SP2 not.

[jtcnz]

Actually, it's more probably related to VMWare bug.

JProfiler can't be activated on Win 2003 Server OS which is running in VMWare. It works on a totally same OS on a real machine.

[peterj]

And from what I can recall, that version of the JVM is not supported in a virtual machine.

[jtcnz]

But we are indeed using this JVM in a virtual machine without any incompatible behavior...
crazy...hehe

[peterj]

There is a difference between "seems to work" and "supported". If the JVM works without issue in the virutal machine, then fine (this is the "seems to work" case).

If you run into a JVM crash in a virtual machine, you have to first reproduce it in a physical machine before Sun will look at the issue. That is what is meant by "not supported". If it was supported, you could submit the crash from the virtual machine.