Tech Tip : CA Single Sign-On : R12.7 AdminUI getting hung when starting

Document created by Albert_Fernandez Employee on Apr 6, 2018Last modified by Albert_Fernandez Employee on Apr 6, 2018
Version 3Show Document
  • View in full screen mode

Question:

We have installed AdminUI along with other CA SSO components, and the installation finished successfully. After restarting the AdminUI we found that even though the process is getting started, it enters in a hung state, and we are unable to access AdminUI. We tried to re-register AdminUI but with no effect. In the server.log we can see the following lines when we start it:

2018-02-22 11:34:10,315 INFO  [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final
2018-02-22 11:34:10,475 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final
2018-02-22 11:34:10,544 INFO  [org.jboss.as] (MSC service thread 1-3) JBAS015899: WildFly 8.2.0.Final "Tweek" starting
2018-02-22 11:34:11,883 INFO  [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) JBAS014627: Attribute any-ipv4-address is deprecated, and it might be removed in future version!
2018-02-22 11:34:11,930 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found castylesr5.1.1.ear in deployment directory. To trigger deployment create a file called castylesr5.1.1.ear.dodeploy
2018-02-22 11:34:11,930 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found iam_siteminder.ear in deployment directory. To trigger deployment create a file called iam_siteminder.ear.dodeploy
2018-02-22 11:34:11,936 INFO  [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
2018-02-22 11:34:11,967 INFO  [org.xnio] (MSC service thread 1-1) XNIO version 3.3.0.Final
2018-02-22 11:34:11,973 INFO  [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.0.Final
2018-02-22 11:34:12,028 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 26) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
2018-02-22 11:34:12,069 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 46) JBAS015537: Activating WebServices Extension
2018-02-22 11:34:12,079 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 44) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique.
2018-02-22 11:34:12,079 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 43) JBAS013171: Activating Security Subsystem
2018-02-22 11:34:12,102 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
2018-02-22 11:34:12,126 INFO  [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.6.Final
2018-02-22 11:34:12,187 INFO  [org.jboss.as.security] (MSC service thread 1-4) JBAS013170: Current PicketBox version=4.0.21.Final
2018-02-22 11:34:12,197 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
2018-02-22 11:34:12,202 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 36) JBAS012615: Activated the following JSF Implementations: [main]
2018-02-22 11:34:12,205 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 30) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors
2018-02-22 11:34:12,247 INFO  [org.jboss.as.naming] (MSC service thread 1-3) JBAS011802: Starting Naming Service
2018-02-22 11:34:12,292 INFO  [org.jboss.as.connector.logging] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.9.Final)
2018-02-22 11:34:12,340 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) JBAS010417: Started Driver service with driver-name = h2
2018-02-22 11:34:12,345 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 45) JBAS017502: Undertow 1.1.0.Final starting
2018-02-22 11:34:12,380 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017502: Undertow 1.1.0.Final starting
2018-02-22 11:34:12,766 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 45) JBAS017527: Creating file handler for path /mypath/siteminder/adminui/welcome-content
2018-02-22 11:34:12,827 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017525: Started server default-server.
2018-02-22 11:34:12,829 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017531: Host default-host starting
2018-02-22 11:34:13,004 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 26) JBAS010403: Deploying JDBC-compliant driver class org.apache.derby.jdbc.EmbeddedDriver (version 10.6)
2018-02-22 11:34:13,006 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) JBAS010417: Started Driver service with driver-name = derbyEmbed
2018-02-22 11:34:13,043 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017519: Undertow HTTP listener default listening on /0.0.0.0:8080
2018-02-22 11:34:13,057 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 26) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 11.2)
2018-02-22 11:34:13,061 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010417: Started Driver service with driver-name = ojdbc
2018-02-22 11:34:13,151 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 48) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/mypath/siteminder/adminui/standalone/data/messagingjournal,bindingsDirectory=/mypath/siteminder/adminui/standalone/data/messagingbindings,largeMessagesDirectory=/mypath/siteminder/adminui/standalone/data/messaginglargemessages,pagingDirectory=/mypath/siteminder/adminui/standalone/data/messagingpaging)
2018-02-22 11:34:13,152 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 48) HQ221006: Waiting to obtain live lock
2018-02-22 11:34:13,175 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 26) JBAS010403: Deploying JDBC-compliant driver class com.microsoft.sqlserver.jdbc.SQLServerDriver (version 4.0)
2018-02-22 11:34:13,187 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) JBAS010417: Started Driver service with driver-name = sqljdbc
2018-02-22 11:34:13,200 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 48) HQ221013: Using NIO Journal
2018-02-22 11:34:13,449 INFO  [io.netty.util.internal.PlatformDependent] (ServerService Thread Pool -- 48) Your platform does not provide complete low-level API for accessing direct buffers reliably. Unless explicitly requested, heap buffer will always be preferred to avoid potential system unstability.
2018-02-22 11:34:13,483 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 48) HQ221043: Adding protocol support CORE
2018-02-22 11:34:13,488 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 48) HQ221043: Adding protocol support AMQP
2018-02-22 11:34:13,490 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 48) HQ221043: Adding protocol support STOMP
2018-02-22 11:34:13,563 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
2018-02-22 11:34:13,564 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:/iam/siteminder/jdbc/jdbc/archive]
2018-02-22 11:34:13,564 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) JBAS010400: Bound data source [java:/iam/siteminder/jdbc/jdbc/WPDS]
2018-02-22 11:34:13,595 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory /mypath/siteminder/adminui/standalone/deployments
2018-02-22 11:34:13,596 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:/iam/siteminder/jdbc/jdbc/idm]
2018-02-22 11:34:13,596 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:/iam/siteminder/jdbc/jdbc/objectstore]
2018-02-22 11:34:13,606 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:/iam/siteminder/jdbc/auditDbDataSource]
2018-02-22 11:34:13,651 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 48) HQ221034: Waiting to obtain live lock
2018-02-22 11:34:13,651 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 48) HQ221035: Live Server Obtained live lock
2018-02-22 11:34:13,834 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) JBAS017519: Undertow HTTPS listener https listening on /0.0.0.0:8443
2018-02-22 11:34:14,007 INFO  [org.jboss.messaging] (MSC service thread 1-1) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor acceptor
2018-02-22 11:34:14,008 INFO  [org.jboss.messaging] (MSC service thread 1-2) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor-throughput acceptor
2018-02-22 11:34:14,014 INFO  [org.jboss.ws.common.management] (MSC service thread 1-3) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.3.2.Final
2018-02-22 11:34:14,063 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 48) HQ221020: Started Netty Acceptor version unknown 0.0.0.0:5455
2018-02-22 11:34:14,065 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 48) HQ221020: Started Netty Acceptor version unknown 0.0.0.0:5445
2018-02-22 11:34:14,067 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 48) HQ221007: Server is now live
2018-02-22 11:34:14,067 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 48) HQ221001: HornetQ Server version 2.4.5.FINAL (Wild Hornet, 124) [4e6942e3-17c4-11e8-b7c3-df8e04f981a3]
2018-02-22 11:34:14,070 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 48) HQ221003: trying to deploy queue jms.queue.iam.siteminder.jms.queue.com.netegrity.ims.msg.queue
2018-02-22 11:34:14,159 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 48) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/iam/siteminder/jms/queue/com.netegrity.ims.msg.queue
2018-02-22 11:34:14,159 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 48) JBAS011601: Bound messaging object to jndi name queue/iam/siteminder/jms/queue/com.netegrity.ims.msg.queue
2018-02-22 11:34:14,169 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 55) HQ221003: trying to deploy queue jms.queue.iam.siteminder.jms.queue.wpUtilQueue
2018-02-22 11:34:14,181 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 55) JBAS011601: Bound messaging object to jndi name queue/iam/siteminder/jms/queue/wpUtilQueue
2018-02-22 11:34:14,181 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 55) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/iam/siteminder/jms/queue/wpUtilQueue
2018-02-22 11:34:14,192 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 57) HQ221003: trying to deploy queue jms.topic.iam.siteminder.jms.topic.ServerCommandTopic
2018-02-22 11:34:14,199 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-2) JBAS010406: Registered connection factory java:/JmsXA
2018-02-22 11:34:14,231 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 57) JBAS011601: Bound messaging object to jndi name topic/iam/siteminder/jms/topic/ServerCommandTopic
2018-02-22 11:34:14,232 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 57) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/iam/siteminder/jms/topic/ServerCommandTopic
2018-02-22 11:34:14,237 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221003: trying to deploy queue jms.queue.iam.siteminder.jms.queue.wpServAutoActQueue
2018-02-22 11:34:14,260 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 58) JBAS011601: Bound messaging object to jndi name queue/iam/siteminder/jms/queue/wpServAutoActQueue
2018-02-22 11:34:14,260 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 58) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/iam/siteminder/jms/queue/wpServAutoActQueue
2018-02-22 11:34:14,264 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 56) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
2018-02-22 11:34:14,265 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 54) HQ221003: trying to deploy queue jms.queue.DLQ
2018-02-22 11:34:14,273 INFO  [org.hornetq.ra] (MSC service thread 1-2) HornetQ resource adaptor started
2018-02-22 11:34:14,273 INFO  [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-2) IJ020002: Deployed: file://RaActivatorhornetq-ra
2018-02-22 11:34:14,275 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-2) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
2018-02-22 11:34:14,282 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 54) JBAS011601: Bound messaging object to jndi name java:/jms/queue/DLQ
2018-02-22 11:34:14,282 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 53) HQ221003: trying to deploy queue jms.queue.iam.siteminder.jms.queue.wpEventQueue
2018-02-22 11:34:14,285 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 53) JBAS011601: Bound messaging object to jndi name queue/iam/siteminder/jms/queue/wpEventQueue
2018-02-22 11:34:14,285 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 53) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/iam/siteminder/jms/queue/wpEventQueue
2018-02-22 11:34:14,286 INFO  [org.hornetq.jms.server] (ServerService Thread Pool -- 52) HQ121005: Invalid "host" value "0.0.0.0" detected for "netty" connector. Switching to "myserverfqdn". If this new address is incorrect please manually configure the connector to use the proper one.
2018-02-22 11:34:14,287 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 52) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
2018-02-22 11:34:14,287 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 51) HQ221003: trying to deploy queue jms.queue.iam.siteminder.jms.queue.RuntimeStatusDetailQueue
2018-02-22 11:34:14,289 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 51) JBAS011601: Bound messaging object to jndi name queue/iam/siteminder/jms/queue/RuntimeStatusDetailQueue
2018-02-22 11:34:14,290 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 51) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/iam/siteminder/jms/queue/RuntimeStatusDetailQueue
2018-02-22 11:34:14,290 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 50) HQ221003: trying to deploy queue jms.queue.ExpiryQueue
2018-02-22 11:34:14,293 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 50) JBAS011601: Bound messaging object to jndi name java:/jms/queue/ExpiryQueue
2018-02-22 11:34:14,293 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 49) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/wpConnectionFactory
2018-02-22 11:34:14,294 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 49) JBAS011601: Bound messaging object to jndi name wpConnectionFactory
2018-02-22 11:34:14,294 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 49) JBAS011601: Bound messaging object to jndi name jms/wpConnectionFactory
2018-02-22 11:34:14,362 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
2018-02-22 11:34:14,362 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015954: Admin console is not enabled
2018-02-22 11:34:14,362 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.2.0.Final "Tweek" started in 4296ms - Started 248 of 302 services (104 services are lazy, passive or on-demand)

