![]() Issue display: you'll see the field "stored" value (the field key) on which the "No result template" is optionally applied.Field edit: no option available in the field editor.When a timeout is reached, the query to the remote database is aborted.Įlements Connect behavior depends on the context: The lower this value, the less impact a slow remote server might have on the Jira load time. This value can be configured from the datasource configuration, from 1 second to 600 seconds (10 minutes). Read timeout - A configurable timeout with a default value of 10 seconds applied to the "Read" step.Connect timeout - A non-configurable 5 seconds timeout applied to the "Connection" step.That's why two timeouts are set on Database datasources: Some queries may take a long time to return from the remote database because of the query itself or unusual load of the remote database.Ī long delay can have a negative impact on Jira load times, whether a user is editing or viewing an Issue. Read - Waiting for the remote database to return the result of a query.Connect - Establishing the connection to the remote database.Retrieving data from a database is done in two steps: If you don't know how to configure a Database datasource - contact a Database Administration (DBA) of your organization. ![]() If your database requires some specific parameters in the URL, you must use the Advanced mode. ![]() It suits most of the use cases.įorm options may vary depending on the selected database type.įrom the parameters you've set, Elements Connect will generate the connection URL to the database. With this mode, you'll be guided step by step by the form. Tomcat must be restarted once in order to have the driver loaded in the classpath.Įlements Connect offers two configuration modes for Database datasources, Simple and Advanced.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |