Absent Member.. Pamela Harrod Absent Member..
Absent Member..
200 views

(OO) Support Tip: How to resolve flows stuck in running state?

How to resolve flows stuck in running state?

Summary:
1. The root cause for certain flows to never finish is that the following operations wait forever if the corresponding service goes down in the middle (e.g., SA or SFS): SSH Command, Http Client Get, Http Client Put, Http Client Post. The corresponding worker threads become blocked, which deteriorates the OO performance.
2. The current workaround is to delete all active runs and restart.
3. This is supposed to be solved by the planned flow timeout feature

Regarding the HTTP Client v1.0 operations, these operations have two timeout inputs (see detail below). Timeout which represents the connection timeout (the maximum waiting time in order to establish a connection). SocketTimeout which represents the maximum period inactivity between two consecutive data packets.
** The socketTimeout is the appropriate input for the scenario described in the incident and should be set accordingly.

Regarding the SSH v1.0 operations, the timeout input functions the same way as the socketTimeout input from the HTTP Client v1.0 operations.

Http Client Get
timeout - the time to wait for a connection to be established, in milliseconds.
socketTimeout - the time to wait for data to be retrieved, in milliseconds.

Http client Post
timeout - the time to wait for a connection to be established, in milliseconds.
socketTimeout - the time to wait for data to be retrieved, in milliseconds.

Http Client Put
timeout - the time to wait for a connection to be established, in milliseconds.
socketTimeout - the time to wait for data to be retrieved, in milliseconds.

SSH Command
Timeout - time in milliseconds to wait for the command to complete.

SSH Shell
Timeout - (optional) time in milliseconds to wait for the command to complete.

Please see the knowledge document at http://support.openview.hp.com/selfsolve/document/KM01935582

Labels (2)
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.