DRAFT KB-XXXX JBoss start-up is stuck with no useful errors in the server logs

Symptoms

JBoss fails to start-up every time standalone.bat|sh script located in <JBOSS_HOME>/bin/ directory is executed. JBoss logs ends at the following step: 

16:18:39,700 ERROR [stderr] (MSC service thread 1-4) SLF4J: Class path contains multiple SLF4J bindings. 
16:18:39,700 ERROR [stderr] (MSC service thread 1-4) SLF4J: Found binding in [vfs:/D:/appian/ear/suite.ear/lib/slf4j-log4j12-1.7.0.jar/org/slf4j/impl/StaticLoggerBinder.class] 
16:18:39,700 ERROR [stderr] (MSC service thread 1-4) SLF4J: Found binding in [vfs:/D:/appian/ear/suite.ear/lib/slf4j-simple-1.7.21.jar/org/slf4j/impl/StaticLoggerBinder.class] 
16:18:39,716 ERROR [stderr] (MSC service thread 1-4) SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. 
16:18:39,716 ERROR [stderr] (MSC service thread 1-4) SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]

Cause

The JBoss is stuck because it is unable to access _admin directory. Either there is significant network latency or there are improper permissions on the _admin directory. 

Action

Ensure that _admin directory is accessible by JBoss. If it's hosted in a shared drive, check the network latency and the load on the shared drive. 

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2018