KB-1522 Excessive logging after upgrading to Appian 17.2 or above

Parmida Borhani — Mon, 23 Jul 2018 03:21:05 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 7/23/2018 3:21:05 AM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

After upgrading Appian to 17.2 or higher and applying a hotfix package, the following message shows up during the application server startup:

2018-02-03 14:54:52,352 ERROR [stderr] (MSC service thread 1-5) SLF4J: Class path contains multiple SLF4J bindings.
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-simple-1.7.21.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-log4j12-1.7.0.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2018-02-03 14:54:52,364 ERROR [stderr] (MSC service thread 1-5) SLF4J: Actual binding is of type [org.slf4j.impl.SimpleLoggerFactory]

After the application server has started successfully, logging messages such as these appear constantly in the application server log:

2018-02-03 14:57:56,453 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,454 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]
2018-02-03 14:57:56,459 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,460 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]

2018-02-03 15:00:47,265 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed
2018-02-03 15:00:47,269 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed

Cause

This issue has been addressed as AN-99391 in the following hotfixes/versions:

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian. For Appian 17.2, this issue can be alleviated by using the below workaround.

Workaround

The issue can be alleviated by following these steps:

Shut down the application server.
Delete slf4j-simple-1.7.21.jar from <APPIAN_HOME>/ear/suite.ear/lib.
Clear the application server cache.
1. Directions for JBoss
2. Directions for WebLogic
If using WebLogic, redeploy the suite EAR to WebLogic.
Start the application server.

Affected Versions

This article applies to Appian versions 17.2 through 17.4.

Last reviewed: March 2018

Tags: weblogic, logging, known issues, application server, fixed issues, infrastructure, jboss

KB-1522 Excessive logging after upgrading to Appian 17.2 or above

Parmida Borhani — Fri, 16 Mar 2018 06:26:30 GMT

Revision 18 posted to Appian Knowledge Base by Parmida Borhani on 3/16/2018 6:26:30 AM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

After upgrading Appian to 17.2 or higher and applying a hotfix package, the following message shows up during the application server startup:

2018-02-03 14:54:52,352 ERROR [stderr] (MSC service thread 1-5) SLF4J: Class path contains multiple SLF4J bindings.
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-simple-1.7.21.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-log4j12-1.7.0.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2018-02-03 14:54:52,364 ERROR [stderr] (MSC service thread 1-5) SLF4J: Actual binding is of type [org.slf4j.impl.SimpleLoggerFactory]

After the application server has started successfully, logging messages such as these appear constantly in the application server log:

2018-02-03 14:57:56,453 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,454 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]
2018-02-03 14:57:56,459 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,460 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]

2018-02-03 15:00:47,265 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed
2018-02-03 15:00:47,269 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed

Cause

This issue has been addressed as AN-99391 in the following hotfixes/versions:

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian. For Appian 17.2, this issue can be alleviated by using the below workaround.

Workaround

The issue can be alleviated by following these steps:

Shut down the application server.
Delete slf4j-simple-1.7.21.jar from <APPIAN_HOME>/ear/suite.ear/lib.
Clear the application server cache.
1. Directions for JBoss
2. Directions for WebLogic
If using WebLogic, redeploy the suite EAR to WebLogic.
Start the application server.

Affected Versions

This article applies to Appian versions 17.2 through 17.4.

Last reviewed: March 2018

Tags: weblogic, logging, known issues, application server, fixed issues, jboss

DRAFT KB-XXXX Excessive logging after upgrading to Appian 17.2 or above

Parmida Borhani — Fri, 16 Mar 2018 02:24:48 GMT

Revision 17 posted to Appian Knowledge Base by Parmida Borhani on 3/16/2018 2:24:48 AM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

After upgrading Appian to 17.2 or higher and applying a hotfix package, the following message shows up during the application server startup:

2018-02-03 14:54:52,352 ERROR [stderr] (MSC service thread 1-5) SLF4J: Class path contains multiple SLF4J bindings.
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-simple-1.7.21.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-log4j12-1.7.0.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2018-02-03 14:54:52,364 ERROR [stderr] (MSC service thread 1-5) SLF4J: Actual binding is of type [org.slf4j.impl.SimpleLoggerFactory]

