Author Archive

Axon 3.0.5 Released

We have released Axon 3.0.5. It contains a few fixes and improvements

One of the improvements is for users that have migrated from Axon 2.4, allowing data stored in that version to still be used (as-is) in 3.0. Support for this is available in the ‘axon-legacy’ module.

The Event Store was unable to cope with timestamps that were stored in another timezone than UTC. The parser has been changed, so that times with explicit timezones are properly converted to an Instant.

The GenericJpaRepository was unable to work with aggregate identifiers other than String. In this release, a converter can be specified that converts the String value used in the Repository API to the value to use in the EntityManager API.

The GenericJpaRepository now loads entities using a write lock from the database. This ensures that an aggregate is only active on a single node at a time and prevents deadlocks when multiple threads attempts to upgrade the read lock to a write lock.

For a detailed overview of changes, check the release notes.

Posted in: News, Release notes

Leave a Comment (0) →

Axon 3.0.4 Released

Axon 3.0.4 has been released. It is a quick follow up on the 3.0.3 release and fixes some issues related to the distributed command bus in combination with Spring.

Due a timing issue in the configuration of several components, it was possible that certain Command Handlers were registered with the wrong Command Bus instance (the local segment instead of the distributed command bus). 3.0.4 addresses those issues.

Furthermore, 3.0.4 provides methods on the Configuration interface that provide access to the different submodules and Event Processors.

For full details of this release, check the release notes.

Posted in: News, Release notes

Leave a Comment (0) →

Axon 3.0.3 Released

Axon 3.0.3 has been released! This release contains quite a few fixes and improvements to earlier versions.

We have solved some issues related to the Spring Cloud components for the Distributed Command Bus. Nodes not accepting any commands themselves caused Class Cast exceptions on the other side, preventing them from participating at all. We have also included Spring Boot Auto Configuration for the Spring Cloud components.

The Tracking processor is now more resilient to failure and exposes its current state. It can now also be paused/resumed at Runtime.

The issue that prevents Axon to work nicely with Spring Boot Devtools has also been identified and fixed. That means it’s now possible to use the Axon starter modules in combination with Spring Boot Devtools.

For more details about this release, check the release notes.

Posted in: News, Release notes

Leave a Comment (0) →

Axon 3.0.2 released

Today, we have released Axon 3.0.2! This release contains a few fixes to issues found in earlier versions.

The generic types in the Given-When-Then test fixtures have been fixed, so that the expectEventMatching() methods now accept the Matchers provided by Axon. Certain matchers could not be used due to incorrect Generic type expectations.

We have also resolved an issue that could cause certain events to be published out-of-order when command handlers would send out new commands as well as events.

In 3.0.1, the TrackingToken would be updated in the JpaTokenStore, even if the data itself didn’t change. In certain databases (e.g. Postgres), this would cause large numbers of LOB Pointers to be ‘consumed’, for no obvious reason. This has been improved in 3.0.2.

We have also implemented a minor improvement: Components registered using the Configuration API are now injectable as parameters of annotated handler methods (e.g. @CommandHandler, @EventHandler).

For more details about this release, check the release notes.

Posted in: News, Release notes

Leave a Comment (0) →

Axon 3.0.1 released

Today, we have released Axon 3.0.1. This release contains fixes for a few bugs and usability issues that were found since the release of 3.0.

A notable new feature is the possibility to use Spring’s @Autowired for resources in the SagaTestFixture.

We have also simplified the configuration of MessageHandlerInterceptors on Processors using the Configuration API. It is no longer necessary to configure a complete custom Processor Builder function. You can now simply register the interceptors that need to be assigned to the Processors as they’re created.

For a list of fixes, check the GitHub issue tracker.

Posted in: News, Release notes

Leave a Comment (0) →
Page 1 of 9 12345...»