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.
Add additional check for NoToken so we never try to open a stream with it.
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.
Skip jacoco if 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.
sonar-enabled
is false.
Priority 2: Should
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.
Weird state causing tracking processors to never advance
Priority 1: Must
Highest priority. A release cannot be made if this issue isn’t resolved.
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.
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
Make the viable name match with the override, the current name can be…
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: Bug
Use to signal issues that describe a bug within the system.
Add suppressible log message when console client is not on the classpath.
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.
Execute the axon-spring-boot-3-integrationtests actually with spring 3
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.
[#2843] Make it possible to have multiple instances of the DbScheduler components.
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.
[#2844] Improve shutdown behavior for 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.
DbSchedulerDeadlineManager
Priority 3: Could
Adding a DLQ tutorial
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: Documentation
Use to signal issues that describe documentation work.
TrackingEventProcessor does not start all threads in rare cases
Priority 3: Could
Low priority. Issues that are nice to have but have a straightforward workaround.
Status: Obsolete
Use to signal this issue is no longer necessary.
Type: Bug
Use to signal issues that describe a bug within the system.
#2848
by nils-christian
was closed Sep 28, 2023
AxonDbSchedulerAutoConfiguration can not be used multiple times in hierarchical Spring context due to static fields
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.
Log notification about AxonIQ console, if console-framework-client is not there
Priority 2: Should
High priority. Ideally, these issues are part of the release they’re assigned to.
Type: Feature
Use to signal an issue is completely new to the project.
Dead-Letter Sequence Identifier Caching
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.
Deadlines How-to
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: Documentation
Use to signal issues that describe documentation work.
Add property to easily disable using Axon Server as event store.
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.
Subscription Query Update Events are dropped when using AxonServer if the events are created with List.of or stream.toList().
Status: Information Required
Use to signal this issue is waiting for information to be provided in the issue's description.
Type: Question
Use to signal the issue is a question of how the project works and thus does not require development
#2768
by heutelbeck
was closed Jun 26, 2023
Enable tracing in DistributedCommandBus with SpanFactory
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.
Add db-scheduler implementation of the Event Scheduler and Deadline Manager
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.
When registering the same Saga multiple times, only the last one is kept.
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.
Add db-scheduler implementation of the Event Scheduler and Deadline Manager
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.
Make the token store claim timeout easily configurable.
Priority 4: Would
Lowest priority. Would-be-nice to include issues when time allows it.
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.
Add JCacheAdapter test scenarios
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.
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.