JVM crashes completely if "excludeClasses" profile is deactivated
If the "excludeClasses" profile is deactivated, the agent should not cause a stop of the jvm, it should be inactive.
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.