JMX Integration Error with AEM

CentOS Linux release 7.8.2003 (Core)

New Relic Infrastructure Agent version: 1.12.0

Infrastructure Pro Annual

Hi

We recently installed the JMX Integration to monitor some mbeans in our AEM instance. We could access the information as expected. But we notice an elevated amount of errors in the logs.

Here is the error we have seen in the logs.

28.07.2020 15:39:42.518 *ERROR* [RMI TCP Connection(834)-10.X.X.X] org.apache.jackrabbit.oak.core.ContentSessionImpl Error during logout.

javax.security.auth.login.LoginException: Login Failure: all modules ignored

Do you have any idea what can cause this type of error?
could it be a miss configuration in the integration?

Thanks for any help you can offer.

Hi @abustamante,

It’s hard to say without being able to compare the response from nrjmx (The JMX client bundled with the JMX integration that makes the actually connection). Can you try running nrjmx directly against your JMX server and share some of the output? The following will try to enumerate all of the Mbeans on your server:

echo '*:*' | nrjmx -H $JMX_SERVER -P $JMX_PORT -v -d -

Hi @sellefson,

Thanks for your help, but the result is simply too long, around 6000 lines, is there something specific you are looking for?

thanks.

Hi @abustamante

What do the first few lines of [DEBUG] output show?

The errors you shared are specific to your Java application, so if they were causing an issue with JMX clients to your applications JMX server, I would expect to see them reflected in the connection attempt from nrjmx.

Hi @sellefson,

Thanks for your help.
Here are the first 50 lines of the output.

nrjmx-2020-07-31-head.txt (6.4 KB)

Thanks,
Armando Bustamante

Hey @abustamante

I see history in our support tickets of this error that I see in the file you sent:

FINE: Unsuported data type (class java.util.Date) for bean org.apache.sling.healthcheck:type=HealthCheck,name=largeIndexHealthCheck,attr=finishedAt
Jul 31, 2020 7:11:28 PM org.newrelic.nrjmx.JMXFetcher queryAttributes

being related to the integration querying beans that are not of a supported type.

This needed some additional investigation from our engineering team & I believe it does now.

Watch out for an email in your inbox from our support team who can help out with talking to our dev team.

hi, just looking through the forum tickets. Did this ever get resolved? I dont think it did. We are using the latest new relic k8s integration agent, looking at the nrjmx, support for java.util.Date doesnt look to be available ?
(https://github.com/newrelic/nrjmx/blob/master/src/main/java/org/newrelic/nrjmx/JMXFetcher.java#L353)

Error I am seeing is:

echo “com.pushtechnology.diffusion:type=Server,server=*” | /usr/bin/nrjmx -host 192.168.199.212 -port 6789 --verbose true

Feb 23, 2021 12:39:27 PM org.newrelic.nrjmx.JMXFetcher queryAttributes
FINE: Unsuported data type (class java.util.Date) for bean com.pushtechnology.diffusion:server=“diffusion-0”,type=Server,attr=LicenseExpiryDate