KB-1060 Login page does not load properly with a "68 services are lazy, passive or on-demand" log line printed in the JBoss server.log

Parmida Borhani — Thu, 30 Nov 2017 18:55:58 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 11/30/2017 6:55:58 PM

Symptoms

JBoss does not deploy Appian correctly after making changes to configuration files on a failed deployment and the following message in displayed in the console:

INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.4.0.GA (AS 7.5.0.Final-redhat-21) started in 8455ms - Started 217 of 254 services (68 services are lazy, passive or on-demand)

Cause

There are two likely causes for this behaviour:

The suite.ear.dodeploy marker file is missing in the <APPIAN_HOME>/ear directory. The marker file is necessary to instruct JBoss to deploy the suite.ear application. Since the suite.ear does not attempt to deploy, JBoss starts with only around 200 services total.
The Appian EAR is not listed in JBoss' deployment scanner path.

Action

To resolve this issue, perform one of the following:

Make any planned configuration changes in the repository.

Ensure that this line is present in the deployment-scanner subsection of standalone.xml:

<deployment-scanner name="appian" path="${appian.home.ear}" scan-interval="5000" auto-deploy-zipped="false" auto-deploy-exploded="false" auto-deploy-xml="false" deployment-timeout="3600"/>

Deploy the configurations using the Configure Script.
Note: This approach will deploy the suite.ear.dodeploy marker file. Note that this fix is only applicable to Appian 7.9 and later. Refer to Configure Script for more information.
Rename the suite.ear.failed/suite.ear.undeployed file located in <APPIAN_HOME>/ear, if it exists, to suite.ear.dodeploy.
Note: If a deployment failed before, search in the <JBOSS_HOME>/standalone/deployments directory for a .failed or .undeployed file. If such a file exists, delete it before attempting to deploy again.

Affected Versions

This article applies to all versions of Appian using JBoss EAP as an application server.

Last Reviewed: February 2017

Tags: installation, application server, upgrade, jboss

KB-1060 Login page does not load properly with a "68 services are lazy, passive or on-demand" log line printed in the JBoss server.log

Parmida Borhani — Thu, 30 Nov 2017 18:55:17 GMT

Revision 2 posted to Appian Knowledge Base by Parmida Borhani on 11/30/2017 6:55:17 PM

Symptoms

JBoss does not deploy Appian correctly after making changes to configuration files on a failed deployment and the following message in displayed in the console:

INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.4.0.GA (AS 7.5.0.Final-redhat-21) started in 8455ms - Started 217 of 254 services (68 services are lazy, passive or on-demand)

Cause

There are two likely causes for this behaviour:

The suite.ear.dodeploy marker file is missing in the <APPIAN_HOME>/ear directory. The marker file is necessary to instruct JBoss to deploy the suite.ear application. Since the suite.ear does not attempt to deploy, JBoss starts with only around 200 services total.
The Appian EAR is not listed in JBoss' deployment scanner path.

Action

To resolve this issue, perform one of the following:

Make any planned configuration changes in the repository.

Ensure that this line is present in the deployment-scanner subsection of standalone.xml:

<deployment-scanner name="appian" path="${appian.home.ear}" scan-interval="5000" auto-deploy-zipped="false" auto-deploy-exploded="false" auto-deploy-xml="false" deployment-timeout="3600"/>

Deploy the configurations using the Configure Script.
Note: This approach will deploy the suite.ear.dodeploy marker file. Note that this fix is only applicable to Appian 7.9 and later. Refer to Configure Script for more information.
Rename the suite.ear.failed/suite.ear.undeployed file located in <APPIAN_HOME>/ear, if it exists, to suite.ear.dodeploy.
Note: If a deployment failed before, search in the <JBOSS_HOME>/standalone/deployments directory for a .failed or .undeployed file. If such a file exists, delete it before attempting to deploy again.

Affected Versions

This article applies to all versions of Appian using JBoss EAP as an application server.

Last Reviewed: February 2017

Tags: installation, application server, upgrade, jboss

KB-1060 Login page does not load properly with a "68 services are lazy, passive or on-demand" log line printed in the JBoss server.log

Nick Vigilante — Tue, 14 Feb 2017 20:15:59 GMT

Revision 1 posted to Appian Knowledge Base by Nick Vigilante on 2/14/2017 8:15:59 PM

Symptoms

JBoss does not deploy Appian correctly after making changes to configuration files on a failed deployment and the following message in displayed in the console:

INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.4.0.GA (AS 7.5.0.Final-redhat-21) started in 8455ms - Started 217 of 254 services (68 services are lazy, passive or on-demand)

Cause

There are two likely causes for this behaviour:

The suite.ear.dodeploy marker file is missing in the <APPIAN_HOME>/eardirectory. The marker file is necessary to instruct JBoss to deploy the suite.ear application. Since the suite.ear does not attempt to deploy, JBoss starts with only around 200 services total.
The Appian EAR is not listed in the JBoss' deployment scanner path.

Action

To resolve this issue, perform one of the following:

Make any planned configuration changes in the repository.

Ensure that this line is present in the deployment-scanner subsection of standalone.xml:

<deployment-scanner name="appian" path="${appian.home.ear}" scan-interval="5000" auto-deploy-zipped="false" auto-deploy-exploded="false" auto-deploy-xml="false" deployment-timeout="3600"/>

Deploy the configurations using the Configure Script.
Note: This approach will deploy the suite.ear.dodeploy marker file. Note that this fix is only applicable to Appian 7.9 and later. Refer to Configure Script for more information.
Rename the suite.ear.failed/suite.ear.undeployed file located in <APPIAN_HOME>/ear, if it exists, to suite.ear.dodeploy.
Note: If a deployment failed before, search in the <JBOSS_HOME>/standalone/deployments directory for a .failed or .undeployed file. If such a file exists, delete it before attempting to deploy again.

Affected Versions

This article applies to all versions of Appian using JBoss EAP as an application server.

Last Reviewed: February 2017

Tags: installation, application server, upgrade, jboss