KB-1581 Notification engines taking significant space on disk and not clearing

Parmida Borhani — Mon, 23 Jul 2018 03:34:54 GMT

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

Symptoms

Notification engines keep growing causing significant disk space usage on the environment.

Cause

Notification alerts generated by the application are cleared from the system when both of the following requirements are satisfied:

The alert is past its expiration limit.
The user associated with that notification logs in to Appian after the alert passes its expiration limit.

Action

Contact Appian Technical Support via support case to obtain a script to correct the problem.
Unzip the contents of the zip into <APPIAN_HOME>/_admin/_scripts.
Run executeAppianSupportScript.bat|sh based on the OS in a terminal.
Execute the deletenotificationsforusers script. The syntax is the following:
DeleteNotificationsForUsers --usernames (List of String) --expired (OPTIONAL) --beforedate (OPTIONAL Date yyyy-MM-dd)

Note: Users running getNotificationsCountForUsers --all will get a list of all users and their notification count. From that list, delete the notifications for users with the most notifications.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: May 2018

Tags: engines, infrastructure

KB-1581 Notification engines taking significant space on disk and not clearing

Nick Vigilante — Tue, 15 May 2018 13:34:21 GMT

Revision 13 posted to Appian Knowledge Base by Nick Vigilante on 5/15/2018 1:34:21 PM

Symptoms

Notification engines keep growing causing significant disk space usage on the environment.

Cause

Notification alerts generated by the application are cleared from the system when both of the following requirements are satisfied:

The alert is past its expiration limit.
The user associated with that notification logs in to Appian after the alert passes its expiration limit.

Action

Contact Appian Technical Support via support case to obtain a script to correct the problem.
Unzip the contents of the zip into <APPIAN_HOME>/_admin/_scripts.
Run executeAppianSupportScript.bat|sh based on the OS in a terminal.
Execute the deletenotificationsforusers script. The syntax is the following:
DeleteNotificationsForUsers --usernames (List of String) --expired (OPTIONAL) --beforedate (OPTIONAL Date yyyy-MM-dd)

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: May 2018

Tags: engines

[DRAFT] KB-XXXX Notification KDBs taking significant space on disk and not clearing

Nick Vigilante — Tue, 15 May 2018 09:33:24 GMT

Revision 12 posted to Appian Knowledge Base by Nick Vigilante on 5/15/2018 9:33:24 AM

Symptoms

Notification engines keep growing causing significant disk space usage on the environment.

Cause

Notification alerts generated by the application are cleared from the system when both of the following requirements are satisfied:

The alert is past its expiration limit.
The user associated with that notification logs in to Appian after the alert passes its expiration limit.

Action

Contact Appian Technical Support via support case to obtain a script to correct the problem.
Unzip the contents of the zip into <APPIAN_HOME>/_admin/_scripts.
Run executeAppianSupportScript.bat|sh based on the OS in a terminal.
Execute the deletenotificationsforusers script. The syntax is the following:
DeleteNotificationsForUsers --usernames (List of String) --expired (OPTIONAL) --beforedate (OPTIONAL Date yyyy-MM-dd)

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: May 2018

Tags: engines

[DRAFT] KB-XXXX Notification KDBs taking significant space on disk and not clearing

Stephen Okala — Wed, 09 May 2018 17:00:48 GMT

Revision 11 posted to Appian Knowledge Base by Stephen Okala on 5/9/2018 5:00:48 PM

Symptoms

Notification engines keep growing causing significant disk space usage on the environment.

Cause

Notification alerts generated by the application that should clear up once they are past their expiration limit, but it requires the user account to login for the automated clearing to occur.

Action

Contact Appian Technical Support via support case to obtain a script to correct the problem.
Unzip the contents of the zip into <APPIAN_HOME>/_admin/_scripts
Run executeAppianSupportScript.bat|sh based on the OS in a terminal.
Execute the deletenotificationsforusers script. The syntax is the following:
- DeleteNotificationsForUsers --usernames (List of String) --expired (OPTIONAL) --beforedate (OPTIONAL Date yyyy-MM-dd)

