[ https://issues.apache.org/jira/browse/GUACAMOLE-1962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17859736#comment-17859736 ]
Tribhuwan Phulera commented on GUACAMOLE-1962: ---------------------------------------------- Is there some issue with maven build. Coz I tried to compile war to commit hash: eb31d5e82df2c299afa15215741f718153967698 which is around same at release of 1.5.5 version. But also getting same error. But the error is not reproducable in [https://guacamole.apache.org/releases/1.5.5/] provided release. I am using maven Version and Java verion details below: root@btspldevremote01:/project/guacamole-client# /project/apache-maven-3.9.8/bin/mvn -v Apache Maven 3.9.8 (36645f6c9b5079805ea5009217e36f2cffd34256) Maven home: /project/apache-maven-3.9.8 Java version: 11.0.23, vendor: Ubuntu, runtime: /usr/lib/jvm/java-11-openjdk-amd64 Default locale: en, platform encoding: UTF-8 OS name: "linux", version: "5.15.0-1059-oracle", arch: "amd64", family: "unix" At compilation getting Successful build for all. > 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-auth-jdbc-mysql > 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)