JBoss EAP 6.1 HornetQ start up issue

Latest response

Hello,
HornetQ is failing to start during server restart and hung up after the below logs.

Due to the race condition of Jboss MSC parallely starting the deployments connection factory lookup is getting failed,we have written a custom JNDI lookup which waits until we get the connection factory with a timeout of 5 minutes.

We have configured -Dorg.jboss.server.bootstrap.maxThreads=30 in the standalone conf file.

There are around 44 components deployed in JBoss server out of which 17 connects to Hornet Q

2017-07-10 13:14:48,470 INFO [org.jboss.as.jacorb] (MSC service thread 1-20) JBAS016328: CORBA Naming Service started
2017-07-10 13:14:48,912 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 1) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/opt/jboss/jbfsw-6/controller/standalone/company_test_svstd_fsw_standalone_BIH-UAT_02/data/messagingjournal,bindingsDirectory=/opt/jboss/jbfsw-6/controller/standalone/company_test_svstd_fsw_standalone_BIH-UAT_02/data/messagingbindings,largeMessagesDirectory=/opt/jboss/jbfsw-6/controller/standalone/company_test_svstd_fsw_standalone_BIH-UAT_02/data/messaginglargemessages,pagingDirectory=/opt/jboss/jbfsw-6/controller/standalone/company_test_svstd_fsw_standalone_BIH-UAT_02/data/messagingpaging)
2017-07-10 13:14:48,914 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 1) HQ221006: Waiting to obtain live lock
2017-07-10 13:14:48,969 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 1) HQ221013: Using NIO Journal
2017-07-10 13:14:49,126 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 1) HQ221034: Waiting to obtain live lock
2017-07-10 13:14:49,126 INFO [org.hornetq.core.server] (ServerService Thread Pool -- 1) HQ221035: Live Server Obtained live lock

Attachments

Responses

Please check your standalone.xml connection for the database and queue connections.The connection pool factory is trying to validate the connections.If there is error/delay in correction will result into hungup.