This release provides the ability to specify XVM specific <env> properties in config DDL. For example:

Would result in the XRruntime for server-1 ending up with:

• property1=value1
• property2=value2a (from xvm specific env)
• property3=value3a (from xvm specific env)

documentation is still in progress for the feature

This release introduces the ability to validate and enforce the value of a solace queue's max bind count when starting a solace message bus binding by setting

See Enforcing Max Queue Bind Count in the Talon Manual for more details

This release provides the ability for DDL config to define template apps, buses and xvms that can provide base configuration shared by multiple applications.

For example in the following DDL snippet tracing configuration is defined in the "app-template" which is referenced by the ems1 app which inherits that configuration.

See DDL Config Reference for more details

documentation is still in progress for the feature

This release introduce DDL profiles as a new configuration feature. DDL profiles allow defining overlay configuration directly inside a the <profiles> section of a DDL. DDL profiles can be activated explicitly or via the profile's <activation> element which support the ability to automatically activate a profile based on environment variables.

In the above code snippet if DDL is parsed with -Dnv.ddl.profiles=troubleshooting, the configuration defined in the troubleshooting profile will be overlaid on top of the main configuration.

See DDL Config Reference for more details.

documentation is still in progress for the feature

This release enhances the Transaction Log Tool's compact command to allow specifying the initial length of the new file into which to compact by using the '-i initialLogSizeBytes' option flag.

This release allows registration of custom message bus providers in DDL which allows custom message bus binding implementation to be used with out having to register the messaging provider programatically.

See: Message Bus Provider Configuration

This release implements the ability to pass properties to an ADM codegen listener via the maven plugins.

Below is example of passing properties

Properties can then be accessed by the listener via the event passed to it:

This release provides the ability to specify provisioning information in DDL Config. For example:

This allows provisioning tools such as Robin or Lumino to leverage configuration directly from DDL rather than relying on additional files such as <xvmname>.jvmparams or <xvmname>.env

For more information see DDL Config Refefence

documentation is still in progress for the feature

This release provides a tibco ems message bus binding provider that supports Guaranteed Qos. The ems provider can be enabled by replacing the jms://... with tibems://.

This release changes the JMS to allow it to make connection retry attempts when the initial connection attempt to the broker fails. Prior to this release, only a single connection attempt would be made which may not be enough in the event that the message broker has not detected the connection drop of a primary application instance when a backup takes over. Two new binding properties were introduced to support this functionality:

• connection_open_retry_count the number of connection retries to make after a failed attempt to open the JMS Connection. Defaults to 10

• connection_open_retry_interval the interval at which connection retry attempts are made in seconds. Defaults to "1s"
  Compatibility Notes:

   

  This change will increase the amount of time it will take for an application to detect that another instance is already connected to the message bus. Setting connection_open_retry_count=0 for the bus will revert to the previous behavior.

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

This feature allows user to configure the preferred cluster primary when starting a cluster by configuring an election priority for the store as follows.

When 2 members connect and either instance is equally eligible to assume the primary role this knob gives priority to the member with the lowest configured priority

This release provides a new AepEngine method, getEngineTimeMicros(), which returns the wall time in microseconds since the epoch in an HA consistent fashion. This method is akin to the existing getEngineTime() method.

See AepEngine.getEngineTimeMicros()

This release updates the Talon archetypes to leverage the new DDL config features for templating and profiles.

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 adds statistics for the per transaction stats logger to heartbeats which include the file size and disruptor usage for the logger.

This release add binary heartbeat logger statistics to heartbeats to make it possible to monitor how large the heartbeat log is growing when binary heartbeat logging is enabled for an XVM.

The release increases the default value for an XVM's trace history from 256 to 512 and makes maxTraceHistory configurable via DDL. The reason for this change is that 256 lines of trace is often too low for applications that are launched with configuration trace on, since admin clients typically would not connect in time to catch the initial XVM trace.

Example DDL Configuation:

Note that this change will only take effect on reconfiguration of an XVM for XVMs that utilize a persistent configuration repository.

This release improves the transaction log reader to return all valid entries up to the first corrupted entry in the log.

Prior to this release, there was no API or mechanism to copy the serialized form of an ADM generated message/entity field. This release implements the

method that performs this function

Prior to this release, there was no mechanism to perform the following

• Initialize an ADM generated message/entity with a pre-serialized set of fields
• Set some more fields on the message/entity using the field setters
• Serialize the message/entity with an expected output of the serialized form comprised of the personalized fields followed by the serialized form of the set fields

This release generates a new method named

on generated messages and entities that performs the above

This method is only generated for messages/entities generated using the Xbuf encoding type

