Issues: AxonFramework/AxonFramework
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
OpenTelemetry Issue - Span ended without all scopes!
Status: Information Required
Use to signal this issue is waiting for information to be provided in the issue's description.
Type: Bug
Use to signal issues that describe a bug within the system.
Set High priority. Ideally, these issues are part of the release they’re assigned to.
Status: Resolved
Use to signal that work on this issue is done.
Type: Bug
Use to signal issues that describe a bug within the system.
axoniq/axonserver:latest
as default Axon Server image
Priority 2: Should
First steps towards the layered Highest priority. A release cannot be made if this issue isn’t resolved.
Status: In Progress
Use to signal this issue is actively worked on.
Type: Enhancement
Use to signal an issue enhances an already existing feature of the project.
CommandBus
Priority 1: Must
Avoid excessive CPU consumption on subscription query
Priority 1: Must
Highest priority. A release cannot be made if this issue isn’t resolved.
Status: Resolved
Use to signal that work on this issue is done.
Type: Bug
Use to signal issues that describe a bug within the system.
Resolve issue with eager gap cleanup
Priority 1: Must
Highest priority. A release cannot be made if this issue isn’t resolved.
Status: Resolved
Use to signal that work on this issue is done.
Type: Bug
Use to signal issues that describe a bug within the system.
the EventStorageEngine is not config
Priority 1: Must
Highest priority. A release cannot be made if this issue isn’t resolved.
Status: Duplicate
Use to signal this issue is a duplicate of another. Please refer to the other issue.
Type: Bug
Use to signal issues that describe a bug within the system.
Global Message Handler adjustments
Priority 1: Must
Highest priority. A release cannot be made if this issue isn’t resolved.
Status: Resolved
Use to signal that work on this issue is done.
Type: Enhancement
Use to signal an issue enhances an already existing feature of the project.
Async-Native Command Handling
Priority 1: Must
Highest priority. A release cannot be made if this issue isn’t resolved.
Status: Resolved
Use to signal that work on this issue is done.
Type: Enhancement
Use to signal an issue enhances an already existing feature of the project.
Added explicit AutoConfigureBefore and AutoConfigureAfter in JpaAutoConfiguration
Priority 1: Must
Highest priority. A release cannot be made if this issue isn’t resolved.
Status: Resolved
Use to signal that work on this issue is done.
Type: Bug
Use to signal issues that describe a bug within the system.
Resolved MySQL startup problems in integration tests
Priority 1: Must
Highest priority. A release cannot be made if this issue isn’t resolved.
Status: Resolved
Use to signal that work on this issue is done.
Type: Bug
Use to signal issues that describe a bug within the system.
Type: Dependency Upgrade
Use to signal an issue that adjusts the project’s dependencies. Typically used by dependabot only.
New Unit of Work through Highest priority. A release cannot be made if this issue isn’t resolved.
Status: Resolved
Use to signal that work on this issue is done.
Type: Enhancement
Use to signal an issue enhances an already existing feature of the project.
ProcessingContext
Priority 1: Must
Resolved apparent memory leak in GapAwareTrackingToken
Priority 2: Should
High priority. Ideally, these issues are part of the release they’re assigned to.
Status: Resolved
Use to signal that work on this issue is done.
Type: Bug
Use to signal issues that describe a bug within the system.
Added support for TrackingToken parameter in SagaTestFixture
Priority 3: Could
Low priority. Issues that are nice to have but have a straightforward workaround.
Status: Resolved
Use to signal that work on this issue is done.
Type: Enhancement
Use to signal an issue enhances an already existing feature of the project.
[#2900] Removed requirement for property to disable AxonServer EventStore and enable another one
Priority 2: Should
High priority. Ideally, these issues are part of the release they’re assigned to.
Status: Resolved
Use to signal that work on this issue is done.
Type: Enhancement
Use to signal an issue enhances an already existing feature of the project.
Integration test should use current Axon version
Priority 1: Must
Highest priority. A release cannot be made if this issue isn’t resolved.
Status: Resolved
Use to signal that work on this issue is done.
Type: Bug
Use to signal issues that describe a bug within the system.
Validate necessity of High priority. Ideally, these issues are part of the release they’re assigned to.
Status: Obsolete
Use to signal this issue is no longer necessary.
Type: Enhancement
Use to signal an issue enhances an already existing feature of the project.
ReflectionUtils#ensureAccessible(T)
and ReflectionUtils#isAccessible(AccessibleObject)
Priority 2: Should
[#2845] Ensure ConfigurerModulue order is respected in Spring Autoconfiguration
Priority 1: Must
Highest priority. A release cannot be made if this issue isn’t resolved.
Status: Resolved
Use to signal that work on this issue is done.
Type: Bug
Use to signal issues that describe a bug within the system.
InfraConfiguration.springAxonConfigurer ignores ConfigurerModule.order()
Priority 1: Must
Highest priority. A release cannot be made if this issue isn’t resolved.
Status: Resolved
Use to signal that work on this issue is done.
Type: Bug
Use to signal issues that describe a bug within the system.
Instruct compiler to include parameter names metadata
Priority 2: Should
High priority. Ideally, these issues are part of the release they’re assigned to.
Status: Resolved
Use to signal that work on this issue is done.
Type: Feature
Use to signal an issue is completely new to the project.
Resolve classloading issue with ConnectionDetails
Priority 1: Must
Highest priority. A release cannot be made if this issue isn’t resolved.
Status: Resolved
Use to signal that work on this issue is done.
Type: Bug
Use to signal issues that describe a bug within the system.
Removed spring-devtools.properties
Priority 2: Should
High priority. Ideally, these issues are part of the release they’re assigned to.
Status: Resolved
Use to signal that work on this issue is done.
Type: Enhancement
Use to signal an issue enhances an already existing feature of the project.
Add support for Spring Docker Compose
Priority 3: Could
Low priority. Issues that are nice to have but have a straightforward workaround.
Status: Resolved
Use to signal that work on this issue is done.
Type: Feature
Use to signal an issue is completely new to the project.
Default to ReplayToken upon creation of new event processor
Priority 2: Should
High priority. Ideally, these issues are part of the release they’re assigned to.
Status: Resolved
Use to signal that work on this issue is done.
Type: Enhancement
Use to signal an issue enhances an already existing feature of the project.
Prevent processors from resetting when no handlers support replay
Priority 3: Could
Low priority. Issues that are nice to have but have a straightforward workaround.
Status: Resolved
Use to signal that work on this issue is done.
Type: Enhancement
Use to signal an issue enhances an already existing feature of the project.
Spring AoT fix
Priority 2: Should
High priority. Ideally, these issues are part of the release they’re assigned to.
Status: Resolved
Use to signal that work on this issue is done.
Type: Bug
Use to signal issues that describe a bug within the system.
Previous Next
ProTip!
Mix and match filters to narrow down what you’re looking for.