runtimeGroupActivationCheckInterval property

Specifies the duration, in minutes, to wait before pureQuery™ Runtime checks for the activation of a pureQuery runtime group. When pureQuery Runtime detects that a runtime group was activated, pureQuery Runtime retrieves updated runtime properties and pureQueryXML data from the runtime group version and uses the updated information.

The property runtimeGroupActivationCheckInterval must be set as a global property. The property must be set so that it applies to all pureQuery Runtime instances that run in a JVM. For information about specifying the property, see Usage notes.

pureQuery Runtime uses the property runtimeGroupActivationCheckInterval when all of the following are true:
  • The application that runs in the JVM is enabled with pureQuery client optimization.
  • The pureQuery application accesses a repository that is created in a database. The location that is specified by the property finalRepositoryProperties is a repository that is created in a database.
  • The value of the pureQuery Runtime property propertiesRefreshInterval for the application is a non-negative integer.

This property can take the following values:

Positive-integer
Specifies the duration, in minutes, to wait before pureQuery Runtime checks for the activation of a runtime group version. The default value for this property is 2

When you activate the runtime group version in a repository, pureQuery Runtime checks for updates to the pureQuery information in the runtime group version.

You activate a runtime group version with the ManageRepository utility option -activate runtimeGroup or from IBM® Data Studio.

Note: If the value of the property propertiesRefreshInterval is a negative integer for a runtime group, the checking for the activation of the runtime group is disabled. pureQuery Runtime does not refresh runtime properties and pureQueryXML data when the runtime group version is activated.
0 | negative-integer
When the value of runtimeGroupActivationCheckInterval is set to 0 or a negative integer, checking for the activation of runtime group versions is disabled.

Usage notes

The property can be specified only as a global property. The property cannot be specified for an application or an application data source connection. The value of the property applies to all pureQuery Runtime instances that run in a JVM. For example, you can specify the property in the following manner:
  • As part of the JVM startup by using Java™ command-line syntax. The following Java command starts the Java application mypdqapp, and sets the value of the runtimeGroupActivationCheckInterval property to 7:
     java -Dpdq.runtimeGroupActivationCheckInterval=7 mypdqapp
  • In a global pureQuery runtime properties file. The following line in a runtime properties file specifies that checking for runtime group activation occurs every 4 minutes.
    pdq.runtimeGroupActivationCheckInterval=4
The property cannot be set in the following manner:
  • Specified in a pdq.appwide.properties file or a pdq.name.properties file
  • Passed as part of the connection-specific URL properties string of a data source or a driver manager connection
  • Specified as part of a db2.jcc.pdqProperties property.

The pureQuery Runtime properties runtimeGroupActivationCheckInterval and propertiesRefreshInterval control the automatic refresh of pureQuery information for runtime group versions. The property propertiesRefreshInterval can be used to specify a specific interval to check for updates to pureQuery information for a runtime group version. propertiesRefreshInterval can also be set to disable all checking for updated pureQuery information for the runtime group version, including the checking that occurs when a runtime group version is activated.

To control the automatic refresh for multiple pureQuery applications that run in a single JVM, you set the value of the runtimeGroupActivationCheckInterval property to control the majority of the refresh activity. You set the value propertiesRefreshInterval for specific applications have special refresh requirements.

After pureQuery Runtime retrieves pureQuery data, pureQuery updates SQL statements in an application server statement cache as required. Existing SQL statements from the application server statement cache are re-prepared when it is safe to do so. Typically, a statement can be re-prepare when the cached statement is in the same state as the state of a newly created statement.


Feedback