After the application server has started successfully, logging messages such as these appear constantly in the application server log:

2018-02-03 14:57:56,453 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,454 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]
2018-02-03 14:57:56,459 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,460 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]

2018-02-03 15:00:47,265 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed
2018-02-03 15:00:47,269 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed

Cause

This issue has been addressed as AN-99391 in the following hotfixes/versions:

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian. For Appian 17.2, this issue can be alleviated by using the below workaround.

Workaround

The issue can be alleviated by following these steps:

Shut down the application server.
Delete slf4j-simple-1.7.21.jar from <APPIAN_HOME>/ear/suite.ear/lib.
Clear the application server cache.
1. Directions for JBoss
2. Directions for WebLogic
If using WebLogic, redeploy the suite EAR to WebLogic.
Start the application server.

Affected Versions

This article applies to Appian versions 17.2 through 17.4.

Last reviewed: March 2018

Tags: weblogic, logging, known issues, application server, fixed issues, jboss

DRAFT KB-XXXX Excessive logging after upgrading to Appian 17.2 or above

Parmida Borhani — Fri, 16 Mar 2018 02:24:11 GMT

Revision 16 posted to Appian Knowledge Base by Parmida Borhani on 3/16/2018 2:24:11 AM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

After upgrading Appian to 17.2 or higher and applying a hotfix package, the following message shows up during the application server startup:

2018-02-03 14:54:52,352 ERROR [stderr] (MSC service thread 1-5) SLF4J: Class path contains multiple SLF4J bindings.
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-simple-1.7.21.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-log4j12-1.7.0.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2018-02-03 14:54:52,364 ERROR [stderr] (MSC service thread 1-5) SLF4J: Actual binding is of type [org.slf4j.impl.SimpleLoggerFactory]

After the application server has started successfully, logging messages such as these appear constantly in the application server log:

2018-02-03 14:57:56,453 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,454 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]
2018-02-03 14:57:56,459 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,460 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]

2018-02-03 15:00:47,265 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed
2018-02-03 15:00:47,269 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed

Cause

This issue has been addressed as AN-99391 in the following hotfixes/versions:

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian. For Appian 17.2, this issue can be alleviated by using the below workaround.

Workaround

The issue can be alleviated by following these steps:

Shut down the application server.
Delete slf4j-simple-1.7.21.jar from <APPIAN_HOME>/ear/suite.ear/lib.
Clear the application server cache.
1. Directions for JBoss
2. Directions for WebLogic
If using WebLogic, redeploy the suite EAR to WebLogic.
Start the application server.

Affected Versions

This article applies to Appian versions 17.2 through 17.4.

Last reviewed: March 2018

Tags: weblogic, logging, known issues, administration, application server, fixed issues, jboss

DRAFT KB-XXXX Excessive logging after upgrading to Appian 17.2 or above

Parmida Borhani — Fri, 16 Mar 2018 02:22:42 GMT

Revision 15 posted to Appian Knowledge Base by Parmida Borhani on 3/16/2018 2:22:42 AM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

After upgrading Appian to 17.2 or higher and applying a hotfix package, the following message shows up during the application server startup:

2018-02-03 14:54:52,352 ERROR [stderr] (MSC service thread 1-5) SLF4J: Class path contains multiple SLF4J bindings.
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-simple-1.7.21.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-log4j12-1.7.0.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2018-02-03 14:54:52,364 ERROR [stderr] (MSC service thread 1-5) SLF4J: Actual binding is of type [org.slf4j.impl.SimpleLoggerFactory]

After the application server has started successfully, logging messages such as these appear constantly in the application server log:

2018-02-03 14:57:56,453 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,454 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]
2018-02-03 14:57:56,459 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,460 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]

2018-02-03 15:00:47,265 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed
2018-02-03 15:00:47,269 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed

Cause

This issue has been addressed as AN-99391 in the following hotfixes/versions:

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian. For Appian 17.2, this issue can be alleviated by using the below workaround.

Workaround

The issue can be alleviated by following these steps:

Shut down the application server.
Delete slf4j-simple-1.7.21.jar from <APPIAN_HOME>/ear/suite.ear/lib.
Clear the application server cache.
1. Directions for JBoss
2. Directions for WebLogic
If using WebLogic, redeploy the suite EAR to WebLogic.
Start the application server.

Affected Versions

This article applies to Appian versions 17.2 through 17.4.

Last reviewed: March 2018

Tags: weblogic, logging, known issues, administration, application server, fixed issues, jboss

DRAFT KB-XXXX Excessive logging after upgrading to Appian 17.2 or above

Parmida Borhani — Fri, 16 Mar 2018 02:21:08 GMT

Revision 14 posted to Appian Knowledge Base by Parmida Borhani on 3/16/2018 2:21:08 AM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

After upgrading Appian to 17.2 or higher and applying a hotfix package, the following message shows up during the application server startup:

2018-02-03 14:54:52,352 ERROR [stderr] (MSC service thread 1-5) SLF4J: Class path contains multiple SLF4J bindings.
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-simple-1.7.21.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-log4j12-1.7.0.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2018-02-03 14:54:52,364 ERROR [stderr] (MSC service thread 1-5) SLF4J: Actual binding is of type [org.slf4j.impl.SimpleLoggerFactory]

After the application server has started successfully, logging messages such as these appear constantly in the application server log:

2018-02-03 14:57:56,453 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,454 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]
2018-02-03 14:57:56,459 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,460 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]


2018-02-03 15:00:47,265 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed
2018-02-03 15:00:47,269 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed

Cause

This issue has been addressed as AN-99391 in the following hotfixes/versions:

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian. For Appian 17.2, this issue can be alleviated by using the below workaround.

Workaround

The issue can be alleviated by following these steps:

Shut down the application server.
Delete slf4j-simple-1.7.21.jar from <APPIAN_HOME>/ear/suite.ear/lib.
Clear the application server cache.
1. Directions for JBoss
2. Directions for WebLogic
If using WebLogic, redeploy the suite EAR to WebLogic.
Start the application server.

Affected Versions

This article applies to Appian versions 17.2 through 17.4.

Last reviewed: March 2018

Tags: weblogic, logging, known issues, administration, application server, fixed issues, jboss

DRAFT KB-XXXX Excessive logging after upgrading to Appian 17.2 or above

Parmida Borhani — Fri, 16 Mar 2018 02:20:27 GMT

Revision 13 posted to Appian Knowledge Base by Parmida Borhani on 3/16/2018 2:20:27 AM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

After upgrading Appian to 17.2 or higher and applying a hotfix package, the following message shows up during the application server startup:

2018-02-03 14:54:52,352 ERROR [stderr] (MSC service thread 1-5) SLF4J: Class path contains multiple SLF4J bindings.
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-simple-1.7.21.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-log4j12-1.7.0.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2018-02-03 14:54:52,364 ERROR [stderr] (MSC service thread 1-5) SLF4J: Actual binding is of type [org.slf4j.impl.SimpleLoggerFactory]

After the application server has started successfully, logging messages such as these appear constantly in the application server log:

2018-02-03 14:57:56,453 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,454 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]
2018-02-03 14:57:56,459 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,460 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]


2018-02-03 15:00:47,265 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed
2018-02-03 15:00:47,269 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed

Cause

This issue has been addressed as AN-99391 in the following hotfixes/versions:

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian. For Appian 17.2, this issue can be alleviated by using the below workaround.

Workaround

The issue can be alleviated by following these steps:

Shut down the application server.
Delete slf4j-simple-1.7.21.jar from <APPIAN_HOME>/ear/suite.ear/lib.
Clear the application server cache.
1. Directions for JBoss
2. Directions for WebLogic
If using WebLogic, redeploy the suite EAR to WebLogic.
Start the application server.

Affected Versions

This article applies to Appian versions 17.2 through 17.4.

Last reviewed: March 2018

Tags: weblogic, logging, known issues, administration, application server, fixed issues, jboss

DRAFT KB-XXXX Excessive logging after upgrading to Appian 17.2 or above

Parmida Borhani — Fri, 16 Mar 2018 02:20:05 GMT

