Config issue on Linux
I believe you can ignore that, especially if you do not have Mecury diagnostics installed. There are some heuristics that are applied at startup (found in the DTHOME/server/conf/server.config.xml file) that identify this potential conflict. In particular you're probably matching this rule:
<entry message="Potential conflicting jvm option found: Mercury Diagnostics" regex=".(?i)-Xbootclasspath/p.(JavaProbe\\classes
boot|JavaProbe/classes/boot).*" severity="warning" shutdown="false" />
Hope this helps,
Rob
Welcome the
Dynatrace Community Forums
Check out the Forum User Guide and Forum Guidelines to learn how to get started.Community Member of the Month
August 2017
Announcing Dynatrace's Community Member of the Month for August 2017, Rick B.! Click here to read more! 
