propertiesRefreshInterval property

Specifies when pureQuery® Runtime checks the location of stored pureQuery data for changes to pureQuery runtime properties or pureQueryXML data after application startup. When pureQuery Runtime detects updates, pureQuery Runtime retrieves the updated runtime properties and pureQueryXML data and uses the updated information.

For an application that is enabled with pureQuery client optimization, pureQuery Runtime checks the location specified by the finalRepositoryProperties property. If the location is a repository created in a database, pureQuery Runtime checks the active runtime group version for the runtime group specified by the propertiesGroupId property.

This property can take the following values:

Positive-integer
Specifies the duration, in minutes, to wait before pureQuery Runtime checks the location of stored pureQuery data for changes to pureQuery properties or pureQueryXML data for the runtime group version.
0
Specifies that pureQuery Runtime checks for updates after the runtime group has been activated. 0 is the default value.

After you activate a runtime group version in the repository, pureQuery Runtime checks for updates to the pureQuery information in that runtime group version. By default, pureQuery Runtime checks the status of runtime groups once every two minutes. The pureQuery runtime property runtimeGroupActivationCheckInterval controls the duration between checks.

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

-1
Disables checking for updates.

Usage notes

The propertiesRefreshInterval property is ignored when using pureQuery enabled applications with the inline methods or annotated methods.

When all the following conditions are satisfied, the outputPureQueryXml property must be specified and cannot specify the same file as the pureQueryXml property. If the pureQueryXml property is specified:
  • The propertiesRefreshInterval property is specified and captured SQL data are being generated.
  • The finalRepositoryProperties property specifies a path to a directory on a file system.

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.

The pureQuery Runtime properties runtimeGroupActivationCheckInterval and propertiesRefreshInterval control the automatic refresh of pureQuery information for runtime group versions. The property runtimeGroupActivationCheckInterval controls when pureQuery Runtime checks for activated runtime group versions. runtimeGroupActivationCheckInterval must be set so that it applies to all pureQuery Runtime instances that run in a JVM.

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 that have special refresh requirements.

The propertiesRefreshInterval property requires the creation of a timer thread. In some environments, a thread cannot be created, and this property is ignored. The following environments prohibit timer thread creation:
  • DB2® z/OS® Java™ stored procedure
  • CICS®

Checking for updates to pureQuery runtime properties or pureQueryXML data is disabled when the cmx.controllerDiscoveryInterval property is set to -2. Setting the property to -2 disables automatic discovery for InfoSphere® Optim™ Performance Manager Extended Insight.


Feedback