KB-1915 How to find the stack trace of a thread in a leak suspects report

Jordan Horwat — Wed, 17 Apr 2019 13:24:41 GMT

Current Revision posted to Appian Knowledge Base by Jordan Horwat on 4/17/2019 1:24:41 PM

Purpose

After generating a Java heap dump, it is common for the corresponding leak suspects reports to contain clear suspects without associated stack traces to analyze. In these situations, it is often possible to find the relevant stack traces in the .threads file that is generated with the report. This is a useful step to take before requesting to analyze a raw heap dump.

Instructions

Navigate to the Thread Overview page of the leak suspects report via the Table of Contents or System Overview pages.
Identify the problematic thread(s) by their retained heap values (circled in green).
Copy the hexadecimal thread IDs from the Object / Stack Frame column of the problematic threads (circled in red).
Note: This ID is different from what is shown in the System Overview page.
Open the .threads file, found in the same directory where the leak suspects report was generated, and search for the thread IDs to find the respective thread stack traces.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2019

Tags: How To, heap, memory, application server, how-to, infrastructure

KB-1915 How to find the stack trace of a thread in a leak suspects report

Jordan Horwat — Wed, 17 Apr 2019 13:24:41 GMT

Revision 14 posted to Appian Knowledge Base by Jordan Horwat on 4/17/2019 1:24:41 PM

Purpose

Instructions

Navigate to the Thread Overview page of the leak suspects report via the Table of Contents or System Overview pages.
Identify the problematic thread(s) by their retained heap values (circled in green).
Copy the hexadecimal thread IDs from the Object / Stack Frame column of the problematic threads (circled in red).
Note: This ID is different from what is shown in the System Overview page.
Open the .threads file, found in the same directory where the leak suspects report was generated, and search for the thread IDs to find the respective thread stack traces.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2019

Tags: How To, heap, memory, application server, how-to, infrastructure

KB-1915 How to find the stack trace of a thread in a leak suspects report

Jordan Horwat — Wed, 17 Apr 2019 13:24:17 GMT

Revision 13 posted to Appian Knowledge Base by Jordan Horwat on 4/17/2019 1:24:17 PM

Purpose

Instructions

Navigate to the Thread Overview page of the leak suspects report via the Table of Contents or System Overview pages.
Identify the problematic thread(s) by their retained heap values (circled in green).
Copy the hexadecimal thread IDs from the Object / Stack Frame column of the problematic threads (circled in red).
Note: This ID is different from what is shown in the System Overview page.
Open the .threads file, found in the same directory where the leak suspects report was generated, and search for the thread IDs to find the respective thread stack traces.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2019

Tags: How To, heap, memory, application server, how-to, infrastructure

DRAFT KB-XXXX How to find the stack trace of a thread in a leak suspects report

Daniel DeVeau — Tue, 16 Apr 2019 20:56:38 GMT

Revision 12 posted to Appian Knowledge Base by Daniel DeVeau on 4/16/2019 8:56:38 PM

Purpose

Instructions

Navigate to the Thread Overview page of the leak suspects report via the Table of Contents or System Overview pages.
Identify the problematic thread(s) by their retained heap values (circled in green).
Copy the hexadecimal thread IDs from the Object / Stack Frame column of the problematic threads (circled in red).
Note: This ID is different from what is shown in the System Overview page.
Open the .threads file, found in the same directory where the leak suspects report was generated, and search for the thread IDs to find the respective thread stack traces.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2019

Tags: How To, heap, memory, application server, how-to, infrastructure

DRAFT KB-XXXX How to find the stack trace of a thread in a leak suspects report

Jordan Horwat — Tue, 16 Apr 2019 20:54:20 GMT

Revision 11 posted to Appian Knowledge Base by Jordan Horwat on 4/16/2019 8:54:20 PM

Purpose

Instructions

Navigate to the Thread Overview page of the leak suspects report via the Table of Contents or System Overview pages.
Identify the problematic thread(s) by their retained heap values (circled in green).
Copy the hexadecimal thread IDs from the Object / Stack Frame column of the problematic threads (circled in red).
Note: This ID is different from what is shown in the System Overview page.
Open the .threads file, found in the same directory where the leak suspects report was generated, and search for the thread IDs to find the respective thread stack traces.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2019

Tags: How To, heap, memory, application server, how-to, infrastructure

DRAFT KB-XXXX How to find the stack trace of a thread in a leak suspects report

Jordan Horwat — Tue, 16 Apr 2019 20:54:07 GMT

Revision 10 posted to Appian Knowledge Base by Jordan Horwat on 4/16/2019 8:54:07 PM

Purpose

After generating a Java heap dump, it is common for the corresponding leak suspects reports to contain clear suspects without associated stack traces to analyze.
In these situations, it is often possible to find the relevant stack traces in the .threads file that is generated with the report.
This is a useful step to take before requesting to analyze a raw heap dump.

