If a DB with a non-default db-port is used, the port has to specified in the runtime.csv on client and server side to successfully connect to the db. While for the connection this works fine, starting a simulation results in a server crash, because the simulation tries to connect to the default port.
This can be prevented by defining the DB_PORT parameter in one of the simulation specific csv files again. Thus the server stability is reduces, as one wrong simulation file results in a server crash. Also it complicates the transition of simulation files between different servers.
For comparison the DB_HOST parameter is successfully read from the initial runtime.csv file and does not need redefinition. I would expect the same behavior for the DB_PORT parameter.
If a DB with a non-default db-port is used, the port has to specified in the
runtime.csvon client and server side to successfully connect to the db. While for the connection this works fine, starting a simulation results in a server crash, because the simulation tries to connect to the default port. This can be prevented by defining theDB_PORTparameter in one of the simulation specific csv files again. Thus the server stability is reduces, as one wrong simulation file results in a server crash. Also it complicates the transition of simulation files between different servers. For comparison theDB_HOSTparameter is successfully read from the initialruntime.csvfile and does not need redefinition. I would expect the same behavior for theDB_PORTparameter.