Only this pageAll pages
Powered by GitBook
1 of 22

X Release Notes

Loading...

X Platform 3.16

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

X Platform Release Notes

X Platform 3.16.26

Release Date: Saturday, November 04, 2023

Release Notes

  • Talon 3.16.42 [Release Notes]

  • Native 3.16.29 []

  • Messaging Bindings

    • Solace 3.16.25 [No changes in this release]

    • Kafka 1.8.24 [No changes in this release]

    • JMS 3.16.25 [

  • Layered Frameworks

    • Hornet 1.16.24 []

    • Eagle 2.9.25 [No changes in this release]

  • DevOps

    • Robin 2.12.24 [No changes in this release]

  • Samples 3.16.26 []

  • Apps 3.16.26 []

X Platform 3.16.27

Release Date: Wednesday, March 06, 2024

Release Notes

  • Talon 3.16.43 [Release Notes]

  • Native 3.16.30 [No changes in this release]

  • Messaging Bindings

    • Solace 3.16.26 [No changes in this release]

    • Kafka 1.8.25 [No changes in this release]

    • JMS 3.16.26 [

  • Layered Frameworks

    • Hornet 1.16.25 [No changes in this release]

    • Eagle 2.9.26 [No changes in this release]

  • DevOps

    • Robin 2.12.25 [No changes in this release]

  • Samples 3.16.27 []

  • Apps 3.16.27 []

Robin 2.12.28

Release Date: Thursday, May 02, 2024

Compatibility Notes

No issues have compatibility implications

Change Summary

Improvements

ROBIN-157

Enable environment variable substitution for config in robin.conf

This release enhances robin to perform environment substitution on config properties in robin.conf

Hornet 1.16.26

Release Date: Thursday, May 02, 2024

Compatibility Notes

No issues have compatibility implications

Change Summary

Improvements

TOA-124

Unknown Talon version info output by Hornet if shaded in uber jar

Hornet pulls dependent Talon version from the Talon jar's manifest info. This causes the Talon version to be unknown if it is shaded in an uber jar. This release fixes this issue

TOA-125

Too much trace in Hornet applications that have a large number of services, messages or channels

Since the change to make the default trace level Config, Hornet applications that have a large number of services, messages and/or channels output a lot of trace logging on startup. This release reduces that trace info

Robin 2.12.30

Release Date: Wednesday, July 24, 2024

Compatibility Notes

No issues have compatibility implications

Change Summary

Improvements

ROBIN-158

Include native libs in Robin linux distribution

This release added nvx-native libs for linux-x86-64 to robin linux distributions

X Platform 3.16.34

Release Date: Wednesday, December 18, 2024

Release Notes

  • Talon 3.16.61 [No changes in this release]

  • Native 3.16.45 [No changes in this release]

  • Messaging Bindings

    • Solace 3.16.30 []

    • Kafka 1.8.28 [No changes in this release]

    • JMS 3.16.29 [No changes in this release

  • Layered Frameworks

    • Hornet 1.16.28 [No changes in this release]

    • Eagle 2.9.29 [No changes in this release]

  • DevOps

    • Robin 2.12.32 [No changes in this release]

  • Samples 3.16.34 []

  • Apps 3.16.34 []

X Platform 3.16.30

Release Date: Thursday, May 02, 2024

Release Notes

  • Talon 3.16.47 []

Hornet 1.16.27

Release Date: Wednesday, July 24, 2024

Compatibility Notes

No issues have compatibility implications

Change Summary

X Platform 3.16.33

Release Date: Tuesday, December 03, 2024

Release Notes

  • Talon 3.16.61 []

Solace 3.16.29

Release Date: Tuesday, December 03, 2024

Compatibility Notes

No issues have compatibility implications

Change Summary

  • Improvement

    • TOA-126 - nv.trace.useslf4j ignored by Hornet service tracer (nv.toa)

    • TOA-127 - Excessive trace by nv.toa tracer

Improvements

TOA-126

nv.trace.useslf4j ignored by Hornet service tracer (nv.toa)

This release fixes an issue in which the nv.trace.useslf4j configuration setting is ignored by Hornet service tracer (nv.toa). This causes the trace output by this tracer to use X trace format and output to stdout instead as configured by the appropriate SLF4J config

TOA-127

Excessive trace by nv.toa tracer

Prior to this release, the Hornet tracer, i.e, the nv.toa logger, outputs the AEP engine configuration if the trace level if at or higher than CONFIG. The AEP engine itself also outputs its configuration when its trace level is set at or above CONFIG. Since the change to make CONFIG the default trace level, both the nv.toa and nv.aep loggers output the engine configuration. This can result in a significant amount of trace when a very large number of message types are employed by an application. To reduce this, this ticket changes the nv.toa logger to output the engine configuration if the trace level if set to VERBOSE or higher.

No changes in this release
]
Release Notes
Release Notes
source
source
No changes in this release
]
source
source
Improvement
ROBIN-157 - Enable environment variable substitution for config in robin.conf
Improvement
TOA-124 - Unknown Talon version info output by Hornet if shaded in uber jar
TOA-125 - Too much trace in Hornet applications that have a large number of services, messages or channels
Improvement
ROBIN-158 - Include native libs in Robin linux distribution
]
Release Notes
source
source
Native 3.16.31 [No changes in this release]
  • Messaging Bindings

    • Solace 3.16.27 [No changes in this release]

    • Kafka 1.8.26 [No changes in this release]

    • JMS 3.16.27 [No changes in this release]

  • Layered Frameworks

    • Hornet 1.16.26 [Release Notes]

    • Eagle 2.9.27 [No changes in this release]

  • DevOps

    • Robin 2.12.28 [Release Notes]

  • Samples 3.16.30 [source]

  • Apps 3.16.30 [source]

  • Release Notes
    Native 3.16.44 [No changes in this release]
  • Messaging Bindings

    • Solace 3.16.29 [Release Notes]

    • Kafka 1.8.28 [No changes in this release]

    • JMS 3.16.29 [No changes in this release]

  • Layered Frameworks

    • Hornet 1.16.28 [No changes in this release]

    • Eagle 2.9.29 [No changes in this release]

  • DevOps

    • Robin 2.12.31 [No changes in this release]

  • Samples 3.16.33 [source]

  • Apps 3.16.33 [source]

  • Release Notes
    • New Feature

      • SOLACE-13 - Added ability to remove orphan subscriptions on startup

    • Improvement

      • SOLACE-38 - Mask Solace connection passwords in logs

    New Features

    SOLACE-13

    Added ability to remove orphan subscriptions on startup

    This release adds a new orphan subscription check policy -Unsubscribe - that, if set, will cause the Solace binding to unsubscribe to all orphan subscriptions, if present, in the Solace broker/appliance.

    Improvements

    SOLACE-38

    Mask Solace connection passwords in logs

    This release masks Solace connection passwords in logs

    SOLACE-40

    Remove need for semp_vpn_index to be configured in Solace binding for orphan subscription checks

    Prior to this release, the Solace binding requires the SEMP VPN Index to be configured on a binding, in addition to the VPN name, to perform orphan subscription checks (for number of subscriptions on the queue that exceed 500). This release enhances the orphan check implementation to pull this index from the SEMP messages and not need it to be configured on the binding

    Solace 3.16.28

    Release Date: Wednesday, July 24, 2024

    Compatibility Notes

    No issues have compatibility implications

    Change Summary

    Changes

    SOLACE-37

    Upgrade to JCSMP 10.21.0

    This release upgrades the solace JCSMP binding to JCSMP v10.21.0

    SOLACE-39

    Upgrade to CCSMP 7.30.0.2

    This release upgrades the solace CCSMP binding to CCSMP v7.30.0.2

    SOLACE-40 - Remove need for semp_vpn_index to be configured in Solace binding for orphan subscription checks
    Change
    SOLACE-37 - Upgrade to JCSMP 10.21.0
    SOLACE-39 - Upgrade to CCSMP 7.30.0.2

    Talon 3.16.47

    Release Date: Thursday, May 02, 2024

    Compatibility Notes

    No issues have compatibility implications

    Change Summary

    New Features

    TALON-120

    Ability to change default trace level

    Prior to this release, CONFIG was the default level for X tracers. This release implements the ability to change the default trace level via the following config property

    nv.trace.defaultLevel

    This property needs to be specified as a JVM system property

    Improvements

    TALON-122

    Change trace level of "Received an unknown event 'MessageBusBindingReconnectingEvent'." log message to verbose

    The following line is output by the SMA discovery cache implementation when the underlying SMA binding is going through an automatic reconnection.

    This release changes the log level this trace from WARNING to VERBOSE (to reduce unnecessary logging)

    Changes

    TALON-119

    Record enqueueTs in message regardless of whether nv.msg.latency.stats is set

    Prior to this release, the AEP engine recorded the enqueueTs is a message only if nv.msg.latency.stats is set to true. This release removes this restriction i.e. enqueueTs is always set in the message

    TALON-125

    Change default pool locking strategy from Lock to Mutex

    This release changes the default pool locking strategy from Lock to Mutex

    Bugs

    TALON-121

    "JVM is Shutting Down" exception thrown when JVM is shut down

    This release fixes the issue in which the following exception is thrown on JVM shut down

    TALON-123

    Field Bitmask not present in serialized json in xbuf2 generated code

    This release fixes an issue in which the field bitmask, necessary to preserve field presence indication when an Xbuf2 generated message/entity is serialized to and then deserialized from json, is absent from the json serialized form of the message/entity

    TALON-124

    java.lang.ArrayIndexOutOfBoundsException: arraycopy: last source index 10241 out of bounds for double[10240]

    This release fixes the following error (that prevents heartbeats from being sent out)

    X Platform 3.16.32

    Release Date: Wednesday, July 24, 2024

    Release Notes

    • Talon 3.16.50 [Release Notes]

    • Native 3.16.40 [No changes in this release]

    • Messaging Bindings

      • Solace 3.16.28 []

      • Kafka 1.8.27 [No changes in this release]

      • JMS 3.16.28 [No changes in this release

    • Layered Frameworks

      • Hornet 1.16.27 []

      • Eagle 2.9.28 [No changes in this release]

    • DevOps

      • Robin 2.12.30 []

    • Samples 3.16.32 []

    • Apps 3.16.32 []

    Talon 3.16.42

    Release Date: Monday, November 06, 2023

    Compatibility Notes

    No issues have compatibility implications

    Change Summary

    Improvements

    TALON-111

    Change "enabled" attribute for detached config element elements in DDL to be optional

    Prior to this release, the 'enabled" attribute in the detached elements in the DDL was required. This meant that it was not possible to rely solely on the optimization setting to switch on detached operation or not. This release makes these "enabled" attributes optional i.e. it is possible to not explictly specify whether detached operation is enabled or not and let the optimization configuration solely determine whether detached operation should be switched on or not.

    TALON-113

    Support for Java 11

    This release adds support for for X applications to be run using Java 11

    TALON-115

    Support for Java 17

    This release adds support for X applications to be run using Java 17

    TALON-116

    Add native memory block and IO Buffer counter stats to XVM heartbeats

    This release adds native memory block and IO Buffer counter stats to XVM heartbeats

    Changes

    TALON-114

    Exclude memory mapped buffer space from off-heap memory stats

    This release modifies memory stats reporting to exclude memory mapped buffer space from off-heap memory stats

    Bugs

    TALON-110

    Deadlock between transaction logging and log compactor threads

    This release fixes an issue in which a deadlock can occur between the transaction logging thread and compactor thread.

    TALON-112

    Off-heap memory live leak in buffer backing xbuf2 generated messages/state

    This release fixes a live-leak issue in messages and state classes generated using the xbuf2 encoding type.

    TALON-117

    Allocation of data backing an Xbuf2 message sometimes not reported in memory stats

    This release fixes an issue in which the allocation of data to back an Xbuf2 generated message would sometimes not get reported to the memory stats manager. This would result in an incorrect memory stat for data used by message/state entities generated using Xbuf2 including sometimes showing the data used as negative

    Hornet 1.16.24

    Release Date: Monday, November 06, 2023

    Compatibility Notes

    No issues have compatibility implications

    Change Summary

    • Change

      • TOA-122 - nv.trace.useslf4j setting does not take effect for trace output by nv.toa logger

    Changes

    TOA-122

    nv.trace.useslf4j setting does not take effect for trace output by nv.toa logger

    A change in the 3.16.20 release introduced an issue due to which the nv.trace.useslf4j setting does not take effect for trace output by nv.toa logger since the X 3.16.20 release. This release fixes this issue

    ]
    Release Notes
    Release Notes
    Release Notes
    source
    source

    TALON-116 - Add native memory block and IO Buffer counter stats to XVM heartbeats

  • Change

    • TALON-114 - Exclude memory mapped buffer space from off-heap memory stats

  • Bug

    • TALON-110 - Deadlock between transaction logging and log compactor threads

    • TALON-112 - Off-heap memory live leak in buffer backing xbuf2 generated messages/state

    • TALON-117 - Allocation of data backing an Xbuf2 message sometimes not reported in memory stats

  • Improvement
    TALON-111 - Change "enabled" attribute for detached config element elements in DDL to be optional
    TALON-113 - Support for Java 11
    TALON-115 - Support for Java 17

    Change

    • TALON-119 - Record enqueueTs in message regardless of whether nv.msg.latency.stats is set

    • TALON-125 - Change default pool locking strategy from Lock to Mutex

  • Bug

    • TALON-121 - "JVM is Shutting Down" exception thrown when JVM is shut down

    • TALON-123 - Field Bitmask not present in serialized json in xbuf2 generated code

    • TALON-124 - java.lang.ArrayIndexOutOfBoundsException: arraycopy: last source index 10241 out of bounds for double[10240]

  • New Feature
    TALON-120 - Ability to change default trace level
    Improvement
    TALON-122 - Change trace level of "Received an unknown event 'MessageBusBindingReconnectingEvent'." log message to verbose
    SmaDiscoveryCache-3c144c69-6757-454e-b0e4-dfddbc88a4f9] Received an unknown event 'MessageBusBindingReconnectingEvent'.
    com.neeve.discovery.EDiscoveryJVMShuttingDownException: JVM is shutting down 
    at com.neeve.discovery.impl.DiscoveryCacheBase.remove(DiscoveryCacheBase.java:1005) 
    at com.neeve.server.controller.SrvController.onAppStateChange(SrvController.java:4338) 
    at com.neeve.server.controller.SrvController$AppWatcher.onAppStopped(SrvController.java:673) 
    at com.neeve.server.app.SrvAppLoader$AepEngineWatcher.onEngineStopped(SrvAppLoader.java:1777) 
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) 
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) 
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) 
    at java.lang.reflect.Method.invoke(Method.java:498) 
    at com.neeve.aep.AepEventDispatcher$Handler.dispatch(AepEventDispatcher.java:151)
    ...
    java.lang.ArrayIndexOutOfBoundsException: arraycopy: last source index 10241 out of bounds for double[10240] 
    at com.neeve.stats.Stats$LatencyManager.get(Stats.java:1028) 
    at com.neeve.server.controller.SrvController$IntSeriesCollector.collect(SrvController.java:148) 
    at com.neeve.server.controller.SrvController$StatsRunner.collectIntSeriesStats(SrvController.java:2695) 
    at com.neeve.server.controller.SrvController$StatsRunner.access$900(SrvController.java:682) 
    at com.neeve.server.controller.SrvController$StatsRunner$Apps.populateEngineStats(SrvController.java:2274) 
    at com.neeve.server.controller.SrvController$StatsRunner$Apps.createForHeartbeat(SrvController.java:2592) 
    at com.neeve.server.controller.SrvController$StatsRunner.run(SrvController.java:2861){code} 
    ...

    Native 3.16.29

    Release Date: Monday, November 06, 2023

    Compatibility Notes

    No issues have compatibility implications

    Change Summary

    Bugs

    NATIVE-1

    Memory leak in cluster replication using native IO

    This release fixes a native memory leak when using native IO for cluster replication

    NATIVE-2

    Memory leak in persistence using native file IO

    This release fixes a native memory leak when using native file IO for persistence

    Talon 3.16.50

    Release Date: Wednesday, July 24, 2024

    Compatibility Notes

    No issues have compatibility implications

    Change Summary

    Solace 3.16.30

    Release Date: Wednesday, December 18, 2024

    Compatibility Notes

    No issues have compatibility implications

    Change Summary

    • Improvement

      • TALON-127 - Enhance serializeToJson() to not serialize absent primitive fields

    • Bug

      • TALON-126 - Minor garbage generation in discovery

    Improvements

    TALON-127

    Enhance serializeToJson() to not serialize absent primitive fields

    Prior to this release, the generated serializeToJson() method would serialize primitive fields regardless of whether the field was present or not. To ensure that the field presence status of primitive fields is preserved across serializeToJson() and deserializeFromJson(), the code generated in prior releases would serialize field presence in a special bitmask field. This release removes the json bitmask field and enhances serializeToJson() to not serialize primitive fields if the field is absent in the source message

    Bugs

    TALON-126

    Minor garbage generation in discovery

    This release fixes a minor garbage generation in the X discovery implementation

    • New Feature

      • SOLACE-42 - Ability to configure the subscription fetch batch size for orphan subscription check

    • Improvement

      • SOLACE-41 - Intermittent performance issue with orphan subscription check

    New Features

    SOLACE-42

    Ability to configure the subscription fetch batch size for orphan subscription check

    This ticket implements the ability to be able to configure the batch size when using sequenced gets to fetch subscriptions for the orphan subscription check. Sequenced gets are used when the number of subscriptions being fetched exceed the max number of subscriptions that can be fetched in a single SEMP call.

    The batch size is configured via the orphan_subscription_check_batch_size connection descriptor parameter. Default value of this parameter is 200.

    Improvements

    SOLACE-41

    Intermittent performance issue with orphan subscription check

    This release fixes the intermittent performance issue with orphan subscription checks in which the time it takes to fetch the subscriptions from the Solace broker/appliance can sometimes be very long

    Bug
    NATIVE-1 - Memory leak in cluster replication using native IO
    NATIVE-2 - Memory leak in persistence using native file IO

    Talon 3.16.61

    Release Date: Tuesday, December 03, 2024

    Compatibility Notes

    No issues have compatibility implications

    Change Summary

    • New Feature

      • TALON-135 - Notify completion of transaction containing injected message

    • Improvement

      • TALON-128 - Suspend aging discovery protocol while discovery connection is down

    New Features

    TALON-135

    Notify completion of transaction containing injected message

    Prior to this release, there was no way for an injector - the caller of the AepEngine#injectMessage method - of a message to get notified as to when the transaction that contains the injected message is complete i.e. when the injected message is stable. This release adds the ability to attach an acknowledger to an injected message that is invoked by the AEP engine when the transaction containing the injected message is complete

    Improvements

    TALON-128

    Suspend aging discovery protocol while discovery connection is down

    This release enhances the SMA discovery implementation to suspend aging while connection to the discovery broker/network is down and reconnecting. The SMA discovery implementation is a discovery implementation to use an SMA bus connection and is used for discovery over the X supported messaging providers such as Solace, JMS and Kafka

    TALON-129

    SMA discovery implementation should attempt to reconnect to the messaging bus if the connection fails

    Prior to this release, the SMA discovery implementation does not attempt to reconnect to the underlying messaging bus when connection to the bus is lost. This release enhances the implementation to attempt and continue to attempt to reconnect to the bus after it loses its connection to the bus

    TALON-131

    Generate getXXXAsTimestampObject() for Date fields

    This release enhances the ADM code generators to generate the getXXXAsTimestampObject() method for Date fields in ADM messages and entities. The method returns a Long object

    TALON-132

    Generate get/setXXXAsInstant() for Date fields

    This release enhances the ADM code generators to generate the setXXXAsInstant() and getXXXAsInstant() methods for Date fields in ADM messages and entities. The method respectively accept and return a java.time.Instant object

    TALON-134

    Duplicate AEP shutdown message over ICR channel

    In a situation in which the processing of the message that invokes the AEP engine's setAsLastTransaction() method with cluster shutdown enabled, it is possible a duplicate shutdown control message is transmitted over the ICR channel. This can result in the first of the duplicate shutdown messages to shut down the ICR received and the second remain in the ICR receiver queue. This results in the ICR receiver either reporting an error or shutting down on restart depending on how the receiver is restarted. This release fixes this issue.

    Bugs

    TALON-133

    Deadlock in SMA discovery binding during close

    This release fixes a deadlock in the SMA discovery binding that can occur if the binding is closed while active discovery events are being received

    TALON-129 - SMA discovery implementation should attempt to reconnect to the messaging bus if the connection fails
    TALON-131 - Generate getXXXAsTimestampObject() for Date fields
    TALON-132 - Generate get/setXXXAsInstant() for Date fields
    TALON-134 - Duplicate AEP shutdown message over ICR channel
    Bug
    TALON-133 - Deadlock in SMA discovery binding during close

    Talon 3.16.43

    Release Date: Wednesday, March 06, 2024

    Compatibility Notes

    No issues have compatibility implications

    Change Summary

    Bugs

    TALON-118

    ICR Receiver not ack'ing final message

    Prior to this release, it was possible for the last message received by an ICR receiver to not be ack'd on a graceful shutdown. This release fixes this issue.

    Bug
    TALON-118 - ICR Receiver not ack'ing final message