Instructions

Navigate to the Thread Overview page of the leak suspects report via the Table of Contents or System Overview pages.
Identify the problematic thread(s) by their retained heap values (circled in green).
Copy the hexadecimal thread IDs from the Object / Stack Frame column of the problematic threads (circled in red).
Note: This ID is different from what is shown in the System Overview page.
Open the .threads file, found in the same directory where the leak suspects report was generated, and search for the thread IDs to find the respective thread stack traces.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2019

Tags: How To, heap, memory, application server, how-to, infrastructure

DRAFT INT-XXXX How to find the stack trace of a thread in a leak suspects report

Jordan Horwat — Tue, 16 Apr 2019 20:53:08 GMT

Revision 9 posted to Appian Knowledge Base by Jordan Horwat on 4/16/2019 8:53:08 PM

Purpose

After generating a Java heap dump, it is common for the corresponding leak suspects reports to contain clear suspects without associated stack traces to analyze.
In these situations, it is often possible to find the relevant stack traces in the .threads file that is generated with the report.
This is a useful step to take before requesting to analyze a raw heap dump.

Instructions

Navigate to the Thread Overview page of the leak suspects report via the Table of Contents or System Overview pages.
Identify the problematic thread(s) by their retained heap values (circled in green).
Copy the hexadecimal thread IDs from the Object / Stack Frame column of the problematic threads (circled in red).
Note: This ID is different from what is shown in the System Overview page.
Open the .threads file, found in the same directory where the leak suspects report was generated, and search for the thread IDs to find the respective thread stack traces.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2019

Tags: How To, heap, memory, application server, how-to, infrastructure

DRAFT INT-XXXX How to find the stack trace of a thread in a leak suspects report

Daniel DeVeau — Mon, 15 Apr 2019 17:13:13 GMT

Revision 8 posted to Appian Knowledge Base by Daniel DeVeau on 4/15/2019 5:13:13 PM

Purpose

It is common for leak suspects reports to contain clear suspects without associated stack traces to analyze.
In these situations, it is often possible to find the relevant stack traces in the .threads file that is generated with the report.
This is a useful step to take before requesting to analyze a raw heap dump.

Instructions

Navigate to the Thread Overview page of the leak suspects report via the Table of Contents or System Overview pages.
Identify the problematic thread(s) by their retained heap values (circled in green).
Copy the hexadecimal thread IDs from the Object / Stack Frame column of the problematic threads (circled in red).
Note: This ID is different from what is shown in the System Overview page.
Open the .threads file, found in the same directory where the leak suspects report was generated, and search for the thread IDs to find the respective thread stack traces.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2019

Tags: How To, heap, memory, application server, how-to, infrastructure

INT-XXXX How to find the stack trace of a thread in a leak suspects report

Daniel DeVeau — Mon, 15 Apr 2019 17:10:09 GMT

Revision 7 posted to Appian Knowledge Base by Daniel DeVeau on 4/15/2019 5:10:09 PM

Purpose

Instructions

Navigate to the Thread Overview page of the leak suspects report via the Table of Contents or System Overview pages.
Identify the problematic thread(s) by their retained heap values (circled in green).
Copy the hexadecimal thread IDs from the Object / Stack Frame column of the problematic threads (circled in red).
Note: This ID is different from what is shown in the System Overview page.
Open the .threads file, found in the same directory where the leak suspects report was generated, and search for the thread IDs to find the respective thread stack traces.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2019

Tags: How To, heap, memory, application server, how-to, infrastructure

INT-XXXX How to find the stack trace of a thread in a leak suspects report

Daniel DeVeau — Mon, 15 Apr 2019 17:09:43 GMT

Revision 6 posted to Appian Knowledge Base by Daniel DeVeau on 4/15/2019 5:09:43 PM

Purpose

Instructions

Navigate to the Thread Overview page of the leak suspects report via the Table of Contents or System Overview pages.
Identify the problematic thread(s) by their retained heap values (circled in green).
Copy the hexadecimal thread IDs from the Object / Stack Frame column of the problematic threads (circled in red).
Note: This ID is different from what is shown in the System Overview page.
Open the .threads file, found in the same directory where the leak suspects report was generated, and search for the thread IDs to find the respective thread stack traces.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2019

Tags: How To, heap, memory, application server, how-to, infrastructure

INT-XXXX How to find the stack trace of a thread in a leak suspects report

Daniel DeVeau — Mon, 15 Apr 2019 17:09:15 GMT

Revision 5 posted to Appian Knowledge Base by Daniel DeVeau on 4/15/2019 5:09:15 PM

Purpose

It is common for leak suspects reports to contain clear suspects without associated stack traces to analyze. In these situations, it is often possible to find the relevant stack traces in the .threads file that is generated with the report. This is a useful step to take before requesting to analyze a raw heap dump.

Instructions

