Configuration Settings on OrientDB Server 2.2.29 are not actually changing

[Eric24]

I need to make a couple of configuration changes to the default settings (script.pool.maxSize and db.pool.max). I've tried doing this using both the command-line approach and updating orientdb-server-config.xml. But after restarting the server with either or both of these in place, the console CONFIG command still returns both settings' default values. Is that expected? If so, how do I confirm that the new values have been accepted? If not, how do I go about setting those (and other) values?

[Mahatva1303]

What you are seeing is usually not expected if the configuration was applied correctly. In many cases, this happens because the values were changed in a config file that is not actually being loaded by the running server instance.

A few things to check:

• Make sure you edited the correct orientdb-server-config.xml used by the active server installation
• Verify there are no environment variables or startup scripts overriding the values
• Some settings may require a full server restart instead of a hot reload
• Check the startup logs carefully — OrientDB often logs overridden or loaded configuration values during boot

You can also try setting the values directly from the console:

config set script.pool.maxSize 50
config set db.pool.max 100

Then restart and check again with:

config get script.pool.maxSize
config get db.pool.max

If the values still revert to defaults, it may indicate:

• the settings are runtime-only,
• overridden elsewhere,
• unsupported in your current OrientDB version,
• or loaded from another configuration source.

One good way to confirm whether the values are actually active is through runtime behavior (thread pools, connection limits, logs, monitoring metrics) rather than relying only on the CONFIG output.

[Mahatva1303]

@Eric24 if this helps you with your query please mark it as answeres