Symantec Access Management

Expand all | Collapse all

JBOSS failing to start when trying to start Admin UI

Jump to Best Answer
  • 1.  JBOSS failing to start when trying to start Admin UI

    Posted 07-25-2017 05:04 PM

    Siteminder 12.7
    OS : Linux 
    trying to start JBOSS bundled version for WAMUI using standalone scripts is failing providing below error. tried Re-register using XPSRegClient but unsuccessful. 
    (It was running earlier)

    JBoss Bootstrap Environment

    JBOSS_HOME: /app/CA/siteminder/adminui

    JAVA: /app/CA/siteminder/adminui/runtime/bin/java

     

    =========================================================================

    14:59:07,355 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.

     

    Thanks



  • 2.  Re: JBOSS failing to start when trying to start Admin UI

    Broadcom Employee
    Posted 07-26-2017 02:15 AM
    Hi,
    How do you start the JBoss Server and AdminUI ? Which command line ?
    Check also if SElinux is enable or not on both Policy Server and
    AdminUI machine
      # cat /selinux/enforce
    it should return 0
    Are both Policy Server and AdminUI running on the same machine ?
    Best Regards,
    Patrick


  • 3.  Re: JBOSS failing to start when trying to start Admin UI

    Posted 07-26-2017 10:08 AM

    use standalone.sh script to run the JBOSS, To get the AdminUI up and running.



  • 4.  Re: JBOSS failing to start when trying to start Admin UI

    Posted 07-26-2017 10:15 AM

    Policy Server and AdminUI running in same machine.



  • 5.  Re: JBOSS failing to start when trying to start Admin UI

    Posted 07-26-2017 02:53 AM

    It would be helpful if we can get a look at the server.log.

    The message you posted is a WARN, not ERROR.

    It is possible it may not be the cause why it does not startup.



  • 6.  Re: JBOSS failing to start when trying to start Admin UI

    Posted 07-26-2017 10:05 AM


    server.log
    [smuser@utlxa551 log]$ more server.log
    2017-07-26 08:03:13,279 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final
    2017-07-26 08:03:13,455 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final
    2017-07-26 08:03:13,524 INFO [org.jboss.as] (MSC service thread 1-4) JBAS015899: WildFly 8.2.0.Final "Tweek" starting
    2017-07-26 08:03:14,795 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!
    2017-07-26 08:03:14,890 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
    2017-07-26 08:03:14,890 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
    2017-07-26 08:03:14,903 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
    2017-07-26 08:03:14,942 INFO [org.xnio] (MSC service thread 1-2) XNIO version 3.3.0.Final
    2017-07-26 08:03:14,951 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.3.0.Final
    2017-07-26 08:03:14,988 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.6.Final
    2017-07-26 08:03:15,030 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 26) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
    2017-07-26 08:03:15,068 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 31) JBAS010280: Activating Infinispan subsystem.
    2017-07-26 08:03:15,077 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 pro
    cessors
    2017-07-26 08:03:15,110 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 46) JBAS015537: Activating WebServices Extension
    2017-07-26 08:03:15,124 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 45) JBAS017502: Undertow 1.1.0.Final starting
    2017-07-26 08:03:15,129 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.
    2017-07-26 08:03:15,130 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017502: Undertow 1.1.0.Final starting
    2017-07-26 08:03:15,132 INFO [org.jboss.as.security] (ServerService Thread Pool -- 43) JBAS013171: Activating Security Subsystem
    2017-07-26 08:03:15,139 INFO [org.jboss.as.security] (MSC service thread 1-1) JBAS013170: Current PicketBox version=4.0.21.Final
    2017-07-26 08:03:15,231 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem
    2017-07-26 08:03:15,236 INFO [org.jboss.as.connector.logging] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.9.Final)
    2017-07-26 08:03:15,286 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 36) JBAS012615: Activated the following JSF Implementations: [main]
    2017-07-26 08:03:15,399 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010417: Started Driver service with driver-name = h2
    2017-07-26 08:03:15,477 INFO [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service
    2017-07-26 08:03:15,770 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 45) JBAS017527: Creating file handler for path /app/CA/siteminder/adminui/welcome-content
    2017-07-26 08:03:15,782 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017525: Started server default-server.
    2017-07-26 08:03:15,870 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017531: Host default-host starting
    2017-07-26 08:03:16,016 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) JBAS017519: Undertow HTTP listener default listening on /0.0.0.0:8080
    2017-07-26 08:03:16,157 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)
    2017-07-26 08:03:16,171 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) JBAS010417: Started Driver service with driver-name = derbyEmbed
    2017-07-26 08:03:16,189 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 26) JBAS010403: Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 11.2)
    2017-07-26 08:03:16,194 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) JBAS010417: Started Driver service with driver-name = ojdbc
    2017-07-26 08:03:16,209 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=/app/CA/siteminder/adminui/standalone/data/messagingjournal,bindingsDirectory=/app/CA/siteminder/adminui/standalone/data/messagingbindings,largeMessagesDirectory=/app/CA/siteminder/admi
    nui/standalone/data/messaginglargemessages,pagingDirectory=/app/CA/siteminder/adminui/standalone/data/messagingpaging)
    2017-07-26 08:03:16,210 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 48) HQ221006: Waiting to obtain live lock
    2017-07-26 08:03:16,245 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 48) HQ221013: Using NIO Journal
    2017-07-26 08:03:16,291 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)
    2017-07-26 08:03:16,298 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-4) JBAS010417: Started Driver service with driver-name = sqljdbc
    2017-07-26 08:03:16,408 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.
    2017-07-26 08:03:16,444 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 48) HQ221043: Adding protocol support CORE
    2017-07-26 08:03:16,458 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 48) HQ221043: Adding protocol support AMQP
    2017-07-26 08:03:16,461 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 48) HQ221043: Adding protocol support STOMP
    2017-07-26 08:03:16,550 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 48) HQ221034: Waiting to obtain live lock
    2017-07-26 08:03:16,550 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 48) HQ221035: Live Server Obtained live lock
    2017-07-26 08:03:16,677 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
    2017-07-26 08:03:16,677 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:/iam/siteminder/jdbc/auditDbDataSource]
    2017-07-26 08:03:16,677 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:/iam/siteminder/jdbc/jdbc/WPDS]
    2017-07-26 08:03:16,677 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:/iam/siteminder/jdbc/jdbc/archive]
    2017-07-26 08:03:16,697 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:/iam/siteminder/jdbc/jdbc/objectstore]
    2017-07-26 08:03:16,698 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:/iam/siteminder/jdbc/jdbc/idm]
    2017-07-26 08:03:16,702 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) JBAS015012: Started FileSystemDeploymentService for directory /app/CA/siteminder/adminui/standalone/deployments
    2017-07-26 08:03:16,896 INFO [org.jboss.messaging] (MSC service thread 1-1) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor acceptor
    2017-07-26 08:03:16,904 INFO [org.jboss.messaging] (MSC service thread 1-2) JBAS011615: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor-throughput acceptor
    2017-07-26 08:03:16,919 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) JBAS017519: Undertow HTTPS listener https listening on /0.0.0.0:8443
    2017-07-26 08:03:17,136 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 48) HQ221020: Started Netty Acceptor version unknown 0.0.0.0:5455
    2017-07-26 08:03:17,194 INFO [org.jboss.ws.common.management] (MSC service thread 1-3) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.3.2.Final
    2017-07-26 08:03:17,199 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 48) HQ221020: Started Netty Acceptor version unknown 0.0.0.0:5445
    2017-07-26 08:03:17,214 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 48) HQ221007: Server is now live
    2017-07-26 08:03:17,214 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 48) HQ221001: HornetQ Server version 2.4.5.FINAL (Wild Hornet, 124) [2bbad2bf-720b-11e7-9f03-0f5d3924085c]
    2017-07-26 08:03:17,220 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 49) HQ221003: trying to deploy queue jms.queue.iam.siteminder.jms.queue.RuntimeStatusDetailQueue
    2017-07-26 08:03:17,320 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 49) JBAS011601: Bound messaging object to jndi name queue/iam/siteminder/jms/queue/RuntimeStatusDetailQueue
    2017-07-26 08:03:17,320 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 49) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/iam/siteminder/jms/queue/RuntimeStatusDe
    tailQueue
    2017-07-26 08:03:17,321 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 51) HQ221003: trying to deploy queue jms.queue.DLQ
    2017-07-26 08:03:17,323 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 51) JBAS011601: Bound messaging object to jndi name java:/jms/queue/DLQ
    2017-07-26 08:03:17,326 INFO [org.hornetq.jms.server] (ServerService Thread Pool -- 57) HQ121005: Invalid "host" value "0.0.0.0" detected for "netty" connector. Switching to "utlxa551". If this new address
    is incorrect please manually configure the connector to use the proper one.
    2017-07-26 08:03:17,344 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) JBAS010406: Registered connection factory java:/JmsXA
    2017-07-26 08:03:17,352 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 57) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/wpConnectionFactory
    2017-07-26 08:03:17,352 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 57) JBAS011601: Bound messaging object to jndi name wpConnectionFactory
    2017-07-26 08:03:17,352 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 57) JBAS011601: Bound messaging object to jndi name jms/wpConnectionFactory
    2017-07-26 08:03:17,353 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 52) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
    2017-07-26 08:03:17,353 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 58) HQ221003: trying to deploy queue jms.queue.ExpiryQueue
    2017-07-26 08:03:17,355 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 58) JBAS011601: Bound messaging object to jndi name java:/jms/queue/ExpiryQueue
    2017-07-26 08:03:17,356 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 53) JBAS011601: Bound messaging object to jndi name java:/ConnectionFactory
    2017-07-26 08:03:17,356 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 56) HQ221003: trying to deploy queue jms.queue.iam.siteminder.jms.queue.wpEventQueue
    2017-07-26 08:03:17,362 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 56) JBAS011601: Bound messaging object to jndi name queue/iam/siteminder/jms/queue/wpEventQueue
    2017-07-26 08:03:17,362 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 56) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/iam/siteminder/jms/queue/wpEventQueue
    2017-07-26 08:03:17,362 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 55) HQ221003: trying to deploy queue jms.queue.iam.siteminder.jms.queue.com.netegrity.ims.msg.queue
    2017-07-26 08:03:17,377 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/com.netegrity.i
    ms.msg.queue
    2017-07-26 08:03:17,378 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 55) JBAS011601: Bound messaging object to jndi name queue/iam/siteminder/jms/queue/com.netegrity.ims.msg.queue
    2017-07-26 08:03:17,378 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 54) HQ221003: trying to deploy queue jms.queue.iam.siteminder.jms.queue.wpUtilQueue
    2017-07-26 08:03:17,382 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 54) JBAS011601: Bound messaging object to jndi name queue/iam/siteminder/jms/queue/wpUtilQueue
    2017-07-26 08:03:17,382 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 54) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/iam/siteminder/jms/queue/wpUtilQueue
    2017-07-26 08:03:17,383 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 50) HQ221003: trying to deploy queue jms.topic.iam.siteminder.jms.topic.ServerCommandTopic
    2017-07-26 08:03:17,419 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 50) JBAS011601: Bound messaging object to jndi name topic/iam/siteminder/jms/topic/ServerCommandTopic
    2017-07-26 08:03:17,419 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 50) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/queue/iam/siteminder/jms/topic/ServerCommandTo
    pic
    2017-07-26 08:03:17,420 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 48) HQ221003: trying to deploy queue jms.queue.iam.siteminder.jms.queue.wpServAutoActQueue
    2017-07-26 08:03:17,435 INFO [org.hornetq.ra] (MSC service thread 1-1) HornetQ resource adaptor started
    2017-07-26 08:03:17,436 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-1) IJ020002: Deployed: file://RaActivatorhornet
    q-ra
    2017-07-26 08:03:17,438 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
    2017-07-26 08:03:17,441 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 48) JBAS011601: Bound messaging object to jndi name queue/iam/siteminder/jms/queue/wpServAutoActQueue
    2017-07-26 08:03:17,442 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/wpServAutoActQu
    eue
    2017-07-26 08:03:17,529 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
    2017-07-26 08:03:17,529 INFO [org.jboss.as] (Controller Boot Thread) JBAS015954: Admin console is not enabled
    2017-07-26 08:03:17,530 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: WildFly 8.2.0.Final "Tweek" started in 4532ms - Started 252 of 304 services (104 services are lazy, passive or on-demand)
    2017-07-26 08:03:44,322 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-1) JBAS010410: Unbound JCA ConnectionFactory [java:/JmsXA]
    2017-07-26 08:03:44,322 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017521: Undertow HTTPS listener https suspending
    2017-07-26 08:03:44,323 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017520: Undertow HTTPS listener https stopped, was bound to /0.0.0.0:8443
    2017-07-26 08:03:44,327 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017532: Host default-host stopping
    2017-07-26 08:03:44,332 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010409: Unbound data source [java:/iam/siteminder/jdbc/jdbc/objectstore]
    2017-07-26 08:03:44,332 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010409: Unbound data source [java:/iam/siteminder/jdbc/jdbc/idm]
    2017-07-26 08:03:44,332 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010409: Unbound data source [java:/iam/siteminder/jdbc/jdbc/WPDS]
    2017-07-26 08:03:44,333 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010409: Unbound data source [java:/iam/siteminder/jdbc/jdbc/archive]
    2017-07-26 08:03:44,333 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010409: Unbound data source [java:/iam/siteminder/jdbc/auditDbDataSource]
    2017-07-26 08:03:44,333 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011605: Unbound messaging object to jndi name java:/queue/iam/siteminder/jms/queue/RuntimeStatusDetailQueue
    2017-07-26 08:03:44,333 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-1) JBAS010409: Unbound data source [java:jboss/datasources/ExampleDS]
    2017-07-26 08:03:44,342 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 61) JBAS011605: Unbound messaging object to jndi name java:jboss/exported/jms/queue/iam/siteminder/jms/queue/RuntimeStatus
    DetailQueue
    2017-07-26 08:03:44,343 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010418: Stopped Driver service with driver-name = ojdbc
    2017-07-26 08:03:44,343 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010418: Stopped Driver service with driver-name = sqljdbc
    2017-07-26 08:03:44,345 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) JBAS010418: Stopped Driver service with driver-name = h2
    2017-07-26 08:03:44,357 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) JBAS010418: Stopped Driver service with driver-name = derbyEmbed
    2017-07-26 08:03:44,372 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 59) JBAS011605: Unbound messaging object to jndi name java:/queue/iam/siteminder/jms/queue/wpServAutoActQueue
    2017-07-26 08:03:44,383 INFO [org.hornetq.ra] (ServerService Thread Pool -- 70) HQ151003: HornetQ resource adaptor stopped
    2017-07-26 08:03:44,389 INFO [org.jboss.as.messaging] (ServerService Thread Pool -- 60) JBAS011605: Unbound messaging object to jndi name java:/topic/iam/siteminder/jms/topic/ServerCommandTopic
    2017-07-26 08:03:44,446 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 62) HQ221002: HornetQ Server version 2.4.5.FINAL (Wild Hornet, 124) [2bbad2bf-720b-11e7-9f03-0f5d3924085c] stopped
    2017-07-26 08:03:44,446 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017521: Undertow HTTP listener default suspending
    2017-07-26 08:03:44,447 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017520: Undertow HTTP listener default stopped, was bound to /0.0.0.0:8080
    2017-07-26 08:03:44,448 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017506: Undertow 1.1.0.Final stopping
    2017-07-26 08:03:44,457 INFO [org.jboss.as] (MSC service thread 1-1) JBAS015950: WildFly 8.2.0.Final "Tweek" stopped in 68ms



  • 7.  Re: JBOSS failing to start when trying to start Admin UI

    Broadcom Employee
    Posted 07-27-2017 02:39 AM

    Hi,

     

    As both AdminUI and Policy Server runs on the same machine, insure they don't run with the same user.

     

    Insure that the partition where /tmp and the adminui folder aren't full.

     

    Insure that the user which runs AdminUI has full permission on files and directories where the AdminUI is installed.

     

    I hope that helps,

     

    Patrick



  • 8.  Re: JBOSS failing to start when trying to start Admin UI

    Posted 01-26-2018 10:24 AM

    Hi,

     

    I am running into same problem with adminui 12.7 version. Jboss will not start up the normal workflow and get stuck at below lines.

     

    14:59:07,355 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.

     

    Is it resolved, please share the details how?

     

    Thanks.



  • 9.  Re: JBOSS failing to start when trying to start Admin UI

    Broadcom Employee
    Posted 01-29-2018 07:23 AM

    Hi Psoni2,

     

    Put further logs and traces on the AdminUI to get further precision on
    what happens in the AdminUI when starting.

     

     

    Steps To Enable AdminUI Debug Logs
    https://communities.ca.com/people/Osarobo_Idehen/blog/2016/11/18/steps-to-enable-adminui-debug-logs

     

     

    If the AdminUI runs on Linux, make sure that you run rngd deamon or
    have a symlink between /dev/random and /dev/urandom.

     

     

    Hope this helps,

    Best Regards,
    Patrick



  • 10.  RE: Re: JBOSS failing to start when trying to start Admin UI

    Posted 01-12-2020 07:56 AM
    Hi Patrick,

    Did anyone has the resolution for this? I am too facing the same issue in R12.7 Linux Envrionment...



    Thanks,
    Karthik


  • 11.  RE: Re: JBOSS failing to start when trying to start Admin UI

    Broadcom Employee
    Posted 01-13-2020 03:02 AM
    Hi Karthik,

    Again, running AdminUI 12.7SP2 on Linux, the AdminUI is accessible and
    start fine even if I still have the error :

    2020-01-13 08:17:42,999 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.

    From the logs posted on 07-26-2017, it seems that JBoss stops on its
    own :


    2017-07-26 08:03:17,530 INFO [org.jboss.as] (Controller Boot Thread)
    JBAS015874: WildFly 8.2.0.Final "Tweek" started in 4532ms - Started
    252 of 304 services (104 services are lazy, passive or on-demand)

    2017-07-26 08:03:44,322 INFO [org.jboss.as.connector.deployment]
    (MSC service thread 1-1) JBAS010410: Unbound JCA ConnectionFactory
    [java:/JmsXA]

    Looking on the internet, this issue might be caused by interaction
    with OS and this is a known issue in JBoss community.

    MysteriousShutdowns

    What can it be

    Most shut downs are due to occurrences, such as users logging off
    while running jboss, someone accidentally hitting ctrl-c, or other
    simple answers, but sometimes it is due to inadvertent signals sent
    to the jvm that causes it to shut down.

    https://developer.jboss.org/wiki/MysteriousShutdowns

    Solution :

    Check if there a problem on files :

    When starting AdminUI it is getting hung and we cannot access the console
    https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=72181

    In order to find the root cause and a way to prevent it we need more
    information from your environment.

    - In /opt/software/ca/wamui/siteminder/adminui/bin/run.conf, set the following :

    add -Xrs to the value set for JAVA_OPTS;

    - Go to /opt/software/ca/wamui/siteminder/adminui/bin, make backup and
    edit the run.sh

    /* make a security copy */

    # cd /opt/software/ca/wamui/siteminder/adminui/bin:
    # cp -p run.sh run.sh.orig

    / * set the shell script to debug * /

    # nano -w run.sh

    add :
    Modify the script run.sh and add "set -x" on the line
    right after the shebang like this :

    #!/bin/sh
    set -x

    Then run the run.sh command that way :

    # strace -o run.dump -t -ff ./run.sh > run-output.txt 2>&1

    Gather all run.dump* and run-output.txt for the traces.

    and check the resulting files at time the JBoss shuts down, to seem if
    there's something blocking at the OS interaction level.

    I hope this helps,

    Best Regards,
    Patrick


  • 12.  RE: Re: JBOSS failing to start when trying to start Admin UI
    Best Answer

    Posted 01-13-2020 05:02 AM
    ​Thanks Patrick!

    Below article resolved my issue.

    https://ca-broadcom.wolkenservicedesk.com/external/article?articleId=72181