Revision 12 posted to Appian Knowledge Base by Parmida Borhani on 3/16/2018 2:20:05 AM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

After upgrading Appian to 17.2 or higher and applying a hotfix package, the following message shows up during the application server startup:

2018-02-03 14:54:52,352 ERROR [stderr] (MSC service thread 1-5) SLF4J: Class path contains multiple SLF4J bindings.
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-simple-1.7.21.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-log4j12-1.7.0.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2018-02-03 14:54:52,364 ERROR [stderr] (MSC service thread 1-5) SLF4J: Actual binding is of type [org.slf4j.impl.SimpleLoggerFactory]

After the application server has started successfully, logging messages such as these appear constantly in the application server log:

2018-02-03 14:57:56,453 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,454 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]
2018-02-03 14:57:56,459 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,460 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]

2018-02-03 15:00:47,265 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed
2018-02-03 15:00:47,269 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed

Cause

This issue has been addressed as AN-99391 in the following hotfixes/versions:

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian. For Appian 17.2, this issue can be alleviated by using the below workaround.

Workaround

The issue can be alleviated by following these steps:

Shut down the application server.
Delete slf4j-simple-1.7.21.jar from <APPIAN_HOME>/ear/suite.ear/lib.
Clear the application server cache.
1. Directions for JBoss
2. Directions for WebLogic
If using WebLogic, redeploy the suite EAR to WebLogic.
Start the application server.

Affected Versions

This article applies to Appian versions 17.2 through 17.4.

Last reviewed: March 2018

Tags: weblogic, logging, known issues, administration, application server, fixed issues, jboss

DRAFT KB-XXXX Excessive logging after upgrading to Appian 17.2 or above

Jussi Lundstedt — Thu, 15 Mar 2018 11:02:37 GMT

Revision 11 posted to Appian Knowledge Base by Jussi Lundstedt on 3/15/2018 11:02:37 AM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

After upgrading Appian to 17.2 or higher and applying a hotfix package, the following message shows up during the application server startup:

2018-02-03 14:54:52,352 ERROR [stderr] (MSC service thread 1-5) SLF4J: Class path contains multiple SLF4J bindings.
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-simple-1.7.21.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-log4j12-1.7.0.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2018-02-03 14:54:52,364 ERROR [stderr] (MSC service thread 1-5) SLF4J: Actual binding is of type [org.slf4j.impl.SimpleLoggerFactory]

After the application server has started successfully, logging messages such as these appear constantly in the application server log:

2018-02-03 14:57:56,453 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,454 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]
2018-02-03 14:57:56,459 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,460 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]

2018-02-03 15:00:47,265 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed
2018-02-03 15:00:47,269 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed

Cause

This issue has been addressed as AN-99391 in the following hotfixes/versions:

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian. For Appian 17.2, this issue can be alleviated by using the below workaround.

Workaround

The issue can be alleviated by following these steps:

Shut down the application server.
Delete slf4j-simple-1.7.21.jar from <APPIAN_HOME>/ear/suite.ear/lib.
Clear the application server cache.
1. Directions for JBoss
2. Directions for WebLogic
If using WebLogic, redeploy the suite EAR to WebLogic.
Start the application server.

Affected Versions

This article applies to Appian versions 17.2 through 17.4.

Last reviewed: March 2018

Tags: weblogic, logging, known issues, administration, application server, fixed issues, jboss

DRAFT KB-XXXX Excessive logging after upgrading to Appian 17.2 or above

Jussi Lundstedt — Thu, 15 Mar 2018 11:01:56 GMT

Revision 10 posted to Appian Knowledge Base by Jussi Lundstedt on 3/15/2018 11:01:56 AM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

After upgrading Appian to 17.2 or higher and applying a hotfix package, the following message shows up during the application server startup:

2018-02-03 14:54:52,352 ERROR [stderr] (MSC service thread 1-5) SLF4J: Class path contains multiple SLF4J bindings.
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-simple-1.7.21.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-log4j12-1.7.0.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2018-02-03 14:54:52,364 ERROR [stderr] (MSC service thread 1-5) SLF4J: Actual binding is of type [org.slf4j.impl.SimpleLoggerFactory]

