fix: Check mxBean compatibility

[asuresh4]

Check for mxBean compatibility ahead of checking whether Allocated Memory is enabled. This is related to #1435 .

[laurit]

@asuresh4 this repository requires commits to be signed https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits you also need to add the gpg key to your github account. Also take a look at https://safjan.com/git-sign-previous-commit/

[asuresh4]

Thanks @laurit , just amended the commit.

[asuresh4]

@breedx-splk @laurit thanks for reviewing and merging this. Would it be possible to do a patch release including the fix? We have a customer waiting for this. If that is not a possibility when is the next planned release? Thanks again!

[laurit]

@asuresh4 I think the next planned release would be on 16 nov. Patch release can be done if needed. It would help if you could provide a sentence for changelog that would describe what this fixes, or describe what failed without this fix.

[asuresh4]

@laurit I opened #1515 for updating CHANGELOG. PTAL. It would be awesome to provide a patch release for the customer since they've wanted to install the agent and this exception has been blocking them.

[laurit]

@asuresh4 is this fixing the same issue as described in #1435?

[asuresh4]

@laurit Yes, the underlying issue is the same. Before this fix, we were invoking isThreadAllocatedMemoryEnabled() (the method that throws the exception) before checking compatibility. This fix invokes mxBeanTypeIsCompatible() first so that we don't run into an exception when doing the casting.

Specifically, the order in which these methods are invoked here: https://github.com/signalfx/splunk-otel-java/pull/1435/files#diff-02b1f2b3a1bbe74fb65beb4e221e386aef0aef86ccabfca6a9774430035955c2R39