Sailpoint IIQ 8.4 ActiveMQ issue

IdentityIQ (IIQ) IIQ Discussion and Questions
1

Hello, everyone!

I’m currently working with SailPoint IdentityIQ 8.4 and attempting to use the embedded ActiveMQ broker for internal messaging within the application. However, I’m encountering an error during startup that indicates the broker is not available to receive messages. Here’s a summary of my setup and the issues I’m facing:

Issue Summary

  1. When I start IdentityIQ, it fails to connect to the embedded ActiveMQ broker and throws an error saying, “make sure the broker is available and ready to receive messages.”
  2. I’ve verified that no other service is running on port 61616.
  3. I don’t have an external ActiveMQ instance configured and would prefer to use the embedded broker for simplicity.
2

Welcome @2022Sandeep123!

When I first started using 8.4, I realized I copied my iiq.properties file from 8.3 where it did not have references to activeMQ.

Please pull the iiq.properties file from the binary and update it with your configurations as your new baseline.

1 Like
3

Thanks for the response.

I was trying to setup the fresh instance and kept ending up with the tomcat server shuting down.

1 Like
4

When I start a new installation, my first verification is establishing a successful connection using iiq console. That way you can eliminate any issues relating to url/port/passwords to your database. If that connection is successful, often times the app server will start up.

1 Like
5

Thats the same way I always follow and always prefer to use the console. Console is working fine however this because of this accessHistory feature in sailpoint 8.4 I m ending up with errors.

6

If you can login successfully to the iiq console. You can issue some test commands to your embedded ActiveMQ.

./iiq console

> bus enable
System Property 'messageBusEnabled' set to 'true'

> bus test --queue test 1

*************************************
     Message Count:                 1
             Queue:              test
            Phased:             false
     Dequeue Delay:              0 ms
   Dequeue Timeout:           5000 ms
     Enqueue Delay:              0 ms

 messageBusEnabled:              true
*************************************

Emptied 1 old messages from queue
Sent message 1: DummyMessage00000000, broker: tcp://localhost:61616
Sent message count : 1 out of 1
Received message 1 : DummyMessage00000000 from broker tcp://localhost:61616

***********************************************
Elapsed time: 1085 ms 
Success: Received 1 out of expected 1
***********************************************
1 Like
7

Was able to run the command bus test --queue test 1 and got the result as you posted. However after this again getting the same error unable to connect to ActiveMQ. Make sure the broker is available and ready to receive message

8

You mentioned that you weren’t able to start IIQ. You really should be able to start your instance without the embedded ActiveMQ enabled. You can disable the bus start up by going doing this in the console.

./iiq console

> bus disable

Afterwards, your server should be able to start. You technically don’t have to have the bus running to use 8.4, but you just won’t have Access History populated.

If that does work, perhaps you can check your iiq.properties file for this entry (it’s supposed to be 0.0.0.0 for the embedded):

# 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

The other reference to the embedded server is a configuration object called MessageBusConfiguration. That should have an entry similar to:

<entry key="clientConnectionString" value="failover:(tcp://localhost:61616)?initialReconnectDelay=10&amp;maxReconnectAttempts=10&amp;randomize=false&amp;startupMaxReconnectAttempts=10&amp;jms.watchTopicAdvisories=false&amp;jms.redeliveryPolicy.initialRedeliveryDelay=900000&amp;jms.redeliveryPolicy.redeliveryDelay=900000"/>

9

This is my configuration and still IIQ server does not start up.

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

Do you think replacing the iiq.properties file from 8.3 will work out ?

10

No it wouldn’t because it would be missing references to the Access History database.

Did you modify your current iiq.properties file from the extracted war file?

11

No I did not modiy anything

12

Hi Sandeep,

Can you share your iiq.properties file
Also restart your server some times you will not get embedded active mq broker status by doing net stat -ano|grep 61616

Thank you
Vidya Prakash

13

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

14

For now I disabled messageBroker from iiq console and sailpoint is up.

iiq console

bus disable

start tomcat

15

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.