After the application server has started successfully, logging messages such as these appear constantly in the application server log:

2018-02-03 14:57:56,453 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,454 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]
2018-02-03 14:57:56,459 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,460 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]

2018-02-03 15:00:47,265 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed
2018-02-03 15:00:47,269 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed

Cause

This issue has been addressed as AN-99391 in the following hotfixes/versions:

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian. For Appian 17.2, this issue can be alleviated by using the below workaround.

Workaround

The issue can be alleviated by following these steps:

Shut down the application server.
Delete slf4j-simple-1.7.21.jar from <APPIAN_HOME>/ear/suite.ear/lib.
Clear the application server cache.
1. Directions for JBoss
2. Directions for WebLogic
If using WebLogic, redeploy the suite EAR to WebLogic.
Start the application server.

Affected Versions

This article applies to Appian versions 17.2 through 17.4.

Last reviewed: March 2018

Tags: weblogic, logging, known issues, administration, application server, fixed issues, jboss

DRAFT KB-XXXX Excessive logging after upgrading to Appian 17.2 or above

Parmida Borhani — Wed, 14 Mar 2018 21:19:32 GMT

Revision 9 posted to Appian Knowledge Base by Parmida Borhani on 3/14/2018 9:19:32 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

After upgrading Appian to 17.2 or higher and applying a hotfix package, the following message shows up during the application server startup:

2018-02-03 14:54:52,352 ERROR [stderr] (MSC service thread 1-5) SLF4J: Class path contains multiple SLF4J bindings.
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-simple-1.7.21.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-log4j12-1.7.0.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2018-02-03 14:54:52,364 ERROR [stderr] (MSC service thread 1-5) SLF4J: Actual binding is of type [org.slf4j.impl.SimpleLoggerFactory]

After the application server has started successfully, logging messages such as these appear constantly in the application server log:

2018-02-03 14:57:56,453 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,454 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]
2018-02-03 14:57:56,459 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,460 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]

2018-02-03 15:00:47,265 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed
2018-02-03 15:00:47,269 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed

Cause

This issue has been addressed as AN-99391 in the following hotfixes/versions:

Appian 17.3 Hotfix Package E
Appian 17.4 Hotfix Package D
Appian 18.1

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian. For Appian 17.2, this issue can be alleviated by using the below workaround.

Workaround

The issue can be alleviated by following these steps:

Shut down the Appian application server
Delete slf4j-simple-1.7.21.jar from the <APPIAN_HOME>/ear/suite.ear/lib
Clear the application server cache
1. Directions for JBoss
2. Directions for WebLogic
If using WebLogic, redeploy the suite EAR to WebLogic
Start the application server

Affected versions

This article applies to Appian versions 17.2 through 17.4.

Tags: weblogic, logging, administration, application server, fixed issues, jboss

DRAFT KB-XXXX Excessive logging after upgrading to Appian 17.2 or above

Parmida Borhani — Wed, 14 Mar 2018 21:19:15 GMT

Revision 8 posted to Appian Knowledge Base by Parmida Borhani on 3/14/2018 9:19:15 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

After upgrading Appian to 17.2 or higher and applying a hotfix package, the following message shows up during the application server startup:

2018-02-03 14:54:52,352 ERROR [stderr] (MSC service thread 1-5) SLF4J: Class path contains multiple SLF4J bindings.
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-simple-1.7.21.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-log4j12-1.7.0.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2018-02-03 14:54:52,364 ERROR [stderr] (MSC service thread 1-5) SLF4J: Actual binding is of type [org.slf4j.impl.SimpleLoggerFactory]

After the application server has started successfully, logging messages such as these appear constantly in the application server log:

2018-02-03 14:57:56,453 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,454 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]
2018-02-03 14:57:56,459 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,460 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]

2018-02-03 15:00:47,265 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed
2018-02-03 15:00:47,269 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed

Cause

This issue has been addressed as AN-99391 in the following hotfixes/versions:

Appian 17.3 Hotfix Package E
Appian 17.4 Hotfix Package D
Appian 18.1

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian. For Appian 17.2, this issue can be alleviated by using the below workaround.

