[ 
https://issues.apache.org/jira/browse/GUACAMOLE-1962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17859649#comment-17859649
 ] 

Nick Couchman commented on GUACAMOLE-1962:
------------------------------------------

[~phuleratribhuwan]: Could you provide more information about your environment 
- in particular, what authentication extension you're using to store the 
connections, and if you've made any code updates at all, or you're using the 
versions downloaded directly from the Guacamole web site?

I've tried this in both my production install of Guacamole (1.5.5), and my test 
instance (pre-1.6.0), with the PostgreSQL JDBC extension, and I am unable to 
reproduce that behavior. I've tried with both a single connection and multiple 
connections, and I do not get the error you're seeing.

> Error while killing session from Active Sessions
> ------------------------------------------------
>
>                 Key: GUACAMOLE-1962
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1962
>             Project: Guacamole
>          Issue Type: Bug
>          Components: guacamole
>    Affects Versions: 1.5.5
>            Reporter: Tribhuwan Phulera
>            Priority: Minor
>         Attachments: error.png, killsessionerror.har
>
>
> Hi Team,
> I'm encountering an error when trying to terminate an active session, as 
> shown in the attached image.
> The response from the ActiveConnection API is as follows:
> {
>     "message": "The extension providing this directory does not support 
> Atomic Operations. The patch cannot be executed.",
>     "translatableMessage": {
>         "key": "APP.TEXT_UNTRANSLATED",
>         "variables":
> {             "MESSAGE": "The extension providing this directory does not 
> support Atomic Operations. The patch cannot be executed."         }
>     },
>     "statusCode": null,
>     "expected": null,
>     "patches": null,
>     "type": "INTERNAL_ERROR"
> }
> I've spent two days searching online for a solution but haven't found anyone 
> else who has faced this issue before. Therefore, I'm raising it here in Jira. 
> Could you please help me understand under what circumstances this issue 
> occurs or if it's a bug? 
> Thank you.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to