Splunk Add-on for Java Management Extensions 5.3.0 ERRORS

[justynap_ldz]

Hello All,

We keep getting some errors from Splunk Add-on for Java Management Extensions 5.3.0:

splunkd.log

1. ERROR ExecProcessor [20951 ExecProcessor] - message from "/opt/splunk/bin/python3.7 /opt/splunk/etc/apps/Splunk_TA_jmx/bin/jmx.py" INFO: Loading mapping descriptors from jar:file:/opt/splunk/etc/apps/Splunk_TA_jmx/bin/lib/jmxmodinput.jar!/mapping.xml

2. ERROR ExecProcessor [20951 ExecProcessor] - message from "/opt/splunk/bin/python3.7 /opt/splunk/etc/apps/Splunk_TA_jmx/bin/jmx.py" Mar 01, 2023 11:59:59 PM org.exolab.castor.mapping.Mapping loadMapping

jmx.log

3. 2023-03-02 06:37:18,168 - com.splunk.modinput.ModularInput -1968729474 [Thread-11] INFO [] - Failed connection with 'service:jmx:rmi:///jndi/rmi://server1.domain.com:port/jmxrmi', trying to collect data with a short URL: 'service:jmx:rmi://server1.domain.com:port/jndi/jmxrmi' .
2023-03-02 06:37:18,168 - com.splunk.modinput.ModularInput -1968729474 [Thread-11] ERROR [] - Exception@checkConnector, e=
java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:369) ~[?:1.8.0_51]
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:270) ~[?:1.8.0_51]
at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:229) ~[?:1.8.0_51]
at com.splunk.jmx.ServerTask.connect(Unknown Source) ~[jmxmodinput.jar:?]
at com.splunk.jmx.ServerTask.checkConnector(Unknown Source) ~[jmxmodinput.jar:?]
at com.splunk.jmx.Scheduler.run(Unknown Source) ~[jmxmodinput.jar:?]
Caused by: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: java.naming.factory.initial
at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:662) ~[?:1.8.0_51]
at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:313) ~[?:1.8.0_51]
at javax.naming.InitialContext.getURLOrDefaultInitCtx(InitialContext.java:350) ~[?:1.8.0_51]
at javax.naming.InitialContext.lookup(InitialContext.java:417) ~[?:1.8.0_51]
at javax.management.remote.rmi.RMIConnector.findRMIServerJNDI(RMIConnector.java:1957) ~[?:1.8.0_51]
at javax.management.remote.rmi.RMIConnector.findRMIServer(RMIConnector.java:1924) ~[?:1.8.0_51]
at javax.management.remote.rmi.RMIConnector.connect(RMIConnector.java:287) ~[?:1.8.0_51]
... 5 more
2023-03-02 06:37:18,168 - com.splunk.modinput.ModularInput -1968729474 [Thread-11] WARN [] - Server misconfiguration already notified once for jmx://_Splunk_TA_jmx_:server1 stanza with message: Failed to connect with the JMX server. Review the configuration of the jmx://_Splunk_TA_jmx_:server1 stanza, and try again.
2023-03-02 06:37:18,174 - com.splunk.modinput.ModularInput -1968729480 [Thread-11] INFO [] - 1 servers found in stanza jmx://_Splunk_TA_jmx_:server1

Add-on has been configured on a Heavy Forwarder
Our jmx_servers.conf is:

[hostname]
description = <description>
destinationapp = Splunk_TA_jmx
host = <FQDN>
jmxport = <port>
protocol = rmi
stubSource = jndi
disabled = 0
lookupPath = /jmxrmi

Does anyone have any idea on how to fix it? 

Greetings,
Justyna