Workaround

The issue can be alleviated by following these steps:

Shut down the Appian application server
Delete slf4j-simple-1.7.21.jar from the <APPIAN_HOME>/ear/suite.ear/lib
Clear the application server cache
1. Directions for JBoss
2. Directions for WebLogic
If using WebLogic, redeploy the suite EAR to WebLogic
Start the application server

Affected versions

This article applies to Appian versions 17.2 through 17.4.

Tags: weblogic, logging, administration, application server, fixed issues, jboss

DRAFT KB-XXXX Excessive logging after upgrading to Appian 17.2 or above

Jussi Lundstedt — Wed, 14 Mar 2018 12:53:11 GMT

Revision 7 posted to Appian Knowledge Base by Jussi Lundstedt on 3/14/2018 12:53:11 PM

Symptoms

After upgrading Appian to 17.2 or higher and applying a hotfix package, the following message shows up during the application server startup:

2018-02-03 14:54:52,352 ERROR [stderr] (MSC service thread 1-5) SLF4J: Class path contains multiple SLF4J bindings.
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-simple-1.7.21.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-log4j12-1.7.0.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2018-02-03 14:54:52,364 ERROR [stderr] (MSC service thread 1-5) SLF4J: Actual binding is of type [org.slf4j.impl.SimpleLoggerFactory]

After the application server has started successfully, logging messages such as these appear constantly in the application server log:

2018-02-03 14:57:56,453 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,454 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]
2018-02-03 14:57:56,459 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,460 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]

2018-02-03 15:00:47,265 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed
2018-02-03 15:00:47,269 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed

Cause

This issue has been addressed as AN-99391 in the following hotfixes/versions:

Appian 17.3 Hotfix Package E
Appian 17.4 Hotfix Package D
Appian 18.1

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian. For Appian 17.2, this issue can be alleviated by using the below workaround.

Workaround

The issue can be alleviated by following these steps:

Shut down the Appian application server
Delete slf4j-simple-1.7.21.jar from the <APPIAN_HOME>/ear/suite.ear/lib
Clear the application server cache
1. Directions for JBoss
2. Directions for WebLogic
If using WebLogic, redeploy the suite EAR to WebLogic
Start the application server

Affected versions

This article applies to Appian versions 17.2 through 17.4.

Tags: weblogic, logging, administration, application server, fixed issues, jboss

DRAFT KB-XXXX Excessive logging after upgrading to Appian 17.2 or above

Jussi Lundstedt — Wed, 14 Mar 2018 12:51:22 GMT

Revision 6 posted to Appian Knowledge Base by Jussi Lundstedt on 3/14/2018 12:51:22 PM

Symptoms

After upgrading Appian to 17.2 or higher and applying a hotfix package, the following message shows up during the application server startup:

2018-02-03 14:54:52,352 ERROR [stderr] (MSC service thread 1-5) SLF4J: Class path contains multiple SLF4J bindings.
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-simple-1.7.21.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-log4j12-1.7.0.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2018-02-03 14:54:52,364 ERROR [stderr] (MSC service thread 1-5) SLF4J: Actual binding is of type [org.slf4j.impl.SimpleLoggerFactory]

After the application server has started successfully, logging messages such as these appear constantly in the application server log:

2018-02-03 14:57:56,453 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,454 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]
2018-02-03 14:57:56,459 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,460 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]

2018-02-03 15:00:47,265 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed
2018-02-03 15:00:47,269 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed

Cause

This issue has been addressed as AN-99391 in the following hotfixes/versions:

Appian 17.3 Hotfix Package E
Appian 17.4 Hotfix Package D
Appian 18.1

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Workaround

The issue can be alleviated by following these steps:

Shut down the Appian application server
Delete slf4j-simple-1.7.21.jar from the <APPIAN_HOME>/ear/suite.ear/lib
Clear the application server cache
1. Directions for JBoss
2. Directions for WebLogic
If using WebLogic, redeploy the suite EAR to WebLogic
Start the application server

Tags: weblogic, logging, administration, application server, fixed issues