Note: Users running getNotificationsCountForUsers --all will get a list of all users and their notification count. From that delete the notifications for users with the most notifications.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2018

Tags: engines

[DRAFT] KB-XXXX Notification KDBs taking significant space on disk and not clearing

Khanh Tran — Tue, 27 Mar 2018 14:44:41 GMT

Revision 10 posted to Appian Knowledge Base by Khanh Tran on 3/27/2018 2:44:41 PM

Symptoms

Notification KDBs keep growing and doesn't seem to free up causing significant disk space usage on the environment.

Cause

Notification alerts generated by the application that should clear up once they are past their expiration limit, but it requires the user account to actually login for the automated clearing to occur.

Action

Contact Appian Technical Support for the correct version of the script based on the version of Appian used.
Unzip the contents of the zip into <APPIAN_HOME>/_admin/_scripts
Run executeAppianSupportScript.bat|sh based on your OS in a terminal
Execute the deletenotificationsforusers script. The syntax is the following:
- DeleteNotificationsForUsers --usernames (List of String) --expired (OPTIONAL) --beforedate (OPTIONAL Date yyyy-MM-dd)

Note: For environments with a lot of user, running getNotificationsCountForUsers --all will get a list of all users and their notification count. From that, you can delete the notifications for users with the most notifications.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2018

Tags: engines

[DRAFT] KB-XXXX Notification KDBs taking significant space on disk and not clearing

Khanh Tran — Tue, 27 Mar 2018 14:43:19 GMT

Revision 9 posted to Appian Knowledge Base by Khanh Tran on 3/27/2018 2:43:19 PM

Symptoms

Notification KDBs keep growing and doesn't seem to free up causing significant disk space usage on the environment.

Cause

Action

Contact Appian Technical Support for the correct version of the script based on the version of Appian used.

Unzip the contents of the zip into <APPIAN_HOME>/_admin/_scripts

Run executeAppianSupportScript.bat|sh based on your OS in a terminal
Execute the deletenotificationsforusers script. The syntax is the following:
- DeleteNotificationsForUsers --usernames (List of String) --expired (OPTIONAL) --beforedate (OPTIONAL Date yyyy-MM-dd)

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2018

Tags: engines

[DRAFT] KB-XXXX Notification KDBs taking significant space on disk and not clearing

Khanh Tran — Tue, 27 Mar 2018 14:01:32 GMT

Revision 8 posted to Appian Knowledge Base by Khanh Tran on 3/27/2018 2:01:32 PM

Symptoms

Notification KDBs keep growing and doesn't seem to free up causing significant disk space usage on the environment.

Cause

Action

Contact Appian Technical Support for the correct version of the script based on the version of Appian used.
Unzip the contents of the zip into <appian home>/_admin/_scripts
Run executeAppianSupportScript.bat|sh based on your OS in a terminal
Execute the deletenotificationsforusers script. The syntax is the following:
- DeleteNotificationsForUsers --usernames (List of String) --expired (OPTIONAL) --beforedate (OPTIONAL Date yyyy-MM-dd)

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2018

Tags: engines

[DRAFT] KB-XXXX Notification KDBs taking significant space on disk and not clearing

Khanh Tran — Tue, 27 Mar 2018 13:59:53 GMT

Revision 7 posted to Appian Knowledge Base by Khanh Tran on 3/27/2018 1:59:53 PM

Symptoms

Notification KDBs keep growing and doesn't seem to free up causing significant disk space usage on the environment.

Cause

Action

Contact Appian Technical Support for the correct version of the script based on the version of Appian used.
Unzip the contents of the zip into <appian home>/_admin/_scripts
Run executeAppianSupportScript.bat|sh based on your OS in a terminal
Execute the deletenotificationsforusers script. The syntax is the following:
- DeleteNotificationsForUsers --usernames (List of String) --expired (OPTIONAL) --beforedate (OPTIONAL Date yyyy-MM-dd)

