Cannot bring up DevTest Portal with error "Schema export unsuccessful java.sql.SQLException: No suitable driver found"

book

Article ID: 141179

calendar_today

Updated On:

Products

CLOUDTEST CA Application Test CA Cloud Test Mobile MOBILECLOUD Service Virtualization

Issue/Introduction

Installed product on linux server (RHE 7.7).

Started IAM, Dashboard, Registry OK

Then trying to start Portal

Expected result:

Portal starts

Current result:

Portal do not start and portal-grails.log shows:

"2019-12-03 09:50:51,983Z (10:50) [Thread-17] ERROR org.hibernate.tool.hbm2ddl.SchemaExport - HHH000231: Schema export unsuccessful
java.sql.SQLException: No suitable driver found for jdbc:h2:mem:prodDb;MVCC=TRUE;LOCK_TIMEOUT=10000;DB_CLOSE_ON_EXIT=FALSE"

h2-1.4.178.jar is present in lib/dradis folder and also in /webserver/phoenix/phoenix-10.5.0/WEB-INF/lib

 

Cause

The cause for this error in Portal log is because portal couldn't communicate with Registry as it was not started properly. 

The issue was Registry component not started properly as it was not able to connect to the external DB configured in site.properties file and gave below error:

- java.sql.SQLException: Connections could not be acquired from the underlying database! 

Environment

Release : 10.5

Component : CA Service Virtualization

Resolution

As seen the issue was actually with Registry component not started properly as it was not able to connect to the external DB configured in site.properties file and gave below error:

- java.sql.SQLException: Connections could not be acquired from the underlying database! 

We did below two changes:

- In the site.properties

    -> set lisadb.internal.enabled=false

    - > gave the plain text password

We stopped all DevTest components, renamed logs folder and restarted all the components and could see that Registry started and picked up external DB and Portal also started and came up fine in the browser. 


Additional Information


To make sure that EDB has also picked up the given External DB, in the EDB console, hover the mouse over DB icon at the top-right icon and see the DB details. If it is using Derby then stop EDB, set/uncomment below property in dradis.properties file and restart. 

dradis.db.internal.enabled=false