Identityiq 404 error

IdentityIQ (IIQ) IIQ Discussion and Questions
1

Hello Sailor,

I am installing fresh iiq8.4 but unable to login,
able to connect to iiq console and able to see the tomcat home page is working.

but unable to go ahead, in the logs of tomcat error for identityiq.

attaching the logs below

22-Jul-2025 11:14:49.583 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [E:\SailPoint\Tomcat 9.0.106\webapps\identityiq]

Jul 22, 2025 11:20:06 AM org.apache.catalina.core.StandardContext listenerStart

SEVERE: Exception sending context initialized event to listener instance of class [sailpoint.web.StartupContextListener]

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'systemStarter' defined in class path resource [iiqBeans.xml]: Invocation of init method failed; nested exception is sailpoint.tools.GeneralException: Unable to start activemq connection. Make sure the broker is available and ready to receive messages.

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1799)

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:594)

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:516)

at org.springframework.beans.factory.support.AbstractBeanFactory.lambda$doGetBean$0(AbstractBeanFactory.java:324)

at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:234)

at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:322)

at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202)

at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:311)

at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:202)

at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:897)

at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:879)

at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:551)

at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:144)

at org.springframework.context.support.ClassPathXmlApplicationContext.<init>(ClassPathXmlApplicationContext.java:85)

at sailpoint.spring.SpringStarter.start(SpringStarter.java:333)

at sailpoint.web.StartupContextListener.contextInitialized(StartupContextListener.java:91)

at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4059)

at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:4501)

at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:164)

at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:599)

at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:571)

at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:603)

at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1174)

at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:1883)

at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)

at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)

at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:76)

at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:118)

at org.apache.catalina.startup.HostConfig.deployDirectories(HostConfig.java:1085)

at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:470)

at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1579)

at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:312)

at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:109)

at org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:389)

at org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:336)

at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:776)

at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:721)

at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:164)

at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1203)

at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1193)

at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)

at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:76)

at java.base/java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:140)

at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:749)

at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:211)

at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:164)

at org.apache.catalina.core.StandardService.startInternal(StandardService.java:412)

at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:164)

at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:874)

at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:164)

at org.apache.catalina.startup.Catalina.start(Catalina.java:739)

at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.base/java.lang.reflect.Method.invoke(Method.java:566)

at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:345)

at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:476)

Caused by: sailpoint.tools.GeneralException: Unable to start activemq connection. Make sure the broker is available and ready to receive messages.

at sailpoint.messagebus.monitoring.impl.BrokerConnectionHealthChecker.checkHealthStatus(BrokerConnectionHealthChecker.java:44)

at sailpoint.environmentMonitoring.MonitoringUtil.checkModuleHealth(MonitoringUtil.java:187)

at sailpoint.server.Environment.start(Environment.java:463)

at sailpoint.server.SystemStarter.springInit(SystemStarter.java:59)

at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.base/java.lang.reflect.Method.invoke(Method.java:566)

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeCustomInitMethod(AbstractAutowireCapableBeanFactory.java:1925)

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods(AbstractAutowireCapableBeanFactory.java:1867)

at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean(AbstractAutowireCapableBeanFactory.java:1795)

... 56 more

Caused by: sailpoint.tools.GeneralException: Unable to start activemq connection. Make sure the broker is available and ready to receive messages.

at sailpoint.messagebus.impl.ActiveMQMessageService.startConnection(ActiveMQMessageService.java:409)

at sailpoint.messagebus.impl.ActiveMQMessageService.<init>(ActiveMQMessageService.java:94)

at sailpoint.messagebus.api.MessageServiceFactory.createMessageService(MessageServiceFactory.java:74)

at sailpoint.messagebus.monitoring.impl.BrokerConnectionHealthChecker.checkHealthStatus(BrokerConnectionHealthChecker.java:33)

... 66 more

Caused by: javax.jms.JMSException: Disposed due to prior exception

at org.apache.activemq.util.JMSExceptionSupport.create(JMSExceptionSupport.java:56)

at org.apache.activemq.ActiveMQConnection.syncSendPacket(ActiveMQConnection.java:1405)

at org.apache.activemq.ActiveMQConnection.ensureConnectionInfoSent(ActiveMQConnection.java:1488)

at org.apache.activemq.ActiveMQConnection.start(ActiveMQConnection.java:530)

at sailpoint.messagebus.impl.ActiveMQMessageService.startConnection(ActiveMQMessageService.java:395)

