One more thing. The memory consumption by Guacamole reached upto 90-100% when this issue occurred. CPU utilization was also ~70%. I'm working with 5 Guac users and 5 remoting instances.
Thanks and regards, Shilpa Bhandari On Wed, Jan 16, 2019 at 5:34 PM Nick Couchman <[email protected]> wrote: > On Wed, Jan 16, 2019 at 6:44 AM Shilpa Bhandari < > [email protected]> wrote: > >> In my case I made 3-4 calls to Guac API to delete a token but it didn't >> give any response for those and after 4-5 minutes it sent response for >> those calls as 404 Token not found. Meanwhile there were some other calls >> also to Guac API to fetch new tokens and those calls also got responded >> with this much delay. >> > > Yes, this is not expected behavior for Guacamole, and indicates either an > issue with the system running Guacamole Client (Tomcat) or the network > between the web browser and the server. > > -Nick >
