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.

Sign up for GitHub

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

IBM Semeru Runtime Certified Edition for z/OS, Kerberos and mssql-jdbc don't work together #2576 #2581

Open
wants to merge 10 commits into
base: main
Choose a base branch
from
+89 −16

Update isIBM()

6187602
Select commit
Loading
Failed to load commit list.
Open

IBM Semeru Runtime Certified Edition for z/OS, Kerberos and mssql-jdbc don't work together #2576 #2581

Update isIBM()
6187602
Select commit
Loading
Failed to load commit list.
Azure Pipelines / public-mssql-jdbc.linux succeeded Jan 29, 2025 in 29m 25s

Build #20250129.1 had test failures

2 errors / 6 warnings

Details

Tests

  • Failed: 6 (0.16%)
  • Passed: 3,796 (98.80%)
  • Other: 40 (1.04%)
  • Total: 3,842

Annotations

Check failure on line 40536 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / public-mssql-jdbc.linux

Build log #L40536 

Build failed.

Check failure on line 40909 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / public-mssql-jdbc.linux

Build log #L40909 

Build failed.

Check failure on line 1 in testWithTrustManagerConstructorArg

See this annotation in the file changed.

@azure-pipelines azure-pipelines / public-mssql-jdbc.linux

testWithTrustManagerConstructorArg 

No suitable driver found for jdbc:sqlserver://msjdbctest.database.windows.net;database=jdbctest;loginTimeout=120;msiClientId=a0bc0c34-a024-4037-9368-9f904a008c36;authentication=ActiveDirectoryManagedIdentity;;encrypt=false;;trustServerCertificate=true;;trustManagerClass=com.microsoft.sqlserver.jdbc.ssl.trustmanager.TrustManagerWithConstructorArg;trustManagerConstructorArg=dummyString;
Raw output 
java.sql.SQLException: No suitable driver found for jdbc:sqlserver://msjdbctest.database.windows.net;database=jdbctest;loginTimeout=120;msiClientId=a0bc0c34-a024-4037-9368-9f904a008c36;authentication=ActiveDirectoryManagedIdentity;;encrypt=false;;trustServerCertificate=true;;trustManagerClass=com.microsoft.sqlserver.jdbc.ssl.trustmanager.TrustManagerWithConstructorArg;trustManagerConstructorArg=dummyString;
	at com.microsoft.sqlserver.jdbc.ssl.trustmanager.CustomTrustManagerTest.testWithTrustManagerConstructorArg(CustomTrustManagerTest.java:50)

Check failure on line 1 in testWithInvalidTrustManager

See this annotation in the file changed.

@azure-pipelines azure-pipelines / public-mssql-jdbc.linux

testWithInvalidTrustManager 

No suitable driver found for jdbc:sqlserver://msjdbctest.database.windows.net;database=jdbctest;loginTimeout=120;msiClientId=a0bc0c34-a024-4037-9368-9f904a008c36;authentication=ActiveDirectoryManagedIdentity;;encrypt=false;;encrypt=true;trustServerCertificate=false;trustManagerClass=com.microsoft.sqlserver.jdbc.ssl.trustmanager.InvalidTrustManager ==> expected: <true> but was: <false>
Raw output 
org.opentest4j.AssertionFailedError: No suitable driver found for jdbc:sqlserver://msjdbctest.database.windows.net;database=jdbctest;loginTimeout=120;msiClientId=a0bc0c34-a024-4037-9368-9f904a008c36;authentication=ActiveDirectoryManagedIdentity;;encrypt=false;;encrypt=true;trustServerCertificate=false;trustManagerClass=com.microsoft.sqlserver.jdbc.ssl.trustmanager.InvalidTrustManager ==> expected: <true> but was: <false>
	at com.microsoft.sqlserver.jdbc.ssl.trustmanager.CustomTrustManagerTest.testWithInvalidTrustManager(CustomTrustManagerTest.java:68)

Check failure on line 1 in testWithPermissiveX509TrustManager

See this annotation in the file changed.

@azure-pipelines azure-pipelines / public-mssql-jdbc.linux

testWithPermissiveX509TrustManager 

No suitable driver found for jdbc:sqlserver://msjdbctest.database.windows.net;database=jdbctest;loginTimeout=120;msiClientId=a0bc0c34-a024-4037-9368-9f904a008c36;authentication=ActiveDirectoryManagedIdentity;;encrypt=false;;trustServerCertificate=true;;trustManagerClass=com.microsoft.sqlserver.jdbc.ssl.trustmanager.PermissiveTrustManager
Raw output 
java.sql.SQLException: No suitable driver found for jdbc:sqlserver://msjdbctest.database.windows.net;database=jdbctest;loginTimeout=120;msiClientId=a0bc0c34-a024-4037-9368-9f904a008c36;authentication=ActiveDirectoryManagedIdentity;;encrypt=false;;trustServerCertificate=true;;trustManagerClass=com.microsoft.sqlserver.jdbc.ssl.trustmanager.PermissiveTrustManager
	at com.microsoft.sqlserver.jdbc.ssl.trustmanager.CustomTrustManagerTest.testWithPermissiveX509TrustManager(CustomTrustManagerTest.java:36)

Check failure on line 1 in testWithTrustManagerConstructorArg

See this annotation in the file changed.

@azure-pipelines azure-pipelines / public-mssql-jdbc.linux

testWithTrustManagerConstructorArg 

No suitable driver found for jdbc:sqlserver://msjdbctest.database.windows.net;database=jdbctest;loginTimeout=120;msiClientId=a0bc0c34-a024-4037-9368-9f904a008c36;authentication=ActiveDirectoryManagedIdentity;;encrypt=false;;trustServerCertificate=true;;trustManagerClass=com.microsoft.sqlserver.jdbc.ssl.trustmanager.TrustManagerWithConstructorArg;trustManagerConstructorArg=dummyString;
Raw output 
java.sql.SQLException: No suitable driver found for jdbc:sqlserver://msjdbctest.database.windows.net;database=jdbctest;loginTimeout=120;msiClientId=a0bc0c34-a024-4037-9368-9f904a008c36;authentication=ActiveDirectoryManagedIdentity;;encrypt=false;;trustServerCertificate=true;;trustManagerClass=com.microsoft.sqlserver.jdbc.ssl.trustmanager.TrustManagerWithConstructorArg;trustManagerConstructorArg=dummyString;
	at com.microsoft.sqlserver.jdbc.ssl.trustmanager.CustomTrustManagerTest.testWithTrustManagerConstructorArg(CustomTrustManagerTest.java:50)
View more details on Azure Pipelines