the user name and password have not been changed，However, suddenly java client requests database 401

[zhaiwanpeng711]

My Environment

• ArangoDB Version: 3.6.5

• Deployment Mode: Cluster

• Deployment Strategy: Manual Start

• Configuration:

• Infrastructure: own

• Operating System: Ubuntu

• Total RAM in your machine: 32Gb

• Disks in use:

• Used Package:

Component, Query & Data

Affected feature:

AQL query (if applicable):

AQL explain and/or profile (if applicable):

Dataset:

Size of your Dataset on disk:

Replication Factor & Number of Shards (Cluster only):

Steps to reproduce

Problem: After running for a while ,java sdk Client requests database，Client requests database 401,However, the user name and password have not been changed.Does arangodb have a protection mechanism to delete a user when resources are insufficient? Or the mechanism of initializing the database? Or will it corrupt the authentication file? The server is displaying an exception that memory keeps increasing。

arangodb logs of only two nodes are displayed :

arangod-coordinator-18119_1 (1).log
arangod-coordinator-18119_1.log
arangod-coordinator-18119.log
arangod-dbserver-18120_1.log
arangod-dbserver-18120.log
arangodb_1.log
arangodb.log

Expected result:

[dothebart]

Hi,
Please note that ArangoDB 3.6 has been EOL for a while now. Please upgrade to Arangodb 3.10 at least.

The issue you're seeing however is probably that you reach the EOL of the JWT: https://docs.arangodb.com/3.10/develop/http-api/authentication/#create-a-jwt-session-token

[zhaiwanpeng711]

Hi, Please note that ArangoDB 3.6 has been EOL for a while now. Please upgrade to Arangodb 3.10 at least.

The issue you're seeing however is probably that you reach the EOL of the JWT: https://docs.arangodb.com/3.10/develop/http-api/authentication/#create-a-jwt-session-token

First of all, thank you for your reply. Due to business reasons, I cannot upgrade to 3.10 in a short period of time. I just want to know whether authentication will be affected when resources are insufficient or some files are damaged. Why are insufficient resources and authentication failures having an impact? No operations such as user reset and permission change are displayed through log analysis

[dothebart]

Hi,
the session token remains intact, but for sure cursors go away if the process is restarted.