Skip to main content

Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Test and Performance Tools Platform (TPTP) » Why native code for agents?
Why native code for agents? [message #141915] Wed, 15 April 2009 16:05 Go to next message
Tony Anecito is currently offline Tony AnecitoFriend
Messages: 20
Registered: July 2009
Junior Member
Hi Eugene,

Why native code for agents? I would thought Sun would provide an all java
way of talking to the jvm for jvmti.

Just curious,
Re: Why native code for agents? [message #142049 is a reply to message #141915] Fri, 24 April 2009 00:43 Go to previous message
Jonathan West is currently offline Jonathan WestFriend
Messages: 49
Registered: July 2009
The JVM Tool Interface specification document is available from here
(, and
describes the entire interface. My presumption is that the requirement for
a native interface is a given, as speed when profiling (or otherwise
interfacing with the JVM) is a top concern so as not to slow down the
virtual machine. Implementing both a Java and native interface to JVM
could merely then have been a resource prioritization. There are also
life-cycle and application/agent barrier concerns with a Java-only JVMTI

The JVM Tool Interface requires instrumentation for many of the functions
ones would normally associate with a tooling interface (for instance,
method calls or object allocation), and, as such, this work could be done
without the JVMTI interface, with Java itself, using the
java.lang.instument.* classes available in Java 5 or with another
instrumentation engine.

The original JSR, JSR 163, is available here
Previous Topic:[Monitor]: The launch requires at least one data collector to be selected.
Goto Forum:

Current Time: Fri Jun 22 23:07:41 GMT 2018

Powered by FUDForum. Page generated in 0.01613 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top