Note: For environments with a lot of user, running getNotificationsCountForUsers --all will get a list of all users and their notification count. From that, you can delete the notifications for users with the most notifications.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2018

Tags: engines

[DRAFT] KB-XXXX Notification KDBs taking significant space on disk and not clearing

Khanh Tran — Tue, 27 Mar 2018 13:10:51 GMT

Revision 6 posted to Appian Knowledge Base by Khanh Tran on 3/27/2018 1:10:51 PM

Symptoms

Notification KDBs keep growing and doesn't seem to free up causing significant disk space usage on the environment.

Cause

Action

Contact Appian Technical Support for the correct version of the script based on the version of Appian used.
Unzip the contents of the zip into <appian home>/_admin/_scripts
Run executeAppianSupportScript.bat|sh based on your OS in a terminal
Execute the deletenotificationsforusers script. The syntax is the following:
- DeleteNotificationsForUsers --usernames (List of String) --expired (OPTIONAL) --beforedate (OPTIONAL Date yyyy-MM-dd)

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2018

Tags: engines

[DRAFT] KB-XXXX Notification KDBs taking significant space on disk and not clearing

Khanh Tran — Tue, 27 Mar 2018 13:10:34 GMT

Revision 5 posted to Appian Knowledge Base by Khanh Tran on 3/27/2018 1:10:34 PM

Symptoms

Notification KDBs keep growing and doesn't seem to free up causing significant disk space usage on the environment.

Cause

Action

Contact Appian Technical Support for the correct version of the script based on the version of Appian used.
Unzip the contents of the zip into <appian home>/_admin/_scripts
Run executeAppianSupportScript.bat|sh based on your OS in a terminal
Execute the deletenotificationsforusers script. The syntax is the following:
- DeleteNotificationsForUsers --usernames (List of String) --expired (OPTIONAL) --beforedate (OPTIONAL Date yyyy-MM-dd)

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2018

Tags: engines

[DRAFT] KB-XXXX Notification KDBs taking significant space on disk and not clearing

Khanh Tran — Tue, 27 Mar 2018 13:09:29 GMT

Revision 4 posted to Appian Knowledge Base by Khanh Tran on 3/27/2018 1:09:29 PM

Symptoms

Notification KDBs keep growing and doesn't seem to free up causing significant disk space usage on the environment.

Cause

Action

Contact Appian Technical Support for the correct version of the script based on the version of Appian used.
Unzip the contents of the zip into <appian home>/_admin/_scripts
Run executeAppianSupportScript.bat|sh based on your OS in a terminal
Execute the deletenotificationsforusers script. The syntax is the following: DeleteNotificationsForUsers --usernames (List of String) --expired (OPTIONAL) --beforedate (OPTIONAL Date yyyy-MM-dd)

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2018

Tags: engines

[DRAFT] KB-XXXX Notification KDBs taking significant space on disk and not clearing

Khanh Tran — Tue, 27 Mar 2018 13:09:03 GMT

Revision 3 posted to Appian Knowledge Base by Khanh Tran on 3/27/2018 1:09:03 PM

Symptoms

Notification KDBs keep growing and doesn't seem to free up causing significant disk space usage on the environment.

Cause

Action

Contact Appian Technical Support for the correct version of the script based on the version of Appian used.
Unzip the contents of the zip into <appian home>/_admin/_scripts
Run executeAppianSupportScript.bat|sh based on your OS in a terminal
Execute the deletenotificationsforusers script. The syntax is the following: DeleteNotificationsForUsers --usernames (List of String) --expired (OPTIONAL) --beforedate (OPTIONAL Date yyyy-MM-dd)

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2018

Tags: engines

[DRAFT] KB-XXXX Notification KDBs taking significant space on disk and not clearing

Khanh Tran — Tue, 27 Mar 2018 13:08:30 GMT

