Unable to access IDM console

[Girish Chandra]

Hi,

IDM console not opening after entering admin credentials. We have deployed on Jboss server in windows environment.

IDM is configured in siteminder and DB is MS SQL.

IDM--12.6.2

Jboss--5.1.0

we are getting below exceptions in server log.

DEPLOYMENTS MISSING DEPENDENCIES:
  Deployment "jboss.j2ee:module="iam_im_identityminder_ejb.jar",service=EjbModule" is missing the following dependencies:
    Dependency "jboss.web.deployment:war=/iam/im" (should be in state "Create", but is actually in state "Configured")
  Deployment "jboss.messaging.connectionfactory:service=ClusterPullConnectionFactory" is missing the following dependencies:
    Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "**ERROR**")
  Deployment "jboss.messaging.connectionfactory:service=ClusteredConnectionFactory" is missing the following dependencies:
    Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "**ERROR**")
  Deployment "jboss.messaging.connectionfactory:service=ConnectionFactory" is missing the following dependencies:
    Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "**ERROR**")
  Deployment "jboss.messaging.connectionfactory:service=wpConnectionFactory" is missing the following dependencies:
    Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "**ERROR**")
  Deployment "jboss.messaging.destination:name=DLQ,service=Queue" is missing the following dependencies:
    Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "**ERROR**")
  Deployment "jboss.messaging.destination:name=ExpiryQueue,service=Queue" is missing the following dependencies:
    Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "**ERROR**")
  Deployment "jboss.messaging.destination:name=iam.im.jms.queue.RuntimeStatusDetailQueue,service=Queue" is missing the following dependencies:
    Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "**ERROR**")
  Deployment "jboss.messaging.destination:name=iam.im.jms.queue.com.netegrity.ims.msg.queue,service=Queue" is missing the following dependencies:
    Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "**ERROR**")
  Deployment "jboss.messaging.destination:name=iam.im.jms.queue.wpEventQueue,service=Queue" is missing the following dependencies:
    Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "**ERROR**")
  Deployment "jboss.messaging.destination:name=iam.im.jms.queue.wpServAutoActQueue,service=Queue" is missing the following dependencies:
    Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "**ERROR**")
  Deployment "jboss.messaging.destination:name=iam.im.jms.queue.wpUtilQueue,service=Queue" is missing the following dependencies:
    Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "**ERROR**")
  Deployment "jboss.messaging.destination:name=iam.im.jms.topic.ServerCommandTopic,service=Topic" is missing the following dependencies:
    Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "**ERROR**")
  Deployment "jboss.messaging.destination:name=iam_im AnalyticsNotificationQueue,service=Queue" is missing the following dependencies:
    Dependency "jboss.messaging:service=PostOffice" (should be in state "Create", but is actually in state "**ERROR**")
  Deployment "jboss.web.deployment:war=/iam/im" is missing the following dependencies:
    Dependency "jboss.messaging.destination:name=iam.im.jms.topic.ServerCommandTopic,service=Topic" (should be in state "Create", but is actually in state "Configured")
  Deployment "jboss.web.deployment:war=/iam/immanage" is missing the following dependencies:
    Dependency "jboss.messaging.destination:name=iam.im.jms.topic.ServerCommandTopic,service=Topic" (should be in state "Create", but is actually in state "Configured")

ERROR [org.jboss.resource.adapter.jms.inflow.JmsActivation] (WorkManager(2)-2) Unable to reconnect org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@690d3810(ra=org.jboss.resource.adapter.jms.JmsResourceAdapter@78d8248a destination=queue/iam/im/jms/queue/wpServAutoActQueue destinationType=javax.jms.Queue tx=true durable=false reconnect=10 provider=DefaultJMSProvider user=null maxMessages=1 minSession=1 maxSession=15 keepAlive=30000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQMaxResent=10)
javax.naming.NameNotFoundException: DLQ not bound

Please check and help us to resolve,

Regards,

Girish

[Michael Niebuhr]

Can I ask why you are attempting to deploy 12.6.2?     That version was released in 2013 and has not been supported since December 2017. 

May be related to this Redhat article? 
https://access.redhat.com/solutions/226713 

• In $JBOSS_HOME/server/$PROFILE/deploy/messaging/*-persistence-service.xml, comment out or remove the depends optional-attribute-name and the attributes as mentioned in the comment.

The current release of Identity Manager is 14.5 and regardless of the outcome of this issue you should begin work on deploying version 14.5, or begin planning on moving to Version 15 which should release this summer. 

[Girish Chandra]

Thanks for your reply.

This is already working application in our environment. When we tried to restart jboss, then issue coming in startup logs.

And application is not opening. We have not changed anything in any file.

We have same environment in two nodes, and issue coming on both nodes.

Issue started from this.

ERROR [org.jboss.messaging.util.ExceptionUtil] (main) org.jboss.messaging.core.jmx.MessagingPostOfficeService@18b4ac03 startService
java.lang.IllegalArgumentException: Cannot start post office since there is already a post office in the cluster with the same node id (5). Are you sure you have given each node a unique node id during installation?
    at org.jboss.messaging.core.impl.postoffice.MessagingPostOffice.start(MessagingPostOffice.java:372).

We have faced network outage, and tried to restart after network restored. Issue coming from since.

Can you please check and help us to resolve.

[Michael Niebuhr]

From this latest message there may be 2 conflicting clusters, but either way you are facing an issue at the Jboss level and should be working with your Jboss admin to clear up. 


I did a bit of googling on your error

This doc suggests restarting 'too quickly'
https://access.redhat.com/solutions/546643  
Maybe stop all nodes in the cluster and leave them down for a couple minutes before restarting them

This
https://developer.jboss.org/thread/158131
describes an issue with the cluster name

Michael
Broadcom Support