KB-2199 "Unknown topic config name: retention.min.timestamp" error observed after upgrade

Elly Meng — Tue, 12 Apr 2022 16:06:23 GMT

Current Revision posted to Appian Knowledge Base by Elly Meng on 4/12/2022 4:06:23 PM

Symptoms

After upgrading from, or applying a hotfix to an Appian version below 20.1, the following error is seen in the application server log during startup:

java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.InvalidConfigurationException: Unknown topic config name: retention.min.timestamp

The environment starts up normally and users are able to access it without any issues.

Cause

The error is due to a change in the internal retention.min.timestamp configuration which is no longer required. This issue has been reported to the Appian Product Team. The reference number for this issue is AN-192137.

Actions

The error is harmless and can be safely ignored. No further action is required.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2021

Tags: known issues, engines, installation, application server, upgrade, infrastructure, open issues

KB-2198 "Unknown topic config name: retention.min.timestamp" error observed after upgrade

Parmida Borhani — Fri, 08 Oct 2021 07:20:52 GMT

Revision 15 posted to Appian Knowledge Base by Parmida Borhani on 10/8/2021 7:20:52 AM

Symptoms

After upgrading from, or applying a hotfix to an Appian version below 20.1, the following error is seen in the application server log during startup:

java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.InvalidConfigurationException: Unknown topic config name: retention.min.timestamp

The environment starts up normally and users are able to access it without any issues.

Cause

Actions

The error is harmless and can be safely ignored. No further action is required.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2021

Tags: known issues, engines, installation, application server, upgrade, infrastructure, open issues

DRAFT SP-6753 "Unknown topic config name: retention.min.timestamp" error observed after upgrade

Parmida Borhani — Fri, 08 Oct 2021 07:19:09 GMT

Revision 14 posted to Appian Knowledge Base by Parmida Borhani on 10/8/2021 7:19:09 AM

Symptoms

After upgrading from, or applying a hotfix to an Appian version below 20.1, the following error is seen in the application server log during startup:

java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.InvalidConfigurationException: Unknown topic config name: retention.min.timestamp

The environment starts up normally and users are able to access it without any issues.

Cause

Actions

The error is harmless and can be safely ignored. No further action is required.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2021

Tags: known issues, engines, installation, application server, upgrade, infrastructure, open issues

DRAFT SP-6753 "Unknown topic config name: retention.min.timestamp" error observed after upgrade

Tom Ryan — Fri, 08 Oct 2021 07:16:03 GMT

Revision 13 posted to Appian Knowledge Base by Tom Ryan on 10/8/2021 7:16:03 AM

Symptoms

After upgrading from, or applying a hotfix to an Appian version below 20.1, the following error is seen in the application server log during startup:

java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.InvalidConfigurationException: Unknown topic config name: retention.min.timestamp

The environment starts up normally and users are able to access it without any issues.

Cause

The error is due to a change in the internal retention.min.timestamp configuration which is no longer required.

Actions

The error is harmless and can be safely ignored. This issue has been reported to the Appian Product Team. The reference number for this issue is AN-192137.

No further action is required.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2021

Tags: known issues, engines, installation, application server, upgrade, infrastructure, open issues

DRAFT SP-6753 "Unknown topic config name: retention.min.timestamp" error observed after upgrade

Khalid Khan — Fri, 08 Oct 2021 06:46:51 GMT

Revision 12 posted to Appian Knowledge Base by Khalid Khan on 10/8/2021 6:46:51 AM

Symptoms

After upgrading from, or applying a hotfix to an Appian version below 20.1, the following error is seen in the application server log during startup:

java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.InvalidConfigurationException: Unknown topic config name: retention.min.timestamp

The environment starts up normally and users are able to access it without any issues.

Cause

The error is due to a failure in applying the retention.min.timestamp configuration which is no longer required.

Actions

The error is harmless and can be safely ignored. This issue has been reported to the Appian Product Team. The reference number for this issue is AN-192137.

No further action is required.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2021