Navigate to the Thread Overview page of the leak suspects report via the Table of Contents or System Overview pages.
Identify the problematic thread(s) by their retained heap values (circled in green).
Copy the hexadecimal thread IDs from the Object / Stack Frame column of the problematic threads (circled in red).
Note: This ID is different from what is shown in the System Overview page.
Open the .threads file, found in the same directory where the leak suspects report was generated, and search for the thread IDs to find the respective thread stack traces.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2019

Tags: How To, heap, memory, application server, how-to, infrastructure

INT-XXXX How to find the stack trace of a thread in a leak suspects report

Daniel DeVeau — Mon, 15 Apr 2019 17:06:46 GMT

Revision 4 posted to Appian Knowledge Base by Daniel DeVeau on 4/15/2019 5:06:46 PM

Purpose

It is common for leak suspects reports to contain clear suspects without associated stack traces to analyze.

In these situations, it is often possible to find the relevant stack traces in the .threads file that is generated with the report.

This is a useful step to take before requesting to analyze a raw heap dump.

Instructions

Navigate to the Thread Overview page of the leak suspects report via the Table of Contents or System Overview pages.
Identify the problematic thread(s) by their retained heap values (circled in green).
Copy the hexadecimal thread IDs from the Object / Stack Frame column of the problematic threads (circled in red).
Note: This ID is different from what is shown in the System Overview page.
Open the .threads file, found in the same directory where the leak suspects report was generated, and search for the thread IDs to find the respective thread stack traces.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2019

Tags: How To, heap, memory, application server, how-to, infrastructure

INT-XXXX How to find the stack trace of a thread in a leak suspects report

Daniel DeVeau — Mon, 15 Apr 2019 17:03:35 GMT

Revision 3 posted to Appian Knowledge Base by Daniel DeVeau on 4/15/2019 5:03:35 PM

Purpose

It is common for leak suspects reports to contain clear suspects without associated stack traces to analyze.

In these situations, it is often possible to find the relevant stack traces in the .threads file that is generated with the report.

This is a useful step to take before requesting to analyze a raw heap dump.

Instructions

Navigate to the Thread Overview page of the leak suspects report via the Table of Contents or System Overview pages.
Identify the problematic thread(s) by their retained heap values.
Copy the hexadecimal thread IDs from the Object / Stack Frame column of the problematic threads.
Note: This ID is different from what is shown in the System Overview page.
Open the .threads file, found in the same directory where the leak suspects report was generated, and search for the thread IDs to find the respective thread stack traces.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2019

Tags: How To, heap, memory, application server, how-to, infrastructure

INT-XXXX How to find the stack trace of a thread in a leak suspects report

Daniel DeVeau — Mon, 15 Apr 2019 17:02:15 GMT

Revision 2 posted to Appian Knowledge Base by Daniel DeVeau on 4/15/2019 5:02:15 PM

Purpose

It is common for leak suspects reports to contain clear suspects without associated stack traces to analyze.

In these situations, it is often possible to find the relevant stack traces in the .threads file that is generated with the report.

This is a useful step to take before requesting to analyze a raw heap dump.

Instructions

Navigate to the Thread Overview page of the leak suspects report via the Table of Contents or System Overview pages.
Identify the problematic thread(s) by their retained heap values.
Copy the hexadecimal thread IDs from the Object / Stack Frame column of the problematic threads.
Note: This ID is different from what is shown in the System Overview page.
Open the .threads file, found in the same directory where the leak suspects report was generated, and search for the thread IDs to find the respective thread stack traces.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: April 2019

Tags: How To, heap, memory, application server, how-to, infrastructure

INT-XXXX How to Investigate a leak suspects report with no stack trace

Daniel DeVeau — Mon, 15 Apr 2019 15:54:10 GMT

Revision 1 posted to Appian Knowledge Base by Daniel DeVeau on 4/15/2019 3:54:10 PM

This article serves as a template that you can copy/paste into a new article for use later on. This template can be used to outline steps on troubleshooting certain types of issues/enabling loggers/performing certain steps to achieve a desired outcome in the product. They must be relevant to Appian or any of the third-party software Appian uses to run, such as JBoss or MySQL. It can either be internal or external.

The title of the article must be under 256 characters (less depending on the types of characters used in the title as this is a limitation of Telligent). It must be as concise as possible. Those using the Knowledge Base should get a good idea of what the article is about just by reading the title.

This description is for informational purposes only. There should be no text above the "Purpose" header when using this template.

Purpose

This section is required for this template. A lot of the older How To articles might not have this section, but going forward we should try to keep a standard format. Provide a short statement about the purpose of this article.

Instructions

This section is required for this template. A lot of the older How To articles might not have this section, but going forward we should try to keep a standard format. Provide the instructions on how to achieve what the article is outlining.

Examples:

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: How To, heap, memory, application server, how-to, infrastructure