This release improves memory footprint of State Replication applications using Xbuf encoding for state objects by reducing the number of packet subheaders initialized in the generated object's backing packet.

Prior to this release when DDL is specified in properties format (for users using an external configuration mechanism) unrecognized properties were ignored. With this release VMConfigurer now throws an error if any x.* property is specified that is not defined in the DDL xml schema.

Note that this validation does not apply to generic properties such as bus properties or env properties (that correspond to hierarchical properties in the DDL xml). Additionally this validation does not cover any properties that are outside of x.* configuration.
Compatibility Notes:

This release adds additional validation of DDL configuration supplied via properties rather than xml. Applications using properties based DDL configuration that pass in unknown x.* properties may fail to start. To revert to the old behavior of ignoring unknown properties, applications may set the property nv.ddl.propertynamevalidation=false in the ddl property set passed to VMConfigurer or as a system property.

This release introduces the setting inactiveMessageTypeStatsInclusionFrequency to XVM heartbeat configuration. This setting can be used to control how frequently message type stats are reported for message types without any activity. By default this value is set to 1 meaning that inactive types are included in every heatbeat, but it can be set to 0 to exclude inactive types in heartbeats, or set to a value N, greater than 1 so that every Nth heartbeat inactive message type stats are included.

This improvement changes when the affinity dump trace is printed (when nv.aep.config trace is enabled) to be printed after messaging is started or when an engine enters the cluster backup role rather than earlier in the engine startup so that bus related threads are created and affinitized when the trace is emitted.

As a consequence an application that comes up as a Backup then transitions to primary will have affinity trace dump at both points in its lifecycle

This release published javadoc jars for nvx-adm, nvx-hummingbird and nvx-talon to the Neeve nexus repository. Prior to this release, only bundled javadoc for nvx-talon-all and nvx-core-all were published.

This release improves the JMS binding such that it now propagates messages' origin and pre-wire timestamps in the JMS message properties. This allows downstream application to compute wire time and end to transit time for message flows when both the sender and receiver applications are configured to capture message latency stats.

This release updates talon maven archetypes to use the nvx-platform-bom for dependency management which allows generated projects to switch platform versions with greater ease.

This release updates the talon archetypes to include the nvx-native runtime for linux by default.

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 provides DDL support for specifing <xvms> and <xvm> rather than <servers> and <servers>. The <servers> and <server> elements are deprecated, but remain usable for backwards compatibility ... with the caveat that only one or the other nomenclature can be used.
Compatibility Notes:

It is recommended that user's update their configuration DDL to switch from <servers> to <xvms> and from <server> to <xvm> as support the former variants will be dropped in a future release.

This release adds the ability to change the ddl configuration prefix used to specify platform related properties in the DDL property set itself by setting the property nv.ddl.prefix. Prior to this release a user could only specify the prefix by setting this property in the environment or set of override properties passed in to VMConfigurer.

This release changes the ADM generated lendXXX(XString val) method to allow it to accept a null value without throwing a NullPointerException.
Compatibility Notes:

To take advantage of this change ADM models need to be regenerated. The ADM compatibility version was incremented from 3.8.0 to 3.8.1 as a result of this change.

This release changes the behavior of the JMS binding to set a JMS ClientID of 'X-SMA-<busname>-<bususername>' on JMS message bus binding connections, where <bususername> is the name of the application if the bus is used in a Talon Application.

Setting a JMS Client is a useful safeguard against a primary and backup instance both assuming a primary role when the application is configured with a messagingStartFailPolicy of FailIfOneBindingFails.

The following new binding descriptor properties were introduced to control setting the client id for jms connections:

