JVM crashes completely if "excludeClasses" profile is deactivated

Description

If the "excludeClasses" profile is deactivated, the agent should not cause a stop of the jvm, it should be inactive.

Environment

Activity

Show:
Ivan Senic
October 13, 2017, 11:15 AM

Let's figure out why is this happening. I know it's possible to not use exclude-rules as we do it in the CMR monitoring configuration. Thus, it needs to be understood.

At least we should increase the severity of the warning displayed on the UI.

Please have a look onto this.

Won't Fix

Assignee

Tobias Angerstein

Reporter

Tobias Angerstein

Labels

None

Integrator

None

Sprint

Priority

Medium