Hi JB, I was wondering if you had a chance to takle a look at the issue I mentioned previously below? The JDBC driver in question is SAP HANAm file ngdbc-2.7.7.jar (or ngdbc-2.5.52.jar as well). Karaf 4.30, openjdk-14.0.2, Windows Server 2016.
Should I create a Felix Jira issue for this? Regards, Scott Leschke From: Leschke, Scott <slesc...@medline.com> Sent: Wednesday, December 30, 2020 9:12 AM To: user@karaf.apache.org Subject: RE: Multi-release jar bundles CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. ________________________________ I think you should be able to reproduce it if you can get hold of the driver. From: Jean-Baptiste Onofre Sent: Wednesday, December 30, 2020 12:09 AM To: user@karaf.apache.org Subject: Re: Multi-release jar bundles CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. ________________________________ Hi Scott, You can try to wrap settings the TCCL, but it seems more a driver issue. Can I reproduce it easily (just installingg SAP driver for instance) ? Regards JB Le 29 déc. 2020 à 19:31, Leschke, Scott <slesc...@medline.com<mailto:slesc...@medline.com>> a écrit : I have a JDBC driver jar (SAP HANA), that is build both as a bundle and an MRJar file supporting JDKs 1.8, 9, 11. It works fine when I run Karaf using JDK 1.8, but if I try to use a more recent JDK, the driver throws the following Caused by: java.lang.AssertionError: Unexpected Java class loaded under Java version 11 (maximum supported version is 8) at com.sap.db.jdbc.DriverSapDB._checkJavaVersion(DriverSapDB.java:2055) ~[?:?] at com.sap.db.jdbc.DriverSapDB.checkJavaVersionMaximum8(DriverSapDB.java:2030) ~[?:?] at com.sap.db.jdbc.Driver.(Driver.java:17) ~[?:?] An SAP person says they think the classloader isn’t MRJar aware and is loading the incorrect class. I most recently tried this with OpenJDK 14.x. Since OSGi involves lots of classloader magic, might that be the case or might something else be going on here? Thanks and regards, Scott Leschke