... 69 more

Caused by: org.apache.activemq.transport.TransportDisposedIOException: Disposed due to prior exception

at org.apache.activemq.transport.ResponseCorrelator.onException(ResponseCorrelator.java:125)

at org.apache.activemq.transport.TransportFilter.onException(TransportFilter.java:114)

at org.apache.activemq.transport.failover.FailoverTransport.propagateFailureToExceptionListener(FailoverTransport.java:1154)

at org.apache.activemq.transport.failover.FailoverTransport.doReconnect(FailoverTransport.java:1103)

at org.apache.activemq.transport.failover.FailoverTransport$2.iterate(FailoverTransport.java:151)

at org.apache.activemq.thread.PooledTaskRunner.runTask(PooledTaskRunner.java:133)

at org.apache.activemq.thread.PooledTaskRunner$1.run(PooledTaskRunner.java:48)

at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)

at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)

at java.base/java.lang.Thread.run(Thread.java:834)

Caused by: java.io.IOException: Wire format negotiation timeout: peer did not send his wire format.

at org.apache.activemq.transport.WireFormatNegotiator.oneway(WireFormatNegotiator.java:99)

at org.apache.activemq.transport.failover.FailoverTransport.restoreTransport(FailoverTransport.java:859)

at org.apache.activemq.transport.failover.FailoverTransport.doReconnect(FailoverTransport.java:1029)

... 6 more

22-Jul-2025 11:20:09.497 SEVERE [main] org.apache.catalina.core.StandardContext.startInternal One or more listeners failed to start. Full details will be found in the appropriate container log file

22-Jul-2025 11:20:09.497 SEVERE [main] org.apache.catalina.core.StandardContext.startInternal Context [/identityiq] startup failed due to previous errors

22-Jul-2025 11:20:09.716 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [identityiq] registered the JDBC driver [com.microsoft.sqlserver.jdbc.SQLServerDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

22-Jul-2025 11:20:09.716 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [identityiq] appears to have started a thread named [Log4j2-TF-3-Scheduled-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:

java.base@11.0.27/jdk.internal.misc.Unsafe.park(Native Method)

java.base@11.0.27/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:234)

java.base@11.0.27/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2123)

java.base@11.0.27/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1182)

java.base@11.0.27/java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:899)

java.base@11.0.27/java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1054)

java.base@11.0.27/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1114)

java.base@11.0.27/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)

java.base@11.0.27/java.lang.Thread.run(Thread.java:834)

22-Jul-2025 11:20:09.716 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [identityiq] appears to have started a thread named [Persistence Adapter Starting Thread] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:

java.base@11.0.27/java.lang.Thread.sleep(Native Method)

java.base@11.0.27/java.lang.Thread.sleep(Thread.java:339)

java.base@11.0.27/java.util.concurrent.TimeUnit.sleep(TimeUnit.java:446)

org.apache.activemq.store.jdbc.LeaseDatabaseLocker.doStart(LeaseDatabaseLocker.java:102)

org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:55)

org.apache.activemq.broker.LockableServiceSupport.preStart(LockableServiceSupport.java:104)

org.apache.activemq.util.ServiceSupport.start(ServiceSupport.java:54)

org.apache.activemq.broker.BrokerService.doStartPersistenceAdapter(BrokerService.java:675)

org.apache.activemq.broker.BrokerService$1.run(BrokerService.java:645)

22-Jul-2025 11:20:09.732 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [identityiq] appears to have started a thread named [Broker Starting Thread] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:

java.base@11.0.27/java.lang.Object.wait(Native Method)

java.base@11.0.27/java.lang.Object.wait(Object.java:328)

org.apache.activemq.broker.BrokerService$2.run(BrokerService.java:714)

22-Jul-2025 11:20:09.732 WARNING [main] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [identityiq] appears to have started a thread named [ActiveMQ InactivityMonitor ReadCheckTimer] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:

java.base@11.0.27/java.lang.Object.wait(Native Method)

java.base@11.0.27/java.util.TimerThread.mainLoop(Timer.java:553)

java.base@11.0.27/java.util.TimerThread.run(Timer.java:506)

