After applying SOI 4.2 CU2 Manager unable to connect to Database


Article ID: 223168


Updated On:


CA Service Operations Insight (SOI)


After applying SOI 4.2 CU2 Manager unable to connect to Database

soimgr-debug.log show the following message

2021-08-03 15:58:34,120 FATAL [ServletInit] connection.ConnectionProviderFactory.newConnectionProvider(76)  - Could not instantiate connection provider
java.lang.ClassCastException: cannot be cast to org.hibernate.connection.ConnectionProvider
 at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(
 at org.hibernate.connection.ConnectionProviderFactory.newConnectionProvider(
 at org.hibernate.cfg.SettingsFactory.createConnectionProvider(
 at org.hibernate.cfg.SettingsFactory.buildSettings(
 at org.hibernate.cfg.Configuration.buildSettings(
 at org.hibernate.cfg.Configuration.buildSessionFactory(
 at com.aprisma.util.thread.JobQueue.runJobThread(
 at com.aprisma.util.thread.JobQueue.access$400(
 at com.aprisma.util.thread.JobQueue$
2021-08-03 15:58:34,120 INFO  [ServletInit] ?.?(?)  - Manager initialization failed [count=2]. Will try again after 15 seconds.


Release : 4.2

Component : Service Operations Insight (SOI) Manager


For the original issue after installing CU2, I found the jar file that was causing the error.

For some unknown reason, the never got removed after installing CU2.

CU2 no longer need this jar file. To fix this error, you need to remove/delete /soi/tomcat/lib/