Error: "No suitable driver found for" When testing sdm_ds in JasperReport server 7.x

Products

• CA Service Desk Manager
• CA Service Management - Service Desk Manager

Issue/Introduction

The following error appears after testing sdm_ds in JasperReport server 7.x

Caused by: java.sql.SQLException: No suitable driver found for jdbc:sdm:bop:@<SDM Server>:2100;impersonateUserUuid=<contact UUID>
 at java.sql.DriverManager.getConnection(DriverManager.java:689)
 at java.sql.DriverManager.getConnection(DriverManager.java:247)
 at org.apache.commons.dbcp.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:75)
 at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.JdbcDriverManagerConnectionFactory.createConnection(JdbcDriverManagerConnectionFactory.java:36)
 at org.apache.commons.dbcp.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:582)
 at org.apache.commons.pool.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:1148)
 at org.apache.commons.dbcp.PoolingDataSource.getConnection(PoolingDataSource.java:106)
 at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.TibcoDriverManagerImpl.unlockConnection(TibcoDriverManagerImpl.java:59)
 at com.jaspersoft.jasperserver.api.engine.jasperreports.service.impl.JdbcDataSourceService.createConnection(JdbcDataSourceService.java:56)
 ... 209 more
ERROR SecureExceptionHandlerImpl,http-nio-8081-exec-10:116 - jsexception.error.creating.connection

 

The connection works OK in JasperStudio.

The integration worked OK with no error messages.

 

 

Environment

Release : 17.3

Component : SDM - Reporting/BOXI/JasperSoft

Cause

IPv4 is being used in the environment

Resolution

In IPv4 environment:  Add the following option to the jasper properties:

-Djava.net.preferIPv4Stack=true 

You would need to click on jasperreportsTomcatw.exe under C:\Jaspersoft\jasperreports-server-7.9.0\apache-tomcat\bin (or similar path) > Java tab> Java Options > Add the properties in this section.

Example:

Restart jasper services and test the connection.

 

In IPv6 environment:

Go to NX.env > @NX_PROTOCOL_ONLY=MIXED > Restart SDM services