JDK-8214803 : Provide SQE and Infra support for 8203359 - container aware JFR events
  • Type: Sub-task
  • Component: hotspot
  • Sub-Component: jfr
  • Affected Version: 12
  • Priority: P4
  • Status: Resolved
  • Resolution: Delivered
  • Submitted: 2018-12-04
  • Updated: 2019-08-15
  • Resolved: 2019-04-15
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 13
13Resolved
Related Reports
Relates :  
Relates :  
Relates :  
Relates :  
Description
Provide an environment or setup instructions to help JFR developers with this task.

E.g.: host with docker engine installed, a set of scripts to generate docker container with JDK in it.
Also, explore certain areas that may be problematic. Run simple Java program with JFR on inside a container, and generate events that provide resource info. Constrain various resources when launching a container, such as Memory, numbers of CPUs, CPU shares, etc. Verify that JFR accurately reports the resources available to the JVM in a container under test. Also, make sure certain handles are properly reported, such as PIDs (host system PID is different from PID of a process inside a container).
Comments
I have created a test to check number of processors, memory and PID for JVM running inside a Docker container. The memory and PID are reported correctly, while number of CPUs is reported incorrectly. New test: 8219997: [TESTBUG] Create test for JFR events in Docker container: CPU, Memory and Process Info Filed a bug for CPU Info issue: 8219999: JFR jdk.CPUInformation event reports incorrect information when running in Docker container
01-03-2019