Details
-
Type:
Bug
-
Status: Closed
-
Priority:
P2
-
Resolution: Not an Issue
-
Affects Version/s: 5.0
-
Fix Version/s: None
-
Component/s: tools
-
Subcomponent:
-
CPU:generic
-
OS:generic
Description
Customer SAP has build a profiling/monitoring application based on JVMDI.
The new Tiger monitoring API lacks 4 events, which are needed by SAP's application sherlok
This table gives an overview of the needed events:
missing events for jvmti | corresponding event in jvmdi which is used by sherlok
--------------------------------+--------------------------------------------------------
JVMTI_EVENT_OBJECT_FREE1 = 85 | JVMPI_EVENT_OBJECT_FREE = 5
JVMTI_EVENT_OBJECT_ALLOC = 86 | JVMPI_EVENT_OBJECT_ALLOC = 4
JVMTI_EVENT_OBJECT_MOVE = 87 | JVMPI_EVENT_OBJECT_MOVE = 6
JVMTI_EVENT_ARENA_DELETE = 88 | JVMPI_EVENT_ARENA_DELETE = 49
The new Tiger monitoring API lacks 4 events, which are needed by SAP's application sherlok
This table gives an overview of the needed events:
missing events for jvmti | corresponding event in jvmdi which is used by sherlok
--------------------------------+--------------------------------------------------------
JVMTI_EVENT_OBJECT_FREE1 = 85 | JVMPI_EVENT_OBJECT_FREE = 5
JVMTI_EVENT_OBJECT_ALLOC = 86 | JVMPI_EVENT_OBJECT_ALLOC = 4
JVMTI_EVENT_OBJECT_MOVE = 87 | JVMPI_EVENT_OBJECT_MOVE = 6
JVMTI_EVENT_ARENA_DELETE = 88 | JVMPI_EVENT_ARENA_DELETE = 49