Explorer for Endevor response delay for LIST ELEMENT

Products

• Endevor

Issue/Introduction

This issue looks to be in Explorer for Endevor v1.6.0 VSCode extension when listing elements for an Endevor location.There is a 120 second delay between the Endevor Web Services (EWS) API issuing a response and VSCode formatting that response to the screen.  The delay is always 120 seconds (+/-1).

To workaround it, have found that installing a previous version (1.5.3), always seems to work fine, then reload and then reinstall 1.6.0 (1.5.4 doesn't help - first noticed the problem in this version).  However this does not work all the time, and the issue will return.  Uninstall and reinstall 1.6.0 does not work.

Note the timestamps in the 'EXPLORER FOR ENDEVOR' log (09:21 -> 09:23) versus the APIMSG output (09:21):




It can be in a different order depending on what finished last (10:14 -> 10:16):

Also, note that 'zowe endevor list elements' is pretty much instantaneous:

Environment

VSCode 1.86.1  (Windows 10 Enterprise)
Explorer for Endevor - v1.6.0
Endevor API version 2.15-20230727-3e83a9ce

Resolution

The Endevor Sys Prog recycled Endevor Web Services (EWS) STC and the delay was resolved.
Endevor Engineering's investigation also led them to believe that the root cause might be somewhere on the Endevor Web Services (EWS) side (or possibly networking issues).
The Tomcat access logs ("<tomcat>/logs/localhost_access_log.<date>") from the dates where delays were experienced will show the end-to-end time for the request/response. However, they were no longer available.

The Sys Prog suspects that the root cause was an ‘overload’ due to a continuous LIST request. Endevor Bridge for Git (B4G) had been set up by a user to do a sync-back every minute for a very large project. It had high CPU utilization and that sync-back has since been turned off.
If it is turned back on further consideration of timing will be done i.e. best to do it manually when required and set up the Endevor to B4G Webhook.