• set_client_id: Controls whether the binding will set the JMS ClientID for JMS connections. (default: true)
• use_legacy_client_id: causes the client id to be set to <bususername><busname> rather than X-SMA<busname>-<bususername> (prior to this release the activemq binding used this client_id implicitly. (default: false)

• client_id: can be set an explicit client id. (default: not set)
  Compatibility Notes:

   

  If the JMS connection is created from a JNDI connection factory that provides a pre configured JMS ClientID it may cause the JMS provider to throw an exception when the client id is set. Consequently, it is important that this functionality be disabled if the connection factory already specified a client id by setting set_client_id=false

This release removes the experimental ADM annotation processor. It is expected that this processor will be added back in a later release after being revamped.

Prior to this release properties set in the <env> section of DDL config were being set as System properties when an XVM was launched. This behavior is undesirable in unit testing situations since the environment set by one XVM can influence the configuration bootstrapping of subsequent launches (because DDL substitution gives preference to System properties when parsing values specified in the env).
Compatibility Notes:

Applications that may have been relying on fetching values in defined in the DDL <env> section should be updated to fetch such properties via XRuntime.getValue("propName") instead.

Alternatively, to revert to the former behavior of the XVM setting env properties as System properties applications may set nv.xvm.setsystempropsfromenv=true either as a system property prior to launching the XVM or in the DDL <env> section.

This release fixes an issue that can result in the error "Encountered orphan slice element on stability (duplicate ack?)" when performing a mix of solicited and unsolicited sends on the same message type when pooling is enabled.

Encountered orphan slice element on stability (duplicate ack?)
Stack trace:
java.lang.Exception
	at com.neeve.aep.AepBusManager.onEvent(AepBusManager.java:2177)
	at com.neeve.sma.impl.MessageBusBindingBase.onEvent(MessageBusBindingBase.java:566)
	at com.neeve.sma.impl.MessageChannelBase.onEvent(MessageChannelBase.java:972)
	at com.neeve.sma.impl.MessageChannelBase.onEvent(MessageChannelBase.java:983)
	at com.neeve.sma.impl.MessageChannelBase.onMessageStability(MessageChannelBase.java:950)

Not actually a bug embedded config repo is only added to nvx-talon-all.jar

This release fixes an issue in the M2E plugin execution for the nvx-platform-maven-plugin that would cause the robin-xar goal to be executing inside eclipse when it should be skipped.

This release fixes an issue that causes the solace bindings orphan subscription check to fail with 'response too big: use sequence get' when retrieving subscriptions from a queue that has a large number of subscriptions. With this change the call to get subscriptions now attempts to retrieve subscriptions in batches.

Prior to this release, the Talon sender gateway Maven archetype would throw an exception when attempting to generate an app. This release fixes that issue.

This release resolves a bug in the direct binding implementation which can cause it to lose messages during a connection failure when sending protobuf encoded messages with pooling enabled.

This release fixes an issue in the ADM code generator in which an entity could not be inlined into another type that type already contains the same field as one in the entity being inlined. For example, prior to this fix the following would have have failed:

This release resolves an bug in which an exception thrown during message key resolution did not reset the key builder used for building dynamic topics. Consequently, if the application is operating with an exception handling policy of LogExceptionAndContinue, a subsequent send call would result in the resolved key containing a portion of the previously partially resolved key.

Prior to this release the ADM code generator did not throw an exception if an ADM model attempts to inline a message type into another message which is not supported. This release changes ADM to throw an exception when attempting to inline a message type.

This release fixes a bug that occur if there is an error creating A JMS session in the JMS message bus binding that would result in the JMS connection not being closed. This can be problematic if the connection is using a JMS Client ID and the process remains alive because subsequent connection attempts will fail.

This release resolves a packet corruption issue that can occur during replication for StateReplication applications using a transaction log with cdcEnabled=true. With this fix, the following error should no longer occur

Fixes an issue where profile, xvm and xvm template env variables in DDL were not being overridden by corresponding values specified as DDL overrides or already present in the environment fed to VMConfigurer which should take precedence.

This release fixes a bug in the configuration repository that would cause configuration seeded by robin to erroneously localize ${} channel key variables when configuring message channels. This would only affect channel keys with variables having default values that are seeded by robin.

This change fixes a compiler warning in XBuf generated code relating the deprecated PktBuffer.create method.
Compatibility Notes:

This change bumps the ADM compatibility version to 3.8.2 (a non breaking change).

This release fixes a bug in the Talon Maven archetypes in which bus descriptor properties were not being properly updated when a non default application name is used.

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.

The prior release had a bug in which it could experience a deadlock if an admin client (such as a Robin controller or Lumino agent) stops a trace watch while the XVM is sending trace to the client. This release fixes this issue.

This release fixes an issue in which the -all flag for StatsDumpTool is not being applied. Prior to this fix the StatsDumpTool would display stats for administrative applications regardless of whether or not this flag was specified.

This release changes heartbeats not to include system cpu load and process cpu load on heartbeats when they are not available. Prior to this release they would be set to -1 (when running in JDK 6 where these stats are not available)

Prior to this release the threaded parameter of PooledStringType.newFactory(name, length, pooled, preallocateCount, threaded, isNative) is ignored and instead the Factory is always treated as thread. This release fixes this issue.

This issue did not affect pooled string factories created via PooledStringType.newFactory(final String name, final Map<String, Object> props).
Compatibility Notes:

For applications that create pooled string factories using the method described above and passed a value of false for threaded, the underlying pool will no longer be threadsafe. This could affect applications that were using the pool (acquire/dispose) from multiple threads.