[Splunk Add-on for Java Management Extensions] Error After Java Version Upgrade - FileNotFoundError

In this scenario, the Java version on the Splunk heavy forwarder was upgraded from 11.0.22.0.7 to 11.0.23.0.9. After the upgrade, data collection from the servers using the Splunk Add-on for Java Management Extensions (TA-JMX) failed, resulting in the following error message in splunkd.log file.

 

2024-10-20 22:59:36,542 ERROR pid=11445 tid=MainThread file=jmx.py:<module>:121 | Failed to open the invoke the input. Reason: Traceback (most recent call last): 
File "/opt/splunk/splunk_hf/etc/apps/Splunk_TA_jmx/bin/jmx.py", line 116, in <module> 
java_main_args, stdin=PIPE, text=True 
File "/opt/splunk/splunk_hf/lib/python3.7/subprocess.py", line 800, in __init__ 
restore_signals, start_new_session) 
File "/opt/splunk/splunk_hf/lib/python3.7/subprocess.py", line 1567, in _execute_child 
raise child_exception_type(errno_num, err_msg, err_filename) 
FileNotFoundError: [Errno 2] No such file or directory: '/usr/lib/jvm/java-11-openjdk-11.0.22.0.7-1.amzn2.0.1.x86_64//bin/java': '/usr/lib/jvm/java-11-openjdk-11.0.22.0.7-1.amzn2.0.1.x86_64//bin/java'

 

The error indicates that the system is still referencing the old Java path (11.0.22) instead of the new version (11.0.23), leading to the failure in invoking the Java process for the JMX data collection.