Open kares opened 2 years ago
this is a known issue with SAP (implementation vendor of the Sybase driver).
potential alternative might be to switch to the jTDS driver (using jdbc:jtds:sybase://
uri format), the driver is unmaintained for years (so is jConnect Sybase driver) but should be working for the simple requirements the JDBC input has on a JDBC driver.
Any work around found for this issue ? I am facing this exact issue in my application
When both jconn4.jar (Sybase JDBC driver) and ojdbc11.jar (Oracle JDBC driver) are on Logstash's class-path, driver auto-loading (with
DriverManager
) occasionally leads to issues.Confirmed versions that exhibit the behavior:
jConnect for JDBC(TM)/7.07 SP100
(Build 26 846)/P/EBF20990/JDK 1.6.0/jdbcmain/OPT/Wed Apr 24 11:30:54 PDT 2013
21.1.0.0.0
Failures usually looks like if the Sybase driver did not load (
Java::com.sybase.jdbc4.jdbc.SybDriver not loaded
):but might also surface as
Java::oracle.jdbc.driver.OracleDriver not loaded
and depend on execution order with multiple inputs.sample native traces when running with plugin >= 5.1.10 :
a potential work-around is to not put these drivers on the class-path at the same time (under $LS_HOME/logstash-core/lib/jars) and instead use the
jdbc_driver_library =>
configuration option. also worth checking latest versions of the drivers whether they still exhibit the behavior.p.s. might be a good candidate for https://github.com/logstash-plugins/logstash-integration-jdbc/issues/93