My DB Connect app has no problem connecting to a non-ssl enforced MSSQL instance. However, when connecting to a ssl enforced MSSQL instance, db connect appears to hang.
One interesting observation is that the problem (hang) seems to be reproducible using a 3rd party app like DBVisualizer to connect using the jTDS driver (same driver use by DB Connect).
By adding this -Djsse.enableCBCProtection=false param in the java options, I can connect to SSL enabled MSSQL instance without having to add any new parameters in the JDBC connection URL.
This appears to be a java bug:
https://www.aquaclusters.com/app/home/project/public/aquadatastudio/discussion/GeneralDiscussions/po...
https://forums.oracle.com/message/10843957
To workaround it, I have to add "-Djsse.enableCBCProtection=false" to the java options parameter, by appending it in the $SPLUNK_HOME/apps/dbx/local/java.conf file. Here is mine for your reference:
[java]
home = /home/luan/jdk1.7.0_25
options = -Xmx256m -Dfile.encoding=UTF-8 -server -Djsse.enableCBCProtection=false -Duser.language=en -Duser.reg ion=
Hi,
I spend a whole day trying to connect using all of this above ( and more, i.e. digging through the canyons of the internet), but to no result. Problem was solved when I uninstalled Java 1.8 and reinstalled Java 1.7.
Works like a charm now.
Btw I am using splunk 6.3. on Linux (Ubuntu). Using sqljdbc4.jar from microsoft (https://www.microsoft.com/en-us/download/details.aspx?displaylang=en&id=11774) to connect to MS SQL server 12.0.2000
Java.conf:
[java]
home = /usr/lib/jvm/default-java/jre
options = -Xmx256m -Dfile.encoding=UTF-8 -Djsse.enableCBCProtection=false -server -Duser.language=en -Duser.region=
Hi,
I'm getting below error for MS SQL connection,
Encountered the following error while trying to save: Splunkd daemon is not responding: ("Error connecting to /servicesNS/admin/dbx/dbx/databases: ('The read operation timed out',)",)
can please help for this
By adding this -Djsse.enableCBCProtection=false param in the java options, I can connect to SSL enabled MSSQL instance without having to add any new parameters in the JDBC connection URL.
This appears to be a java bug:
https://www.aquaclusters.com/app/home/project/public/aquadatastudio/discussion/GeneralDiscussions/po...
https://forums.oracle.com/message/10843957
To workaround it, I have to add "-Djsse.enableCBCProtection=false" to the java options parameter, by appending it in the $SPLUNK_HOME/apps/dbx/local/java.conf file. Here is mine for your reference:
[java]
home = /home/luan/jdk1.7.0_25
options = -Xmx256m -Dfile.encoding=UTF-8 -server -Djsse.enableCBCProtection=false -Duser.language=en -Duser.reg ion=
Hi, I'm experiencing this time-out connecting to a remote SQL 2014. I've tried the java options and arg.ssl=require but neither work. What can I try next? Thanks
My java.conf
[java]
home = C:\Program Files\Java\jre1.8.0_45
options = -Djsse.enableCBCProtection=false
@splunkIT Thanks again!! this worked, now I can go have fun on the farm.
(\__/)
(='.'=)
(")_(")
One quick fix to the statement above, you might want to add the region to this option entry:
options = -Xmx256m -Dfile.encoding=UTF-8 -server -Djsse.enableCBCProtection=false -Duser.language=en -Duser.region=us
Hello, i have the same issue during connecting dbx to mssql2012.
I add -Djsse.enableCBCProtection=false to .../apps/dbx/local/java.conf and it's didn't work
Can anybody help me with this?
@yyakovlev, please open a ticket with splunk support if you still need assistance on db connect.