Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use driver from two separate ClassLoaders #1862

Open
m-froehlich opened this issue Jul 7, 2022 · 7 comments
Open

Use driver from two separate ClassLoaders #1862

m-froehlich opened this issue Jul 7, 2022 · 7 comments
Labels
Backlog The topic in question has been recognized and added to development backlog
Projects

Comments

@m-froehlich
Copy link

Driver version

10.2.0

SQL Server version

Irrelevant

Client Operating System

Windows, but irrelevant

JAVA/JVM version

17

Table schema

Problem description

When I try to use the driver from two separate ClassLoaders with integrated login enabled, then the native library is loaded twice, which effectively fails.

The driver should never load native libraries more than once, even if succeeding instances of the driver are triggered from other ClassLoaders.

@lilgreenbird
Copy link
Member

hi @m-froehlich we will investigate and get back to you

@lilgreenbird lilgreenbird added this to Under Investigation in MSSQL JDBC via automation Jul 11, 2022
@tkyc
Copy link
Member

tkyc commented Jul 12, 2022

We'll triage this in our next planning meeting and prioritize accordingly.

@tkyc tkyc added the Backlog The topic in question has been recognized and added to development backlog label Jul 12, 2022
@lilgreenbird lilgreenbird moved this from Under Investigation to Backlog in MSSQL JDBC Jul 12, 2022
@Jeffery-Wasty
Copy link
Member

Hi @m-froehlich,

An update on this issue. We're currently able to spend time on this issue, and are looking into providing a solution soon. In the meantime, are you able to confirm the problem persists with the latest version of the driver (11.2.0)?

@Jeffery-Wasty Jeffery-Wasty self-assigned this Aug 11, 2022
@Jeffery-Wasty Jeffery-Wasty added Under Investigation Used for issues under investigation and removed Backlog The topic in question has been recognized and added to development backlog labels Aug 11, 2022
@Jeffery-Wasty Jeffery-Wasty moved this from Backlog to Under Investigation in MSSQL JDBC Aug 11, 2022
@m-froehlich
Copy link
Author

Hi Jeffery,
thanks for taking the time. Nothing has changed to the issue so far. So, yes, this problem still persists in the current version of the driver.

@Jeffery-Wasty
Copy link
Member

Thanks for checking, we'll look into this and get back to you with our findings.

@tkyc tkyc moved this from Under Investigation to Backlog in MSSQL JDBC Nov 10, 2022
@Jeffery-Wasty Jeffery-Wasty added Backlog The topic in question has been recognized and added to development backlog and removed Under Investigation Used for issues under investigation labels Feb 1, 2023
@dobos66
Copy link

dobos66 commented Jan 30, 2024

Hi Jeffery,
We've encountered the same issue using the latest 12.4 driver. Could you please inform us if there will be any progress on this in the near future, or if there is a workaround currently available? Thank you for your assistance!

@Jeffery-Wasty Jeffery-Wasty removed their assignment Jan 30, 2024
@Jeffery-Wasty
Copy link
Member

Jeffery-Wasty commented Jan 30, 2024

This issue is in our backlog at the moment. We'll reassess the priority and update this issue if we plan to continue work on it in the near future.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backlog The topic in question has been recognized and added to development backlog
Projects
MSSQL JDBC
  
Backlog
Development

No branches or pull requests

5 participants