Getting error for "The ActiveMQ JDBCAdapter class has not been supplied and b" while installing 8.4

Administration & Troubleshooting
1

Hi,

Doing fresh installation with below configuration.

SailPoint 8.4

MSSQL 2019

Appche tomcat.

I am able to go in IIQ console, but after strating the webserver, getting below error.

18-Jan-2024 17:08:13.389 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [C:\apache-tomcat-9.0.73\webapps\host-manager] has finished in [125] ms
18-Jan-2024 17:08:13.389 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [C:\apache-tomcat-9.0.73\webapps\IIQ]
2024-01-18T17:08:54,154 ERROR main sailpoint.messagebus.impl.ActiveMQMessageServiceManager:120 - The ActiveMQ JDBCAdapter class has not been supplied and broker setup is unable to continue.
2024-01-18T17:08:54,279 ERROR main sailpoint.messagebus.impl.ActiveMQMessageServiceManager:217 - There has been an error when setting up the broker persistence.
sailpoint.tools.GeneralException: The ActiveMQ JDBCAdapter class has not been supplied and broker setup is unable to continue.
at sailpoint.messagebus.impl.ActiveMQMessageServiceManager.startupBrokerService(ActiveMQMessageServiceManager.java:121) ~[identityiq.jar:8.4 Build bdd0ed4de58-20230919-192552]
at sailpoint.messagebus.impl.ActiveMQMessageServiceManager.start(ActiveMQMessageServiceManager.java:96) ~[identityiq.jar:8.4 Build bdd0ed4de58-20230919-192552]
at sailpoint.server.EmbeddedBrokerService.start(EmbeddedBrokerService.java:53) ~[identityiq.jar:8.4 Build bdd0ed4de58-20230919-192552]
at sailpoint.server.Servicer.startStartupService(Servicer.java:384) ~[identityiq.jar:8.4 Build bdd0ed4de58-20230919-192552]
at sailpoint.server.Servicer.configureStartup(Servicer.java:367) ~[identityiq.jar:8.4 Build bdd0ed4de58-20230919-192552]
at sailpoint.server.Environment.start(Environment.java:455) ~[identityiq.jar:8.4 Build bdd0ed4de58-20230919-192552]
at sailpoint.server.SystemStarter.springInit(SystemStarter.java:59) ~[identityiq.jar:8.4 Build bdd0ed4de58-20230919-192552]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]
at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) ~[?:?]
at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]
at java.lang.reflect.Method.invoke(Method.java:568) ~[?:?]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeCustomInitMethod(AbstractAutowireCapableBeanFactory.java:1925) ~[spring-beans-5.2.24.RELEASE.jar:5.2.24.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1867) ~[spring-beans-5.2.24.RELEASE.jar:5.2.24.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1795) ~[spring-beans-5.2.24.RELEASE.jar:5.2.24.RELEASE]
at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:594) ~[spring-beans-5.2.24.RELEASE.jar:5.2.24.RELEASE]

Thanks

2

Have you updated the iiq.properties file for the access history database configuration as well along with identityiq and identityiPlugin database?

3

Yes, I updated identityiqplugin and identityiqah details in iiq properties file. please find the attached.

Also i am able to run IIQ console, but tomcat is not getting started.
iiq.xml (16.9 KB)

4

@bilaldalvi   Could you please help me on above issue?

5

Issue has been fixed, activemqJdbcAdapter property was not updated in iiq.properties file.

6

Please uncomment below line and restart app server

activeMQMessageServiceManager.activemqJdbcAdapter=org.apache.activemq.store.jdbc.adapter.TransactJDBCAdapter

7

Thankyou for replying @bkshah1611 this will help. @ thankyou for posting this

8

@VipinVerma1   @bkshah1611   @dheerajk27

On the below line, which IP should we post in place of 0.0.0.0. Will it be the Tomcat server hosted IP? Or the Database hosted box IP or the access history Database hosted IP? All three are seperate for us. I am facing the same issue.

activeMQMessageServiceManager.brokerUri=tcp://0.0.0.0:61616?transport.trace=true&transport.soTimeout=10000

9

Update 0.0.0.0 with you localhost or hostname on which IIQ is deployed.