How can we solve this problem?

Environment:

Policy Server R12.7 on RHEL7
AdminUI R12.7 (on same box)

Answer:

This can happen when JBoss is not able to deploy the ear files needed due to not having enough permissions on the files. First, check if under your /siteminder/adminui/standalone/deployments folder you have the following files along with the .ear files:

iam_siteminder.ear
castylesr5.1.1.ear
iam_siteminder.ear.undeployed 
castylesr5.1.1.ear.undeployed 


If you have them, it means the JBoss scanner was not able to deploy them before, so stop AdminUI and ensure the user which is running AdminUI has enough permissions (W/R) over all the standalone folder tree. Then, remove the .undeployed files, leaving only the .ear files in the folder:

castylesr5.1.1.ear
iam_siteminder.ear


And then, create the following files (you can use the "touch" command for this) to indicate to the JBoss scanner to deploy them:
# touch castylesr5.1.1.ear.dodeploy
# touch iam_siteminder.ear.dodeploy


So, in the folder you will see the following files along with the readme:
castylesr5.1.1.ear
iam_siteminder.ear
iam_siteminder.ear.dodeploy
castylesr5.1.1.ear.dodeploy


The next time you start AdminUI standalone, it will try to deploy them again, and the logs should show that with the following entries:
2018-02-23 10:49:24,265 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) JBAS015876: Starting deployment of "iam_siteminder.ear" (runtime-name: "iam_siteminder.ear") 
2018-02-23 10:49:24,267 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) JBAS015876: Starting deployment of "castylesr5.1.1.ear" (runtime-name: "castylesr5.1.1.ear") 
After that, AdminUI will start properly, and the extension of the files we created in the deployments folder will change from .dodeploy to .deployed to indicate the scanner that, and you are now able to access through the normal URL or to complete the registration process.


1 person found this helpful

Attachments

    Outcomes