Tags: known issues, engines, installation, application server, upgrade, infrastructure, open issues

DRAFT SP-6753 "Unknown topic config name: retention.min.timestamp" error observed after upgrade

Khalid Khan — Fri, 08 Oct 2021 06:45:59 GMT

Revision 11 posted to Appian Knowledge Base by Khalid Khan on 10/8/2021 6:45:59 AM

Symptoms

After upgrading from, or applying a hotfix to an Appian version below 20.1, the following error is seen in the application server log during startup:

java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.InvalidConfigurationException: Unknown topic config name: retention.min.timestamp

The environment starts up normally and users are able to access it without any issues.

Cause

The error is due to a failure in applying the retention.min.timestamp configuration which is no longer required.

Actions

The error is harmless and can be safely ignored. This issue has been reported to the Appian Product Team. The reference number for this issue is AN-192137.

No further action is required.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2021

Tags: known issues, engines, installation, application server, upgrade, infrastructure, open issues

DRAFT SP-6753 "Unknown topic config name: retention.min.timestamp" error observed after upgrade

Khalid Khan — Fri, 08 Oct 2021 06:32:40 GMT

Revision 10 posted to Appian Knowledge Base by Khalid Khan on 10/8/2021 6:32:40 AM

Symptoms

After upgrading from an Appian version below 20.1, or applying a hotfix to an older version of Appian (example: 19.4), the following error is seen in the application server log during startup:

java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.InvalidConfigurationException: Unknown topic config name: retention.min.timestamp

The environment starts up normally and users are able to access it without any issues.

Cause

The error is due to a failure in applying the retention.min.timestamp configuration which is no longer required.

Actions

The error is harmless and can be safely ignored. This issue has been reported to the Appian Product Team. The reference number for this issue is AN-192137.

No further action is required.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2021

Tags: known issues, engines, installation, application server, upgrade, infrastructure, open issues

DRAFT SP-6753 "Unknown topic config name: retention.min.timestamp" error observed after upgrade

Khalid Khan — Fri, 08 Oct 2021 06:22:06 GMT

Revision 9 posted to Appian Knowledge Base by Khalid Khan on 10/8/2021 6:22:06 AM

Symptoms

After upgrading from an Appian version below 20.1, or applying a hotfix to an older version of Appian (example: 19.4), the following error is seen in the application server log during startup:

java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.InvalidConfigurationException: Unknown topic config name: retention.min.timestamp

The environment starts up normally and users are able to access it without any issues.

Cause

The error is due to a failure in applying the retention.min.timestamp configuration which is no longer required. The error is harmless and can be safely ignored. This issue has been reported to the Appian Product Team. The reference number for this issue is AN-192137.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2021

Tags: known issues, engines, installation, application server, upgrade, infrastructure, open issues

DRAFT SP-6753 "Unknown topic config name: retention.min.timestamp" error observed after upgrade

Parmida Borhani — Fri, 17 Sep 2021 04:07:40 GMT

Revision 8 posted to Appian Knowledge Base by Parmida Borhani on 9/17/2021 4:07:40 AM

Symptoms

After upgrading from an older Appian version to a more recent one (example: 18.4 to 20.1), or applying a hotfix to an older version of Appian (example: 19.4), the following error is seen in the application server log during startup:

java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.InvalidConfigurationException: Unknown topic config name: retention.min.timestamp

The environment starts up normally and users are able to access it without any issues.

Cause

The error is due to a failure in applying the retention.min.timestamp configuration which is no longer required in the more recent version of Appian. The error is harmless but the configuration can be removed in order to stop the messages in the application server log.

Action