22-Jul-2025 11:20:09.732 SEVERE [main] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [identityiq] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@4bda62ab]) and a value of type [sailpoint.api.Meter.MeterSet] (value [sailpoint.api.Meter$MeterSet@41d9a166]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.

22-Jul-2025 11:20:09.747 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [E:\SailPoint\Tomcat 9.0.106\webapps\identityiq] has finished in [320,164] ms

22-Jul-2025 11:20:09.747 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [E:\SailPoint\Tomcat 9.0.106\webapps\manager]

22-Jul-2025 11:20:09.826 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [E:\SailPoint\Tomcat 9.0.106\webapps\manager] has finished in [79] ms

22-Jul-2025 11:20:09.826 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deploying web application directory [E:\SailPoint\Tomcat 9.0.106\webapps\ROOT]

22-Jul-2025 11:20:09.872 INFO [main] org.apache.catalina.startup.HostConfig.deployDirectory Deployment of web application directory [E:\SailPoint\Tomcat 9.0.106\webapps\ROOT] has finished in [46] ms

22-Jul-2025 11:20:09.872 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8080"]

22-Jul-2025 11:20:09.904 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in [321012] milliseconds

Kindly assist on this, how to resolve this

2

Hi @Riyazuddin99

did you import init.xml and init-lcm.xml from iiq console?

try restarting application server.

3

I see following errors:
Threads are going to be renewed over time to try and avoid a probable memory leak.

but failed to unregister it when the web application was stopped.
To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

This is very likely to create a memory leak.

I have observed these errors in my local instance:

actions:

  1. upgrading to 8.4p2 will resolve these errors.

delete ActiveMQ related details from iiq.properties then restart the application.

4

yes, i did imported them.

and iiq console is working fine

5

why this issue.
because, I tried the same in the sandbox it’s working any issue.

but in the dev envi is giving me this error.

6

Hi @Riyazuddin99

Could you please try to restart application serve.

  1. stop application server.
  2. delete temp and work folder.
  3. start the application server.

similar issues reported: the solution is: latest patch 8.4p2

Tomcat automatically shut down for SailPoint 8.4 after the upgrade
Upgrade 8.2 to 8.3 IIQ - #12 by pravin_ranjan

7

Hello @pattabhi ,

I tried but no luck,

still same issue.

image
image1861×655 71.2 KB

not why memory lead on fresh installation.

but tomcat and iiq console is working fine

8

The best practice suggests you to upgrade to latest patch especially over IIQ 8.4 because there are fixes around memory leaks which were addressed.

reference link:
https://community.sailpoint.com/t5/IdentityIQ-Articles/What-s-New-in-IdentityIQ-8-4/ta-p/240336

image
image1387×202 34 KB

Failing to upgrade to IIQ 8.4
9

Which db are you using?
From services if using MYSQL check whether its running or not
Run this and try again

10

Hello @uditsahntl01 ,

I am using mssql database,
and the database is up and running.

if it was anything to database, i believe then iiq console will also fail to connect.

Thanks

11

Hello @Riyazuddin99 Could you please tell me the database names for the Sandbox and Development environments?

3 Likes
12

Hi @Riyazuddin99

Did you get chance to try out the following suggestion?

remove/delete following section from iiq.properties then restart application server once.

# These settings are for the activemq broker.  At this time this should remain
# set to type activemq. This is only needed for running an embedded message
# broker within IdentityIQ, and is ignored when the message broker is external
messageServiceFactory.type=activemq
activeMQMessageServiceManager.brokerUri=tcp://0.0.0.0:61616?transport.trace=true&transport.soTimeout=10000
activeMQMessageServiceManager.activemqLocker=org.apache.activemq.store.jdbc.LeaseDatabaseLocker
# ActiveMQ Broker System Usage limit sizing in Megabytes
activeMQMessageServiceManager.memoryLimit=1024
activeMQMessageServiceManager.storeLimit=100000
activeMQMessageServiceManager.tempLimit=50000

I have faced same issue in my local setup, which was resolved automatically by deploying latest patch 8.4p2

13

Hello @santhirajumunganda ,

This is Development environments.

14

Could you please share the iiq.properties file?

15

Hello Everyone,

the issue got fixed when added
java_opt=noBroker

in the java properties when was able to login from the UI.
as root cause of this might be created due to the messaging configuration issue.

Thanks all for your support and input towards resolving the issue

Riyaz

16

I am getting the same error. Can you please assist with how you sorted it out? I am new in this space

IIQ error2
IIQ error21663×587 58.6 KB

17

what are you error you are getting in the loggers files.

18

Hi @sandy_2025 ,
Could you try using the tomcat server of version 9.

19

sure, I will try with tomcat 9. Thanks!

20

@Riyazuddin99 Catalina logs

image
image1787×588 71.2 KB