AnsweredAssumed Answered

Admin ui hangs

Question asked by Ujwol Shrestha Employee on Jan 28, 2018
Latest reply on Jan 29, 2018 by Ujwol Shrestha

Created on behalf of @ P Soni

and follow up on thread : 12.7 adminui: creating legacy administrator to loginto admin ui 


Hi Ujwol,


Thanks for your reply. I changed the search. It went through to the final screen this time, which is better. but I haven't had much luck. I came to below screen and it got hung.



I started the adminui using standalone script. It has been sitting here for hours now, The logs below is from 3rd attempt of starting jboss.


12:31:02,145 WARN  [] (ServerService Thread Pool -- 44) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique.

From server.log not much detail:


tail -f server.log
2018-01-25 12:31:07,597 INFO  [] (ServerService Thread Pool -- 51) JBAS011601: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
2018-01-25 12:31:07,693 INFO  [] (MSC service thread 1-2) JBAS010406: Registered connection factory java:/JmsXA
2018-01-25 12:31:07,810 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) JBAS017519: Undertow HTTPS listener https listening on /
2018-01-25 12:31:07,843 INFO  [org.hornetq.ra] (MSC service thread 1-2) HornetQ resource adaptor started
2018-01-25 12:31:07,844 INFO  [$ResourceAdapterActivator] (MSC service thread 1-2) IJ020002: Deployed: file://RaActivatorhornetq-ra
2018-01-25 12:31:07,846 INFO  [] (MSC service thread 1-2) JBAS010401: Bound JCA ConnectionFactory [java:/JmsXA]
2018-01-25 12:31:08,204 INFO  [] (MSC service thread 1-3) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.3.2.Final
2018-01-25 12:31:08,309 INFO  [] (Controller Boot Thread) JBAS015961: Http management interface listening on
2018-01-25 12:31:08,310 INFO  [] (Controller Boot Thread) JBAS015954: Admin console is not enabled
2018-01-25 12:31:08,310 INFO  [] (Controller Boot Thread) JBAS015874: WildFly 8.2.0.Final "Tweek" started in 16172ms - Started 252 of 304 services (104 services are lazy, passive or on-demand)


What is the way of further debugging this issue?