Check <APPIAN_HOME>/conf/custom.properties and <APPIAN_HOME>/services/conf/service_manager.conf to see if the retention.min.timestamp configuration is defined anywhere in these files.
If so, delete any references to the configuration from the files in step 1 and proceed to step 6. If there are no references to the configuration, proceed to step 3.
Navigate to <APPIAN_HOME> and run the following command to view all configurations of the topic (retention.min.timestamp should be in the output):
```
./services/kafka_2.13-2.7.0-appian-*/bin/kafka-configs.sh -bootstrap-server <SERVER_NAME>:9092 --entity-type topics --entity-name serviceManager.transaction.<ENGINE_NAME> --describe --all
```
- Replace <SERVER_NAME> with the name of the server running Kafka.
- Replace <ENGINE_NAME> with the name of each Appian Engine.
- Note: The command should be run for all Appian Engines, one at a time.

Delete the configuration for each Appian Engine:

./services/kafka_2.13-2.7.0-appian-*/bin/kafka-configs.sh -bootstrap-server <SERVER_NAME>:9092 --entity-type topics --entity-name serviceManager.transaction.<ENGINE_NAME> --alter --delete-config retention.min.timestamp

Re-run the command in step 3 and verify that the retention.min.timestamp configuration does not show up in the output anymore.
Restart Appian services as outlined in the documentation.
After performing these steps, confirm that the error message is no longer observed in the application server log.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2021

Tags: known issues, engines, installation, application server, upgrade, infrastructure, open issues

DRAFT SP-6753 "Unknown topic config name: retention.min.timestamp" error observed after upgrade

Parmida Borhani — Fri, 17 Sep 2021 04:04:57 GMT

Revision 7 posted to Appian Knowledge Base by Parmida Borhani on 9/17/2021 4:04:57 AM

Symptoms

After upgrading from an older Appian version to a more recent one (example: 18.4 to 20.1), the following error is seen in the application server log during startup:

java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.InvalidConfigurationException: Unknown topic config name: retention.min.timestamp

The environment starts up normally and users are able to access it without any issues.

Cause

Action

Check <APPIAN_HOME>/conf/custom.properties and <APPIAN_HOME>/services/conf/service_manager.conf to see if the retention.min.timestamp configuration is defined anywhere in these files.
If so, delete any references to the configuration from the files in step 1 and proceed to step 6. If there are no references to the configuration, proceed to step 3.
Navigate to <APPIAN_HOME> and run the following command to view all configurations of the topic (retention.min.timestamp should be in the output):
```
./services/kafka_2.13-2.7.0-appian-*/bin/kafka-configs.sh -bootstrap-server <SERVER_NAME>:9092 --entity-type topics --entity-name serviceManager.transaction.<ENGINE_NAME> --describe --all
```
- Replace <SERVER_NAME> with the name of the server running Kafka.
- Replace <ENGINE_NAME> with the name of each Appian Engine.
- Note: The command should be run for all Appian Engines, one at a time.

Delete the configuration for each Appian Engine:

./services/kafka_2.13-2.7.0-appian-*/bin/kafka-configs.sh -bootstrap-server <SERVER_NAME>:9092 --entity-type topics --entity-name serviceManager.transaction.<ENGINE_NAME> --alter --delete-config retention.min.timestamp

Re-run the command in step 3 and verify that the retention.min.timestamp configuration does not show up in the output anymore.
Restart Appian services as outlined in the documentation.
After performing these steps, confirm that the error message is no longer observed in the application server log.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2021

Tags: known issues, engines, installation, application server, upgrade, infrastructure, open issues

DRAFT SP-6753 "Unknown topic config name: retention.min.timestamp" error seen when starting up App-Server

Parmida Borhani — Fri, 17 Sep 2021 04:03:08 GMT

Revision 6 posted to Appian Knowledge Base by Parmida Borhani on 9/17/2021 4:03:08 AM

Symptoms

After upgrading from an older Appian version to a more recent one (example: 18.4 to 20.1), the following error is seen in the application server log during startup:

java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.InvalidConfigurationException: Unknown topic config name: retention.min.timestamp

The environment starts up normally and users are able to access it without any issues.

Cause

Action

