Hello -
Recently we have been getting some heap memory alerts, and as I looked at the active threads I noticed it showing 571 active, with 704 peak. After I restarted the GoAnywhere service we dropped back down to 47 active threads. Is there anyway to see what the thread connections are? I would like to see more details on what connections we have when alerts come across. Let me know if you need any other information on this. Thank You.
Is There A Way To Check Thread Usage?
Post any question you may have in regards to GoAnywhere MFT and let our talented support staff and other users assist you.
If you need a quicker response, please create a support ticket via the customer portal my.goanywhere.com or contact our support team by email at [email protected].
If you need a quicker response, please create a support ticket via the customer portal my.goanywhere.com or contact our support team by email at [email protected].
- Support_Jerrod Offline
- Support Specialist
- Posts: 11
- Joined: Wed Dec 13, 2017 5:52 pm
Re: Is There A Way To Check Thread Usage?
Hello Sam,
In order to see the details of each thread, a third-party tool will need to be used to plug into the JVM to generate a thread dump. From a GoAnywhere MFT perspective, the best way to get an idea of what the threads are doing is to survey the application. We recommend viewing active sessions (services > active sessions), active jobs (workflows > active jobs), monitors (workflows > monitors > active monitors), and triggers to better understand what the additional threads are. Please keep in mind that a certain number of threads are used upon initialization of the application and for basic operational functions. This includes indexing audit logs used to provide the powerful auditing capabilities that MFT delivers. If you have more questions about this, please feel free to reach out to our support team!
In order to see the details of each thread, a third-party tool will need to be used to plug into the JVM to generate a thread dump. From a GoAnywhere MFT perspective, the best way to get an idea of what the threads are doing is to survey the application. We recommend viewing active sessions (services > active sessions), active jobs (workflows > active jobs), monitors (workflows > monitors > active monitors), and triggers to better understand what the additional threads are. Please keep in mind that a certain number of threads are used upon initialization of the application and for basic operational functions. This includes indexing audit logs used to provide the powerful auditing capabilities that MFT delivers. If you have more questions about this, please feel free to reach out to our support team!