alibaba/Sentinel

JVM crash on JMX getSystemCpuLoad when using Sentinel

Open

#2,885 opened on Sep 20, 2022

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Java (23,109 stars) (8,150 forks)batch import
help wantedkind/question

Description

Issue Description

Type: bug report or fea hs_err_pid6440.log ture request

Describe what happened (or what feature you want)

Describe what you expected to happen

How to reproduce it (as minimally and precisely as possible)

Tell us your environment

Anything else we need to know?

Contributor guide

Tech stack
java
Domain
backendobservability
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
unclear
Prerequisites
JavaJVM internalsJMXSentinel experience
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
10
Research direction
The issue involves a JVM crash when using JMX getSystemCpuLoad with Sentinel. The attached hs err log file (hs err pid6440.log) should be analyzed to identify the crash location and potential causes. Reproduce the issue with a minimal Sentinel setup and JMX monitoring, and check for known JVM bugs or Sentinel configuration issues. Look at related issues and pull requests in the Sentinel repository for context.