Check <APPIAN_HOME>/conf/custom.properties and <APPIAN_HOME>/services/conf/service_manager.conf to see if the retention.min.timestamp configuration is defined anywhere in these files.
If so, delete any references to the configuration from the files in step 1 and proceed to step 6. If there are no references to the configuration, proceed to step 3.
Navigate to <APPIAN_HOME> and run the following command to view all configurations of the topic (retention.min.timestamp should be in the output):
```
./services/kafka_2.13-2.7.0-appian-*/bin/kafka-configs.sh -bootstrap-server <SERVER_NAME>:9092 --entity-type topics --entity-name serviceManager.transaction.<ENGINE_NAME> --describe --all
```
- Replace <SERVER_NAME> with the name of the server running Kafka.
- Replace <ENGINE_NAME> with the name of each Appian Engine.
- Note: The command should be run for all Appian Engines, one at a time.

Delete the configuration for each Appian Engine:

./services/kafka_2.13-2.7.0-appian-*/bin/kafka-configs.sh -bootstrap-server <SERVER_NAME>:9092 --entity-type topics --entity-name serviceManager.transaction.<ENGINE_NAME> --alter --delete-config retention.min.timestamp

Re-run the command in step 3 and verify that the retention.min.timestamp configuration does not show up in the output anymore.
Restart Appian services as outlined in the documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2021

Tags: known issues, engines, application server, upgrade, infrastructure, open issues, config

DRAFT SP-6753 "Unknown topic config name: retention.min.timestamp" error seen when starting up App-Server

Parmida Borhani — Fri, 17 Sep 2021 03:59:05 GMT

Revision 5 posted to Appian Knowledge Base by Parmida Borhani on 9/17/2021 3:59:05 AM

Symptoms

After upgrading from an older Appian version to a more recent one (example: 18.4 to 20.1), the following error is seen in the application server log during startup:

java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.InvalidConfigurationException: Unknown topic config name: retention.min.timestamp

The environment starts up normally and users are able to access it without any issues.

Cause

Action

Check <APPIAN_HOME>/conf/custom.properties and <APPIAN_HOME>/services/conf/service_manager.conf to see if the retention.min.timestamp configuration is defined anywhere in these files.
If so, delete any references to the configuration from the files in step 1 and proceed to step 6. If there are no references to the configuration, proceed to step 3.

Navigate to <APPIAN_HOME> and run the following command to view all configurations of the topic (retention.min.timestamp should be in the output): ./services/kafka_2.13-2.7.0-appian-*/bin/kafka-configs.sh -bootstrap-server <SERVER_NAME>:9092 --entity-type topics --entity-name serviceManager.transaction.<ENGINE_NAME> --describe --all

Replace <SERVER_NAME> with the name of the server running Kafka.
Replace <ENGINE_NAME> with the name of each Appian Engine.
- Note: The command should be run for all Appian Engines, one at a time.

Delete the configuration for each Appian Engine:

./services/kafka_2.13-2.7.0-appian-*/bin/kafka-configs.sh -bootstrap-server <SERVER_NAME>:9092 --entity-type topics --entity-name serviceManager.transaction.<ENGINE_NAME> --alter --delete-config retention.min.timestamp

Re-run the command in step 3 and verify that the retention.min.timestamp configuration does not show up in the output anymore.
Restart Appian services as outlined in the documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2021

Tags: known issues, engines, application server, upgrade, infrastructure, open issues, config

DRAFT SP-6753 "Unknown topic config name: retention.min.timestamp" error seen when starting up App-Server

Parmida Borhani — Fri, 17 Sep 2021 03:57:01 GMT

Revision 4 posted to Appian Knowledge Base by Parmida Borhani on 9/17/2021 3:57:01 AM

Symptoms

After upgrading from an older Appian version to a more recent one (example: 18.4 to 20.1), the following error is seen in the application server log during startup:

java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.InvalidConfigurationException: Unknown topic config name: retention.min.timestamp

The environment starts up normally and users are able to access it without any issues.

Cause

Action