DRAFT KB-XXXX Excessive logging after upgrading to Appian 17.2 or above

Jussi Lundstedt — Fri, 02 Mar 2018 12:48:44 GMT

Revision 5 posted to Appian Knowledge Base by Jussi Lundstedt on 3/2/2018 12:48:44 PM

Symptoms

After upgrading Appian to 17.2 or higher and applying a hotfix package, the following message shows up during the application server startup:

2018-02-03 14:54:52,352 ERROR [stderr] (MSC service thread 1-5) SLF4J: Class path contains multiple SLF4J bindings.
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-simple-1.7.21.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-log4j12-1.7.0.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2018-02-03 14:54:52,364 ERROR [stderr] (MSC service thread 1-5) SLF4J: Actual binding is of type [org.slf4j.impl.SimpleLoggerFactory]

After the application server has started successfully, logging messages such as these appear constantly in the application server log:

2018-02-03 14:57:56,453 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,454 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]
2018-02-03 14:57:56,459 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,460 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]

2018-02-03 15:00:47,265 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed
2018-02-03 15:00:47,269 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed

Cause

This issue has been addressed as AN-99391 in the following hotfixes/versions:

Appian 17.2 Hotfix Package I
Appian 17.3 Hotfix Package E
Appian 17.4 Hotfix Package D
Appian 18.1

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Workaround

The issue can be alleviated by following these steps:

Shut down the Appian application server
Delete slf4j-simple-1.7.21.jar from the <APPIAN_HOME>/ear/suite.ear/lib
Clear the application server cache
If using WebLogic, redeploy the suite EAR to WebLogic
Start the application server

Tags: weblogic, logging, administration, application server, fixed issues

DRAFT KB-XXXX Excessive logging after upgrading to Appian 17.2 or above

Jussi Lundstedt — Fri, 02 Mar 2018 11:18:57 GMT

Revision 4 posted to Appian Knowledge Base by Jussi Lundstedt on 3/2/2018 11:18:57 AM

Symptoms

After upgrading Appian to 17.2 or higher and applying a hotfix package, the following message shows up during the application server startup:

2018-02-03 14:54:52,352 ERROR [stderr] (MSC service thread 1-5) SLF4J: Class path contains multiple SLF4J bindings.
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-simple-1.7.21.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-log4j12-1.7.0.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2018-02-03 14:54:52,364 ERROR [stderr] (MSC service thread 1-5) SLF4J: Actual binding is of type [org.slf4j.impl.SimpleLoggerFactory]

After the application server has started successfully, logging messages such as these appear constantly in the application server log:

2018-02-03 14:57:56,453 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,454 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]
2018-02-03 14:57:56,459 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,460 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]

2018-02-03 15:00:47,265 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed
2018-02-03 15:00:47,269 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed

Cause

This issue has been addressed as AN-99391 in the following hotfixes/versions:

Appian 17.2 Hotfix Package I
Appian 17.3 Hotfix Package E
Appian 17.4 Hotfix Package D
Appian 18.1

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Workaround

The issue can be alleviated by following these steps:

Shut down the Appian application server
Delete slf4j-simple-1.7.21.jar from the <APPIAN_HOME>/ear/suite.ear/lib
Clear the application server cache
If using WebLogic, redeploy the suite EAR to WebLogic
Start the application server

Tags: weblogic, logging, administration, application server, fixed issues

DRAFT KB-XXXX Excessive logging after upgrading to Appian 17.2 or above

Jussi Lundstedt — Tue, 27 Feb 2018 15:00:41 GMT

Revision 1 posted to Appian Knowledge Base by Jussi Lundstedt on 2/27/2018 3:00:41 PM

Symptoms

After upgrading Appian to 17.2 or higher and applying a hotfix package, the following message shows up during the application server startup:

2018-02-03 14:54:52,352 ERROR [stderr] (MSC service thread 1-5) SLF4J: Class path contains multiple SLF4J bindings.
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-simple-1.7.21.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-log4j12-1.7.0.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2018-02-03 14:54:52,364 ERROR [stderr] (MSC service thread 1-5) SLF4J: Actual binding is of type [org.slf4j.impl.SimpleLoggerFactory]

