Data privacy notice

 

When this content is loaded, usage information is transmitted to Vimeo and may be processed there.

 

             

Database properties

Modified on Fri, 14 Jul, 2023 at 2:21 PM

The file database.properties stores several settings related to the database, such as the login credentials.

You should edit database related settings via the user interface. Please note that some of these properties are stored encrypted.


 Property Default valueEncrypted Explanation
db.connection.login.password-yesPassword for accessing the database.
db.connection.login.username-yesUser name for accessing the database.
db.connection.jdbcurl-noThe JDBC connection URL to the database.
db.connection.connnections.max50noThe maximum size that the connection pool is allowed to reach, including both idle and in-use connections. 
db.connection.connnections.timeout200noThe maximum amount of time in seconds that a connection is allowed to sit idle in the connection pool. A value of 0 means that idle connections are never removed from the pool. Otherwise, the minimum allowed value is 10.
db.connection.connnections.unreturned.timeout0noThe maximum lifetime in milliseconds of a connection in the connection pool. A value of 0 indicates no maximum lifetime. However, the db.connection.connnections.timeout setting still applies.
db.connection.connnections.leakdetection_threshold0noThe amount of time in milliseconds that a connection can be out of the connection pool before a message is logged indicating a possible connection leak. A value of 0 means that leak detection is disabled. Lowest acceptable value for enabling leak detection is 2000.
db.connection.dbms.shortname-noThe type of database management system. Possible values are mysql (MySQL), oracle (Oracle), postgresql (PostgreSQL), sqlserver (SQLServer), and h2db (H2 Server).
7.1.0+  db.auto.updatetruenoWhen enabled, all available database and system updates are run automatically when the formcycle application is started. This setting can also be overriden via the JVM parameter xfcAutoUpdate.
7.1.0+  db.update.callback.mails(empty)noWhen the automatic update finishes, a report is sent to these mail addresses. The report contains the status of the update (success or error) and information about the error, if one occurred. This setting can also be overriden via the JVM parameter xfcUpdateCallbackEmails.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article