Check the following files to see if the retention.min.timestamp configuration is defined:
- ```
<APPIAN_HOME>/conf/custom.properties
```
- ```
<APPIAN_HOME>/services/conf/service_manager.conf
```
If so, delete any references to the configuration from the files in step 1 and proceed to step 6. If there are no references to the configuration, proceed to step 3.
Navigate to <APPIAN_HOME> and run the following command to view all configurations of the topic (retention.min.timestamp should be in the output):
- ```
./services/kafka_2.13-2.7.0-appian-*/bin/kafka-configs.sh -bootstrap-server <SERVER_NAME>:9092 --entity-type topics --entity-name serviceManager.transaction.<ENGINE_NAME> --describe --all
```
  - Replace <SERVER_NAME> with the name of the server running Kafka.
  - Replace <ENGINE_NAME> with the name of each Appian Engine.
  - The command should be ran for all Appian Engines, one at a time.

Delete the configuration for each Appian Engine:

./services/kafka_2.13-2.7.0-appian-*/bin/kafka-configs.sh -bootstrap-server <SERVER_NAME>:9092 --entity-type topics --entity-name serviceManager.transaction.<ENGINE_NAME> --alter --delete-config retention.min.timestamp

Re-run the command in step 3 and verify that the retention.min.timestamp configuration does not show up in the output anymore.
Restart Appian services as outlined in the documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2021

Tags: known issues, engines, application server, upgrade, infrastructure, open issues, config

DRAFT SP-6753 "Unknown topic config name: retention.min.timestamp" error seen when starting up App-Server

Parmida Borhani — Fri, 17 Sep 2021 03:52:14 GMT

Revision 3 posted to Appian Knowledge Base by Parmida Borhani on 9/17/2021 3:52:14 AM

Symptoms

After upgrading from an older Appian version to a more recent one (example: 18.4 to 20.1), the following error is seen in the application server log during startup:

java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.InvalidConfigurationException: Unknown topic config name: retention.min.timestamp

The environment starts up normally and users are able to access it without any issues.

Cause

Action

Check the following files to see if the retention.min.timestamp configuration is defined:
- ```
<APPIAN_HOME>/conf/custom.properties
```
- ```
<APPIAN_HOME>/services/conf/service_manager.conf
```
If so, delete any references to the configuration from the files in step 1 and proceed to step 6. If there are no references to the configuration, proceed to step 3.
Navigate to <APPIAN_HOME> and run the following command to view all configurations of the topic (retention.min.timestamp should be in the output):
- ```
./services/kafka_2.13-2.7.0-appian-*/bin/kafka-configs.sh -bootstrap-server <SERVER_NAME>:9092 --entity-type topics --entity-name serviceManager.transaction.<ENGINE_NAME> --describe --all
```
  - <SERVER_NAME> should be replaced with the name of the server where Kafka is running.
  - <ENGINE_NAME> should be replaced with the name of each Appian Engine.
  - The command should be ran for all Appian Engines, one at a time.
Delete the configuration for each Appian Engine:
- ./services/kafka_2.13-2.7.0-appian-*/bin/kafka-configs.sh -bootstrap-server <SERVER_NAME>:9092 --entity-type topics --entity-name serviceManager.transaction.<ENGINE_NAME> --alter --delete-config retention.min.timestamp
Re-run the command in step 3 and verify that the retention.min.timestamp configuration does not show up in the output anymore.
Restart Appian services as outlined in: https://docs.appian.com/suite/help/latest/Starting_and_Stopping_Appian.html

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2021

Tags: known issues, engines, application server, upgrade, infrastructure, open issues, config

DRAFT SP-6753 "Unknown topic config name: retention.min.timestamp" error seen when starting up App-Server

Parmida Borhani — Fri, 17 Sep 2021 03:51:00 GMT

Revision 2 posted to Appian Knowledge Base by Parmida Borhani on 9/17/2021 3:51:00 AM

Symptoms

After upgrading from an older Appian version to a more recent one (example: 18.4 to 20.1), the following error is seen in the application server log during startup:

java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.InvalidConfigurationException: Unknown topic config name: retention.min.timestamp

The environment starts up normally and users are able to access it without any issues.

Cause

Action

Check the following files to see if the retention.min.timestamp configuration is defined:
- ```
<APPIAN_HOME>/conf/custom.properties
```
- ```
<APPIAN_HOME>/services/conf/service_manager.conf
```
If so, delete any references to the configuration from the files in step 1 and proceed to step 6. If there are no references to the configuration, proceed to step 3.
Navigate to <APPIAN_HOME> and run the following command to view all configurations of the topic (retention.min.timestamp should be in the output):
- ./services/kafka_2.13-2.7.0-appian-*/bin/kafka-configs.sh -bootstrap-server <SERVER_NAME>:9092 --entity-type topics --entity-name serviceManager.transaction.<ENGINE_NAME> --describe --all
  - <SERVER_NAME> should be replaced with the name of the server where Kafka is running.
  - <ENGINE_NAME> should be replaced with the name of each Appian Engine.
  - The command should be ran for all Appian Engines, one at a time.
Delete the configuration for each Appian Engine:
- ./services/kafka_2.13-2.7.0-appian-*/bin/kafka-configs.sh -bootstrap-server <SERVER_NAME>:9092 --entity-type topics --entity-name serviceManager.transaction.<ENGINE_NAME> --alter --delete-config retention.min.timestamp
Re-run the command in step 3 and verify that the retention.min.timestamp configuration does not show up in the output anymore.
Restart Appian services as outlined in: https://docs.appian.com/suite/help/latest/Starting_and_Stopping_Appian.html

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2021

Tags: known issues, engines, application server, upgrade, infrastructure, open issues, config

DRAFT SP-6753 "Unknown topic config name: retention.min.timestamp" error seen when starting up App-Server

Khalid Khan — Thu, 16 Sep 2021 02:18:15 GMT

Revision 1 posted to Appian Knowledge Base by Khalid Khan on 9/16/2021 2:18:15 AM

Symptoms

After upgrading from a much older Appian version to a more recent one (example: 18.4 to 20.1), the following error is seen in the app-server log when starting the app-server:

java.util.concurrent.ExecutionException: org.apache.kafka.common.errors.InvalidConfigurationException: Unknown topic config name: retention.min.timestamp

The app-server and other services/engines start up fine and the user is able to access the environment without any issues.

Cause

The error is caused due to a failure to apply some configuration which is no longer supported. This does not harm the site but should ideally be removed.

Action

Check the following files to see if the retention.min.timestamp configuration is defined anywhere:
1. ```
AE_HOME/conf/custom.properties
```
2. ```
AE_HOME/services/conf/service_manager.conf
```
Delete any reference to the configuration from within the files above.
Navigate to AE_HOME and run the following command to view all configurations of the topic (retention.min.timestamp should be in the output):
- ./services/kafka_2.13-2.7.0-appian-*/bin/kafka-configs.sh -bootstrap-server <SERVER_NAME>:9092 --entity-type topics --entity-name serviceManager.transaction.<ENGINE_NAME> --describe --all
  - <SERVER_NAME> should be replaced with the name of the server where Kafka is running.
  - <ENGINE_NAME> should be replaced with the name of each Appian Engine.
  - The command should be ran for all Appian Engines, one at a time.
Delete the configuration for each Appian Engine:
- ./services/kafka_2.13-2.7.0-appian-*/bin/kafka-configs.sh -bootstrap-server <SERVER_NAME>:9092 --entity-type topics --entity-name serviceManager.transaction.<ENGINE_NAME> --alter --delete-config retention.min.timestamp
Re-run the command in step 3 and verify that the retention.min.timestamp configuration does not show up in the output anymore.
Restart Appian services as outlined in: https://docs.appian.com/suite/help/latest/Starting_and_Stopping_Appian.html

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2021

Tags: known issues, engines, application server, upgrade, infrastructure, open issues, config