This release introduces beta APIs for using indexes and querying from Talon applications. The Javadoc for AepEngine class provides more information.

This release enhance the ODS store to track the total size of data that it holds and emit it along with store statistics in heartbeats. The store data size statistic captures the sum of serialized data size of the objects that it holds. This is a useful metric for determining the size of the data held in the store exclusive of java object overhead.

See Also:

• IStoreBindingStats.html.getDataSize()

• SrvMonAppStoreBindingStats.html.getDataSize()

  ODS
  STATS AND ALERTS

This release allows shutting down a Talon XVM using the Talon XVM Entrypoint class (com.neeve.server.Main) by specifying the option '-a shutdown'. For example, if an XVM was started with

If can be subsequently shutdown gracefully using:

Compatibility Notes:

Note the -a / --action option replaces the former deprecated option -a which used to allow specifying an app descriptor to launch. This release formally removes support for specifying an app descriptor.

This release enhances the Talon archetypes to include xvm scripts in project's packaged distribution. New projects created from the archetypes can launch xvms by issuing:

Full usage for the xvm script can be displayed via:

This release changes the code generated by ADM for collection nodes by moving more of the implementation code into the platform collection base classes.
Compatibility Notes:

This change increments the ADM compatibility level to 3.9.0; collections generated with this version of the platform require APIs not available in earlier releases.

This change also removes the methods first, next previous and last from the generated queues.

This release fixes an issue in the nvx-talon-sr-processor-archetype in which the outbound event type specified in the archetypes is not properly used.

This release fixes a bug in which the method com.neeve.server.embedded.EmbeddedXVM.create(URL, String, Properties) sets the provided properties as System properties. This is inconsistent with the other creation methods in EmbeddedXVM, and pollutes the environment in which the XVM is being launched. The correct way for setting XVM specific configuration is to set such configuration in the source DDL as properties under <env> section which are applied by the XVM when it is started.
Compatibility Notes:

Applications that use this method should ensure that they do not rely on the passed in DDL substitution properties being set as System Properties. In such cases, the system property names passed in may be converted to start with "x.env." such that they are applied to the environment for the XVM (accessible through XRuntime), or alternatively modify code to set them as System properties manually.