KB-1737 JBoss start-up does not progress with no useful errors in the server logs

Parmida Borhani — Thu, 04 Oct 2018 08:15:29 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 10/4/2018 8:15:29 AM

Symptoms

JBoss fails to start-up every time the standalone.bat|sh script located in the <JBOSS_HOME>/bin/ directory is executed. The following output is the last thing printed in the server.log located in the <JBOSS_HOME>/standalone/logs directory:

ERROR [stderr] (MSC service thread 1-4) SLF4J: Class path contains multiple SLF4J bindings. 
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] 
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] 
ERROR [stderr] (MSC service thread 1-4) SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. 
ERROR [stderr] (MSC service thread 1-4) SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]

Note: The SLF4J errors above are not directly related to this issue and can be safely disregarded. They simply display the point at which the start-up hangs.

Cause

This issue may be caused by the application server being unable to access <APPIAN_HOME>/_admin directory. This may be caused by one of the following reasons:

There is significant network latency while accessing the <APPIAN_HOME>/_admin directory.
There is heavy load on the server hosting the <APPIAN_HOME>/_admin directory.
There are improper permissions on the <APPIAN_HOME>/_admin directory.

Action

Ensure that the <APPIAN_HOME>/_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 using JBoss as an application server.

Last Reviewed: September 2018

Tags: administration, application server, infrastructure, network, jboss

KB-1737 JBoss start-up does not progress with no useful errors in the server logs

Parmida Borhani — Thu, 04 Oct 2018 04:13:46 GMT

Revision 6 posted to Appian Knowledge Base by Parmida Borhani on 10/4/2018 4:13:46 AM

Symptoms

ERROR [stderr] (MSC service thread 1-4) SLF4J: Class path contains multiple SLF4J bindings. 
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] 
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] 
ERROR [stderr] (MSC service thread 1-4) SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. 
ERROR [stderr] (MSC service thread 1-4) SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]

Note: the SLF4J errors above are not directly related to this issue and can be safely disregarded. They simply display the point at which the start-up hangs.

Cause

This issue may be caused by the application server being unable to access <APPIAN_HOME>/_admin directory. This may be caused by one of the following reasons:

There is significant network latency while accessing the <APPIAN_HOME>/_admin directory.
There is heavy load on the server hosting the <APPIAN_HOME>/_admin directory.
There are improper permissions on the <APPIAN_HOME>/_admin directory.

Action

Ensure that the <APPIAN_HOME>/_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 using JBoss as an application server.

Last Reviewed: September 2018

Tags: administration, application server, infrastructure, network, jboss

DRAFT KB-XXXX JBoss start-up does not progress with no useful errors in the server logs

Parmida Borhani — Wed, 03 Oct 2018 00:59:22 GMT

Revision 5 posted to Appian Knowledge Base by Parmida Borhani on 10/3/2018 12:59:22 AM

Symptoms

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]

Note: the SLF4J errors above are not directly related to this issue and can be safely disregarded.

Cause

This issue may be caused by the application server being unable to access <APPIAN_HOME>/_admin directory. This may be caused by one of the following reasons:

There is significant network latency while accessing the <APPIAN_HOME>/_admin directory.
There is heavy load on the server hosting the <APPIAN_HOME>/_admin directory.
There are improper permissions on the <APPIAN_HOME>/_admin directory.

Action

Ensure that the <APPIAN_HOME>/_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 using JBoss as an application server.

Last Reviewed: September 2018

Tags: administration, application server, infrastructure, network, jboss

DRAFT KB-XXXX JBoss start-up does not progress with no useful errors in the server logs

Tom Ryan — Tue, 02 Oct 2018 01:49:04 GMT

Revision 4 posted to Appian Knowledge Base by Tom Ryan on 10/2/2018 1:49:04 AM

Symptoms

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]

Note: the SLF4J errors above are not directly related to this issue and can be safely disregarded.

Cause

This issue may be caused by the application server being unable to access <APPIAN_HOME>/_admin directory. This may be caused by one of the following reasons:

There is significant network latency while access the <APPIAN_HOME>/_admin directory.
There is heavy load on the server hosting <APPIAN_HOME>/_admin directory.
There are improper permissions on the <APPIAN_HOME>/_admin directory.

Action

Ensure that the <APPIAN_HOME>/_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 using JBoss as an application server.

Last Reviewed: September 2018

Tags: administration, application server, infrastructure, network, jboss

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

Anirudh Rathi — Tue, 18 Sep 2018 14:04:26 GMT

Revision 3 posted to Appian Knowledge Base by Anirudh Rathi on 9/18/2018 2:04:26 PM

Symptoms

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 application server is unable to proceed with the start-up because it is unable to access <APPIAN_HOME>/_admin directory. Following reasons can be the reason for this:

There is significant network latency while access the <APPIAN_HOME>/_admin directory.
There is heavy load on the server hosting <APPIAN_HOME>/_admin directory.
There are improper permissions on the <APPIAN_HOME>/_admin directory.

Action

Ensure that the <APPIAN_HOME>/_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 using JBoss as an application server.

Last Reviewed: September 2018

Tags: administration, application server, infrastructure, network, jboss

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

Anirudh Rathi — Mon, 17 Sep 2018 10:16:54 GMT

Revision 2 posted to Appian Knowledge Base by Anirudh Rathi on 9/17/2018 10:16:54 AM

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

Tags: start-up, application server, shared components, infrastructure

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

Anirudh Rathi — Fri, 14 Sep 2018 21:15:54 GMT

Revision 1 posted to Appian Knowledge Base by Anirudh Rathi on 9/14/2018 9:15:54 PM

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 to the 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

Tags: start-up, application server, shared components, infrastructure