Skip to content

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.

Sign up for GitHub

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

Clear current search query, filters, and sorts
91 Open 1,085 Closed
91 Open 1,085 Closed
Author
Filter by author
Label
Filter by label
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Milestones
Filter by milestone
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Spring: HierarchicalBeanFactory is not supported 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.
#1055 by OLibutzki was closed May 6, 2019 Release 4.2
@OLibutzki
3 👍 1
Register Parameter Resolvers in Test Fixtures 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: Enhancement Use to signal an issue enhances an already existing feature of the project.
#1050 by smcvb was closed Jan 9, 2020 Release 4.3
@smcvb
2 👍 1
Replace CI Services for Test Containers 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.
#1647 by smcvb was closed Dec 23, 2020 Release 4.5
1
@smcvb
👍 1
Allow easy (property) configuration for the claimTimeout of the default TokenStore 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.
#2708 by smcvb was closed May 23, 2023 Release 4.8.0
1
@gklijs
👍 1
Add matcher for exact class type Ideal for Contribution 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.
#2444 by Blackdread was closed Oct 27, 2022 Release 4.6.2
1
@Blackdread
3 👍 1
Automatic migration recipes to 4.7+ Ideal for Contribution 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.
#2596 by timtebeek was closed Feb 14, 2023 Release 4.7.2
@timtebeek
10 👍 1
Deprecated fallback warning with Spring 6.0.5 Priority 2: Should 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: Bug Use to signal issues that describe a bug within the system.
#2630 by nils-christian was closed Mar 9, 2023 Release 4.7.3
@smcvb
5 👍 1
Concepts of GenericEventMessage & DomainEventMessage gets lost 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.
#1697 by pepperbob was closed Feb 8, 2021 Release 4.4.7
@abuijze @smcvb
2 👍 1
Change jdbc column names to snake case as default. Ideal for Contribution 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: Enhancement Use to signal an issue enhances an already existing feature of the project.
#2074 by vab2048 was closed Feb 7, 2023 Release 4.8.0
1
@Blackdread
3 👍 1
Canceled subscription query remains active if updates Flux is not subscribed, causing error on emit 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.
#2299 by lbilger was closed Jul 22, 2022 Release 4.5.15
@smcvb
4 👍 1
Support for Finite State Machines within Aggregates Priority 2: Should High priority. Ideally, these issues are part of the release they’re assigned to. Status: Duplicate Use to signal this issue is a duplicate of another. Please refer to the other issue. Type: Feature Use to signal an issue is completely new to the project.
#2417 by Opayne93 was closed Oct 3, 2022
@smcvb
2 👍 1
Add NoToastPostgresSQLDialect Priority 3: Could Low priority. Issues that are nice to have but have a straightforward workaround. Status: Won't Fix Use to signal that the issue is acknowledged, but it’s decided that the work will not be performed. Type: Enhancement Use to signal an issue enhances an already existing feature of the project.
#2112 by YvonneCeelie was closed Mar 18, 2022
@YvonneCeelie
1 👍 1
Add an actuator health indicator to check the connection between the application and Axon Server 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.
#1964 by rzcastilho was closed Mar 14, 2022 Release 4.6.0
1
@smcvb
5 👍 1
AMQP-Client version conflict between axon-amp and spring-boot-starter-amqp 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: Dependency Upgrade Use to signal an issue that adjusts the project’s dependencies. Typically used by dependabot only.
#347 by jangalinski was closed Jun 8, 2017 Release 3.1
@abuijze
1 👍 1
Create awareness around token entries disk usage on PostgreSQL in the documentation when using the JPA implementation Type: Incorrect Repository Use to signal the issue is constructed in the wrong repository.
#1351 by rcusters was closed Feb 20, 2020
@smcvb @hatzlj
4 👍 1
Large number of rolled back transactions on JPA/JDBC TokenStore 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.
#1475 by abuijze was closed Jan 4, 2022 Release 4.6.0
@Vermorkentech
4 👍 1
Fine tune "No Handler For..." Exception 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.
#1646 by smcvb was closed Dec 29, 2021 Release 4.6.0
1
@smcvb
👍 1
No reconnect of AxonQueryBus after the AxonServer restarts 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.
#1411 by akraskovski was closed Apr 23, 2020 Release 4.3.2
@smcvb
14 👍 1
When loading the aggregrate prepare the Snapshot trigger first in the EventSourcingRepository Ideal for Contribution 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.
#1439 by YvonneCeelie was closed Dec 17, 2020 Release 4.5
1
@smcvb
👍 1
TrackingProcessorStatus should report estimated position and error status for each segment 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.
#1063 by abuijze was closed May 7, 2019 Release 4.2
1
@abuijze
2 👍 1
Slow JdbcTokenStore performance on PostgreSQL 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.
#1165 by sgrimm-sg was closed Jul 24, 2019 Release 4.2
1
@abuijze @sgrimm-sg
1 👍 1
Increasing the timeout for one test Ideal for Contribution 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: Enhancement Use to signal an issue enhances an already existing feature of the project.
#1349 by metao1 was closed Feb 19, 2020 Release 4.3
@smcvb
1 👍 1
Provide Bill of Materials Artifact Priority 2: Should 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: Feature Use to signal an issue is completely new to the project. Type: Incorrect Repository Use to signal the issue is constructed in the wrong repository.
#1200 by joshiste was closed Mar 9, 2021 Release 4.5
1
@smcvb
3 👍 1
Spring default processor mode in application.properties Priority 2: Should 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: Bug Use to signal issues that describe a bug within the system.
#1064 by m1l4n54v1c was closed Aug 10, 2020 Release 4.2.1
1 👍 1
Add asynchronous processor support to SagaConfiguration 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.
#263 by sgrimm-sg was closed Nov 14, 2017 Release 3.1
@abuijze
1 👍 1
ProTip! Follow long discussions with comments:>50.