- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Java_path environment variable in dbx_settings.conf
Hi, does anyone know if it's possible to replace the hard coded javaHome key in db_connect's dbx_settings.conf file with the java_home environment variable in Windows? I have an auto patching set-up in a Windows Splunk heavy forwarder, and every time Java gets upgraded, it crashes the Splunk service. For example, I'd like to replace this:
javaHome = C:\Program Files\java\jdk-17.0.11.9-hotspot
With this:
javaHome=%java_home%
The above syntax doesn't work, although I'm not sure if it's a syntax or functionality issue.
Thanks!
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I tried adding it via the gui, but I get the error "JAVA_HOME path does not exist". I'm curious if Splunk is it's a syntax issue - I'm inputting %JAVA_HOME% as the path.
I also found that if I leave the field blank, Splunk auto-populates the value. I'll see if it auto-populates it with a new path at next upgrade.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content

@apiprek2- Try updating JavaHome variable from DB Connect UI with that variable you have on Windows.
And see if your Splunk DB connect works properly or not.
On the side note, Ideally root Splunk service should not have any impact on change or Java, Java variable, or DB connect.
I hope this helps!!!
