It appears that this issue still persists in DB Connect 1.1.2:
http://docs.splunk.com/Documentation/DBX/1.1.2/DeployDBX/Releasenotes
Any specific on when this issue will be fixed in a form of either a patch or maintenance release?
I have tried the workaround solution from Answers:
However, it is still not resolving the problem. Specifically, I have tried the steps suggested by SplunkIT:
1.) Do not modify the $SPLUNK_HOME/etc/apps/dbx/bin/spp/java/__init__.py file
2.) Instead, add the following entries in $SPLUNK_HOME/etc/apps/dbx/bin/spp/__init__.py (the file is empty by default):
import os, logging
logging.basicConfig(level=logging.DEBUG,
filename=os.path.join(os.environ["SPLUNK_HOME"], "var", "log", "splunk", "jbridge.log"),
format="%(asctime)s %(levelname)s %(message)s", filemode="a")
In bin/spp/java/__init__.py add the following lines:
import os, logging
filename=os.path.join(os.environ["SPLUNK_HOME"], "var", "log", "splunk", "jbridge.log")
format="%(asctime)s %(levelname)s %(message)s"
logging.basicConfig(level=logging.ERROR, filename=filename, format=format, filemode="a")
logger=logging.getLogger("spp.java")
…
I have broken them into multiple lines. so it should be easy to do copy&paste now.
@btsay_splunk: Anyway you can attach the necessary __init__.py file/s for me to use instead? It appears that every time I do a copy and past, something would get screwed up. Unfortunately, I am not that familiar with python coding.