After the application server has started successfully, logging messages such as these appear constantly in the application server log:

2018-02-03 14:57:56,453 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,454 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]
2018-02-03 14:57:56,459 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,460 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]

2018-02-03 15:00:47,265 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed
2018-02-03 15:00:47,269 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed

Cause

This issue has been addressed as AN-99391 in the following hotfixes/versions:

Appian 17.2 Hotfix Package I
Appian 17.3 Hotfix Package E
Appian 17.4 Hotfix Package D
Appian 18.1

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Tags: weblogic, logging, administration, application server, fixed issues

DRAFT KB-XXXX Excessive logging after upgrading to Appian 17.2 or above

Jussi Lundstedt — Tue, 27 Feb 2018 10:02:10 GMT

Revision 3 posted to Appian Knowledge Base by Jussi Lundstedt on 2/27/2018 10:02:10 AM

Symptoms

After upgrading Appian to 17.2 or higher and applying a hotfix package, the following message shows up during the application server startup:

2018-02-03 14:54:52,352 ERROR [stderr] (MSC service thread 1-5) SLF4J: Class path contains multiple SLF4J bindings.
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-simple-1.7.21.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-log4j12-1.7.0.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2018-02-03 14:54:52,364 ERROR [stderr] (MSC service thread 1-5) SLF4J: Actual binding is of type [org.slf4j.impl.SimpleLoggerFactory]

After the application server has started successfully, logging messages such as these appear constantly in the application server log:

2018-02-03 14:57:56,453 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,454 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]
2018-02-03 14:57:56,459 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,460 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]

2018-02-03 15:00:47,265 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed
2018-02-03 15:00:47,269 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed

Cause

This issue has been addressed as AN-99391 in the following hotfixes/versions:

Appian 17.2 Hotfix Package I
Appian 17.3 Hotfix Package E
Appian 17.4 Hotfix Package D
Appian 18.1

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Tags: weblogic, logging, administration, application server, fixed issues

DRAFT KB-XXXX Excessive logging after upgrading to Appian 17.2 or above

Jussi Lundstedt — Tue, 27 Feb 2018 10:01:56 GMT

Revision 2 posted to Appian Knowledge Base by Jussi Lundstedt on 2/27/2018 10:01:56 AM

Symptoms

After upgrading Appian to 17.2 or higher and applying a hotfix package, the following message shows up during the application server startup:

2018-02-03 14:54:52,352 ERROR [stderr] (MSC service thread 1-5) SLF4J: Class path contains multiple SLF4J bindings.
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-simple-1.7.21.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: Found binding in [vfs:/apps/appian/ear/suite.ear/lib/slf4j-log4j12-1.7.0.jar/org/slf4j/impl/StaticLoggerBinder.class]
2018-02-03 14:54:52,353 ERROR [stderr] (MSC service thread 1-5) SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
2018-02-03 14:54:52,364 ERROR [stderr] (MSC service thread 1-5) SLF4J: Actual binding is of type [org.slf4j.impl.SimpleLoggerFactory]

After the application server has started successfully, logging messages such as these appear constantly in the application server log:

2018-02-03 14:57:56,453 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,454 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]
2018-02-03 14:57:56,459 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - begin com.appiancorp.core.expr.Parse eval [Thread 238]
2018-02-03 14:57:56,460 ERROR [stderr] (Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13) [Appian ReschedulingTimerTask - IaReplicatorTimerTask - 13] INFO feature_context - end com.appiancorp.core.expr.Parse eval:0ms [Thread 238]

2018-02-03 15:00:47,265 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed
2018-02-03 15:00:47,269 ERROR [stderr] (Appian Plugin Hot Deploy) [Appian Plugin Hot Deploy] INFO com.atlassian.plugin.loaders.ScanningPluginLoader - No plugins found to be installed

Cause

This issue has been addressed as AN-99391 in the following hotfixes/versions:

Appian 17.2 Hotfix Package I
Appian 17.3 Hotfix Package E
Appian 17.4 Hotfix Package D
Appian 18.1

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Tags: weblogic, logging, administration, application server, fixed issues