New Identity Manager Environment throws' null pointer exception
Article ID: 244785
Updated On:
Products
Issue/Introduction
After deploying a fresh Identity Manager Websphere when accessing any tasks within IDM a Java.lang.NullPointerException is thrown:
The SystemOut.log shows issues with the Messaging BUS not being found:
[6/27/22 9:58:38:036 EDT] 00000073 SystemOut O 09:58:38,036 INFO [ims.Main] * Startup Step 11 : Attempting to start RuntimeStatusDetailService
[6/27/22 9:58:38:054 EDT] 00000073 SystemOut O 09:58:38,053 INFO [ims.Main] auto-acknowledge mode is applied to runtime status message queue
[6/27/22 9:58:38:060 EDT] 00000073 SibMessage W [:] CWSIK0015E: The destination iam_im-RuntimeStatusDetailQueue was not found on messaging engine <was-idm-node-1.was-idm-server-1-iam_im-IMSBus>.
[6/27/22 9:58:38:062 EDT] 00000073 SibTr$Suppres I CWSIU0005I: Future occurences of "CWSIK0015E: The destination iam_im-RuntimeStatusDetailQueue was not found on messaging engine <was-idm-node-1.was-idm-server-1-iam_im-IMSBus>.." will be suppressed for the next 30 minutes.
[6/27/22 9:58:38:067 EDT] 00000073 SystemOut O 09:58:38,067 ERROR [ims.RuntimeStatusDetail] javax.jms.InvalidDestinationException: CWSIA0062E: Failed to create a MessageProducer for queue://iam_im-RuntimeStatusDetailQueue?busName=iam_im-IMSBus
[6/27/22 9:58:38:083 EDT] 00000073 SystemOut O 09:58:38,083 INFO [ims.Main] * Startup Step 22 : Attempting to start EventService
...
from resource iam/im/jms/factory/javax.jms.QueueConnectionFactory was used within a local transaction containment boundary.
[6/27/22 9:58:38:092 EDT] 00000073 SystemOut O 09:58:38,092 INFO [ims.Main] auto-acknowledge mode is applied to event message queue
[6/27/22 9:58:38:094 EDT] 00000073 SibMessage W [:] CWSIK0015E: The destination iam_im-IMSEvents was not found on messaging engine <was-idm-node-1.was-idm-server-1-iam_im-IMSBus>.
[6/27/22 9:58:38:095 EDT] 00000073 SibTr$Suppres I CWSIU0005I: Future occurences of "CWSIK0015E: The destination iam_im-IMSEvents was not found on messaging engine <was-idm-node-1.was-idm-server-1-iam_im-IMSBus>." will be suppressed for the next 30 minutes.
[6/27/22 9:58:38:096 EDT] 00000073 SystemOut O 09:58:38,096 ERROR [ims.tmt.events] javax.jms.InvalidDestinationException: CWSIA0062E: Failed to create a MessageProducer for queue://iam_im-IMSEvents?busName=iam_im-IMSBus
[6/27/22 9:58:38:097 EDT] 00000073 SystemOut O 09:58:38,096 INFO [ims.Main] * Startup Step 23 : Attempting to start AdminService
[6/27/22 9:58:38:098 EDT] 00000073 SystemOut O 09:58:38,098 INFO [ims.Main] * Startup Step 24 : Attempting to start GeneralMonitorAdmin
[6/27/22 9:58:38:099 EDT] 00000073 SystemOut O 09:58:38,099 INFO [ims.Main] * Startup Step 25 : Attempting to start StatusNotificationService
[6/27/22 9:58:38:109 EDT] 00000073 SibMessage W [:] CWSIK0015E: The destination iam_im-StatusNotificationsQueue was not found on messaging engine <was-idm-node-1.was-idm-server-1-iam_im-IMSBus>
[6/27/22 9:58:38:110 EDT] 00000073 SibTr$Suppres I CWSIU0005I: Future occurences of "CWSIK0015E: The destination iam_im-StatusNotificationsQueue was not found on messaging engine <was-idm-node-1.was-idm-server-1-iam_im-IMSBus>." will be suppressed for the next 30 minutes.
[6/27/22 9:58:38:119 EDT] 00000073 SystemOut O 09:58:38,111 ERROR [im.provisioning.statusnotifications.StatusNotificationsJMSQueue] Failed to start Status Notifications JMS Queue StatusNotificationsQueue
javax.jms.InvalidDestinationException: CWSIA0062E: Failed to create a MessageProducer for queue://iam_im-StatusNotificationsQueue?busName=iam_im-IMSBus
at com.ibm.ws.sib.api.jms.impl.JmsMsgProducerImpl.<init>(JmsMsgProducerImpl.java:410) ~[com.ibm.ws.sib.server.jar:1.0.0]
at com.ibm.ws.sib.api.jms.impl.JmsQueueSenderImpl.<init>(JmsQueueSenderImpl.java:60) ~[com.ibm.ws.sib.server.jar:1.0.0]
Environment
Release : 14.4
Component :
Resolution
This issue indicates that Websphere was not able to complete its configuration. Manually creating the bus should resolve the problem.
Create the below Destinations(Buses > iam_im-IMSBus > Destinations) manually in websphere to resolve the issue:
iam_im-IMSEvents
iam_im-RuntimeStatusDetailQueue
iam_im-StatusNotificationsQueue
iam_im-wpEventQueue
iam_im-wpServAutoActQueue
iam_im-wpUtilQueue
If this does not resolve the issue please work with your Websphere admin and review the WebSphere documentation section:
https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/identity-manager/14-4/installing/install-on-websphere/install-websphere-application-server.html
Or manually deploy:
https://techdocs.broadcom.com/us/en/symantec-security-software/identity-security/identity-manager/14-4/installing/install-on-websphere/websphere-manual-ear-deployment.html
Feedback
