Bug Fixes

Any patch release made for an Axon project is tailored towards resolving bugs. This page aims to provide a dedicated overview of patch releases per project.

Axon Framework

Release 4.3.5

• The TrackingEventProcessor#mergeSegment(int) method was invoked with the high segment number of the pair to merge, an error would occur in the process as it expected to receive the lower number on all scenarios. This was resolved in pull request #1450.

• A small connectivity adjustment which was performed in the AxonServerConnectionManager for bug release 4.3.4 has been reverted. Although it worked successfully for some scenarios, it did not correctly cover all possibilities. The commit can be found here for reference. The full scenario will be covered through the adjusted connector which is underway for beta release in 4.4.

For a complete list of all resolved bugs we refer to the issue tracker.

Release 4.3.4

• Whilst adjusting the JdbcEventStorageEngine in #1187 to allow more flexibility to configure the used statements, we accidentally dropped support for adjusting how the store wrote timestamps. This issue was rectified by user ovstetun in pull request #1454.

• Snapshots were incorrectly created in the same phase as the publication of events. This has been moved to the after commit phase of the UnitOfWork in issue #1457.

• When using the SequenceEventStorageEngine to merge an active and historic event stream there was a discrepancy when the active stream didn't contain any events and the historic stream did. This has been resolved in pull request #1459.

For a complete list of all resolved bugs we refer to the issue tracker.

Release 4.3.3

This bug release contained a single fix, under pull request #1425. A situation was reported where a Tracking Event Processor did not catch up with the last event, until a new event was available after that event. Effectively causing it to read up to N-1. This only accounted for usages of the MultiStreamableMessageSource, thus when two (or more) event streams were combined into a single source for a TrackingEventProcessor.

To remain complete, here is the issue tracker page contained the closed issues for release 4.3.3.

Release 4.3.2

• When using the QueryGateway, it was not possible to provide a QueryMessage as the query field since the queryName would be derived from the class name of the provided query. Hence, QueryMessage would be the queryName, instead of the actual queryName. This issue has been resolved in #1410.

• There was a window of opportunity where the Snapshotter would publish the last event in its stream twice. This could cause faulty snapshots in some scenarios. This issue was marked under #1408 and resolved in pull request #1416.

• The bi-directional stream created by the Axon Server Connector wasn't always closed correctly; specifically in error cases. This problem has been resolved in pull request 1397.

For a complete list of all resolved bugs we refer to the issue tracker.

Release 4.3.1

• Through the new Create-or-Update feature a bug was introduced which didn't allow non-String aggregate identifiers. This problem was quickly resolved in #1363, allowing the usage of "complex" aggregate identifiers once more.

• The graceful shutdown process introduced in 4.3 had a couple of minor problems. One of which was the shutdown order within the AxonServerCommandBus and AxonServerQueryBus, which basically made it so that the approach prior to 4.3 was maintained. We also noticed that the AxonServerConnectionManager never shutdown nicely. All of these, plus some other minor fixes, have been performed in #1372.

• The AggregateCreationPolicy#ALWAYS did not behave as expected, resulting in faulty behaviour when used. Pull request #1371 saw an end to this problem, ensuring the desired usage of all newly introduced creation policies.

For a complete list of all resolved bugs we refer to the issue tracker.

Release 4.3

• A ConcurrencyException was thrown when an aggregate was created at two distinct JVM's at the same time. As ConcurrencyExceptions are typically retryable, the creation command would be issued again if a RetryScheduler was in place. Retrying this operation is however useless and hence has been replaced for an AggregateStreamCreationException in pull request #1333.

• The test fixtures for state-stored aggregates did unintentionally not allow resource injection. This problem has been resolved in pull request #1315.

• The MultiStreamableMessageSource did not deal well with one or several exceptional streams. Hence exception handling has been improved on this matter in #1325.

For a complete list of all resolved bugs we refer to the issue tracker.

Release 4.2.2

• In a distributed setup, the DisruptorCommandBus was not always correctly identified as being the local segment. Due to this, aggregate repositories weren't created by the DisruptorCommandBus as is required in such a configuration. This was marked in #874 and resolved through #1287.

• As described in #1274, a query handler with return type Future was not being returned at all but threw an exception. Pull request #1323 solved that in 4.2.2.

• An issue was solved where the JdbcAutoConfiguration unintentionally depended on a JPA specific class.