Revision 2 posted to Appian Knowledge Base by Khanh Tran on 3/27/2018 1:08:30 PM

Symptoms

Notification KDBs keep growing and doesn't seem to free up causing significant disk space usage on the environment.

Cause

Action

Contact Appian Technical Support for the correct version of the script based on the version of Appian used.
Unzip the contents of the zip into <appian home>/_admin/_scripts
Run executeAppianSupportScript.bat|sh based on your OS in a terminal
Execute the deletenotificationsforusers script. The syntax is the following: DeleteNotificationsForUsers --usernames (List of String) --expired (OPTIONAL) --beforedate (OPTIONAL Date yyyy-MM-dd)

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2018

Tags: engines

[DRAFT] KB-XXXX Notification KDBs taking significant space on disk and not clearing

Khanh Tran — Tue, 13 Feb 2018 15:33:38 GMT

Revision 1 posted to Appian Knowledge Base by Khanh Tran on 2/13/2018 3:33:38 PM

Symptoms

This section is required for this template. All symptoms of the issue, including relevant screenshots and log lines, should be included here. The symptoms should be as descriptive as possible.

Cause

This section is required for this template. When writing a cause for a particular article, ensure the following is taken into consideration:

The cause is concise and does not disclose more information than absolutely necessary.
The cause does not share any Appian source code. Source code for plugins/shared components are fine.
If this is an issue outside of the Appian product and the third-party vendor included documentation referencing the bug, provide their documentation for reference.

For any enhancements/defects, use one of the following as applicable:

This issue has been reported to the Appian Product Team. The reference number for this issue is AN-XXXXX.
This product use case has been logged to the Appian Product Team for consideration to add this functionality in the product. Kindly note it is not Appian Support’s policy to disclose how or when a product use case will be implemented.
This issue has been addressed via AN-XXXXX in Appian X.X Hotfix Package X.
This issue has been addressed via AN-XXXXX in the following hotfixes/versions:
- List each specific hotfix package/version in ascending order by version.
This use case has been incorporated in Appian X.X Hotfix Package X.
This use case has been incorporated in the following versions/hotfixes:
- List each specific hotfix package/version in ascending order by version.

Note: When listing hotfixes, add a hyperlink to the Hotfix documentation for that version.

When logging a product defect, ensure you use the known issues tag as well as the open issues or fixed issues tag, depending if the issue is fixed or not.

If no cause is known and this is not something Engineering can reproduce/needs to know about, then say “The root cause of this issue is currently unknown.” If you use that as your cause, then a valid action must be present.

Action

This section is required for this template and contains the steps to resolve the issue. If an issue in an article is solved by a hotfix and/or major version of Appian, use the following language to indicate that:

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

If there is a product issue with Engineering that is open and a workaround for that issue exists, include it in the Action section until the fix is available. After the fix is made available, use that as a workaround instead.

Otherwise, the content in this section should wholly solve a customer’s issue without producing any undesirable side effects. If there is at least one valid action that doesn’t cause undesirable side effects, all other actions with negative side effects should go in the Workaround section.

Workaround

This section is optional and should only be used as an alternative action if there is a massive technical debt associated with performing the action in the above section for customers (such as upgrading). It can also be used if there is a solution to the issue in the article but is more inconvenient to implement or it causes other undesirable behavior and wouldn’t warrant being an action.

Affected Versions

This section includes any relevant version information for Appian or other third/party configurations. Some examples of valid affected versions are as follows:

This article applies to all versions of Appian.
This article applies to Appian 7.11 and later.
This article applies to Appian 16.2 and earlier.
This article applies to Appian 7.11 and 16.1.
This article applies to Appian 16.1, 16.2, and 16.3.
This article applies to all versions of Appian from Appian 7.10 to Appian 16.2.
This article applies to all versions of Appian using JBoss EAP 6.4.9 as an application server and Internet Explorer 9 as a web browser.
This article applies to all versions of Appian Cloud.

Last Reviewed: Month YYYY

Tags: engines