I am also using the token API and Logout API and it always responds. *TO GET TOKEN :-*
1. Request URL: https://hostname/guacamole/api/tokens 2. Request Method: POST 3. Status Code: 200 OK 4. Remote Address: hostname:443 5. Referrer Policy: origin-when-cross-origin *TO DELETE TOKEN :-* 1. Request URL: https://hostname/guacamole/api/tokens/7DAA03E7D8ED357CC24F34515484BDC838B72B19F73D3F90A9E5546DA4465956 2. Request Method: DELETE 3. Status Code: 204 No Content 4. Remote Address: hostname:443 5. Referrer Policy: origin-when-cross-origin My suggestion would be to checkout latest code of *guacamole-client *and *guacamole-server *and then test without doing any changes in the code or without calling any API ( using *user-mapping.xml*). *<user-mapping>* * <!-- Per-user authentication and config information -->* * <authorize username="admin" password="admin">* * <connection name="Windows Server">* * <protocol>rdp</protocol>* * <param name="hostname">XXXX</param>* * <param name="port">3389</param>* * <param name="resize-method">reconnect</param>* * <param name="domain">xxxx</param>* * <param name="username">amarjeet.singh</param>* * <param name="password">xxxxxx</param>* * </connection>* * </authorize>* </*user-mapping>* If issue still exists, then take the *tcpdump *for the delay. *NOTE :* If you haven't done any changes in guacamole-client and guacamole-server code that means the issue is not with the API. As Nick said you can always check the *logs of guacamole-client and guacamole-server*. For memory consumption, please check which process is consuming more memory using *top command. * Check if it is guacd or java . *On Wed, Jan 16, 2019 at 6:12 PM Shilpa Bhandari <[email protected] <[email protected]>> wrote:* > 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 >> >