For a complete list of all resolved bugs we refer to the issue tracker.

Release 4.2.1

• A one-to-many Upcaster instance tied to Axon Server would only use the first event result and ignore the rest. This issue has been resolved in pull request #1264.

• The axon-legacy module's GapAwareTrackingToken did not implement the TrackingToken interface. This was marked in issue #1230 and resolved in #1231.

• The builders of the ExponentialBackOffIntervalRetryScheduler and IntervalRetryScheduler previously did not implement the validate() method correctly. Through this a NullPointerException could occur on start-up, as marked in #1293.

For a complete list of all resolved bugs we refer to the issue tracker.

Release 4.2

• An Aggregate's Snapshotter was not auto configured when Spring Boot is being used, as was filed under #932.

• The CommandResultMessage was returned as null when using the DisruptorCommandBus. This was solved in pull request #1169.

• The ScopeDescriptor used by the DeadlineManager had serialization issue when a user would migrate from an Axon 3.x application to Axon 4.x. The axon-legacy package has been expanded to contain legacy ScopeDescriptors to resolve this problem.

For a complete list of all resolved bugs we refer to the issue tracker.

Release 4.1.2

• A dependency on XStream was enforced undesirably through the Builder pattern introduced in 4.0. This has been resolved by using a Supplier of a Serializer in the Builders instead, as described under this issue.

• Due to a hierarchy issue in the Spring Boot auto configuration, the JdbcTokenStore was not always used as expected. The ordering has been fixed under issue #1077.

• The ordering of message handling functions was incorrect according to the documentation. Classes take precedence over interface, and the depth of interface hierarchy is calculated based on the inheritance level (as described here).

For a complete list of all resolved bugs we refer to the issue tracker.

Release 4.1.1

• Query Dispatch Interceptors were no called correctly when a subscription query was performed when Axon Server was used as the QueryBus. This issue was marked here and resolved in pull request #1042.

• When Axon Server was (auto) configured without being able to connect to an actual instance, processing instructions were incorrectly dispatched regardless. Pull request #1040 resolves this by making sure an active connection is present.

• The Spring Boot auto configuration did not allow the exclusion of the axon-server-connector dependency due to a direct dependency on classes. This has been resolved by expecting fully qualified class names as Strings instead (resolved under this pull request).

• The JpaEventStorageEngine was not wrapping the appendEvents operation in a transaction. Problem has been resolved under issue #1035.

For a complete list of all resolved bugs we refer to the issue tracker.

Release 4.1

• Command an Query message priority was not set correctly for the Axon Server Connector. This issue has been addressed under bug #1004.

• The CapacityMonitor was not registered correctly for Event Processor, which user "Sabartius" resolved under issue #961.

• Some exception were not reported correctly and/or clearly when utilizing the Axon Server Connector (issue marked under number #945).

For a complete list of all resolved bugs we refer to the issue tracker.

Release 4.0.4

• Deserialization failures were accidentally swallowed by the command and query gateway (marked under #967).

• Resolved an issue where custom exception in a Command Handling constructor caused NullPointerExceptions.

For a complete list of all resolved bugs we refer to the issue tracker.

Release 4.0.3

• The SimpleQueryBus reported exceptions on the initial result incorrectly upon performing a subscription query. Issue has been described and resolved under #913.

• Resolved issue where the the "download Axon Server" message was shown upon a reconnect of an application to a Axon Server node.

• Large global index gaps between events caused issues when querying the event stream (described here).

• Fixed inconsistency in the GlobalSequenceTrackingToken#covers(TrackingToken) method.

For a complete list of all resolved bugs we refer to the issue tracker.

Release 4.0.2

• A timeout was thrown instead of a exception by Axon Server when a duplicate aggregate id was created, which is resolved in #903.

• Command or Query handling exception were no properly serialized through Axon Server (resolved in #904).

For a complete list of all resolved bugs we refer to the issue tracker.

Release 4.0.1

• Resolved QueryUpdateEmitter configuration for the Axon Server connector set up (see issue here).

• For migration purposes legacy TrackingTokens should have been added, which is resolved here.

• Event Processing was stopped after a reconnection with Axon Server. Resolve the problem in issue #883.

For a complete list of all resolved bugs we refer to the issue tracker.

Release 4.0

The bugs marked for release 4.0 were issues introduced to new features or enhancements. As such they should not have impacted users in any way. Regardless, the full list can be found here.