从Saga调度命令时未调用事件处理程序

如何解决从Saga调度命令时未调用事件处理程序

我有一个usersHttpService: accept(code: string,user: UserInfo) { return this.http.post(`${this.env.MY URL}/mon/accepting/${code}/accept`,user); } CommandHandlerEventSourcingHandler链,当直接分派命令EventHandler时,它们都按预期被调用。如果从Foo或公用EventHandler中分派同一命令,则不会导致调用同一Saga

不幸的是,我无法透露实际的代码,但这是发生的情况的说明:

Illustration of the issue

未调用的EventHandler仅将事件作为参数,没有带注释的EventHandler或类似参数。它负责写入读取模型,@MetaData需要继续执行该读取模型。此时,此过程失败,因为尚未更新读取模型,因为尚未调用@SagaEventHandler

这里可能是什么问题?使用Axon 4.3.1。

配置:

EventHandler

简短的通话链:

  1. 通过HTTP请求接收到初始命令。
/*
 * Copyright (c) 2020 divine Cloud Services Ltd.
 * All rights reserved
 *
 * All information contained herein is and remains the property of
 * divine Cloud Services Ltd. The intellectual and technical concepts
 * contained herein are proprietary to divine Cloud Services Ltd. and
 * may be protected by trade secret or copyright law. Dissemination
 * of this information or reproduction of this material is strictly prohibited
 * unless prior written permission is obtained from divine Cloud Services Ltd.
 */

package engineering.divine.infrastructure.conf;

import engineering.divine.artefact.model.meta.ArtefactDefinition;
import engineering.divine.artefact.ports.ArtefactDefinitionRepository;
import engineering.divine.infrastructure.persistence.BinarySerialiser;
import engineering.divine.infrastructure.persistence.DefaultArtefactDefinitionRepository;
import engineering.divine.infrastructure.persistence.graph.GraphEventStorageEngine;
import engineering.divine.infrastructure.persistence.graph.database.GraphManager;
import engineering.divine.infrastructure.security.interceptors.AuditCommandDispatchInterceptor;
import engineering.divine.integration.github.GitHubCommandHandler;
import engineering.divine.integration.github.GitHubQueryHandler;
import org.axonframework.commandhandling.CommandBus;
import org.axonframework.commandhandling.CommandMessage;
import org.axonframework.commandhandling.SimpleCommandBus;
import org.axonframework.common.transaction.TransactionManager;
import org.axonframework.config.Configurer;
import org.axonframework.config.EventProcessingConfigurer;
import org.axonframework.eventhandling.PropagatingErrorHandler;
import org.axonframework.eventsourcing.EventCountSnapshotTriggerDefinition;
import org.axonframework.eventsourcing.EventSourcingRepository;
import org.axonframework.eventsourcing.SnapshotTriggerDefinition;
import org.axonframework.eventsourcing.Snapshotter;
import org.axonframework.eventsourcing.eventstore.EmbeddedEventStore;
import org.axonframework.eventsourcing.eventstore.EventStorageEngine;
import org.axonframework.eventsourcing.eventstore.EventStore;
import org.axonframework.messaging.interceptors.BeanValidationInterceptor;
import org.axonframework.modelling.command.Repository;
import org.axonframework.queryhandling.QueryBus;
import org.axonframework.queryhandling.QueryMessage;
import org.axonframework.queryhandling.SimpleQueryBus;
import org.axonframework.spring.eventsourcing.SpringAggregateSnapshotterFactoryBean;
import org.springframework.beans.BeansException;
import org.springframework.beans.factory.annotation.Autowired;
import org.springframework.beans.factory.annotation.Value;
import org.springframework.context.ApplicationContext;
import org.springframework.context.ApplicationContextAware;
import org.springframework.context.annotation.Bean;
import org.springframework.context.annotation.Configuration;
import org.springframework.context.annotation.Primary;

import java.util.concurrent.Executors;

@SuppressWarnings("unchecked")
@Configuration
public class AxonConfig implements ApplicationContextAware {

    private ApplicationContext applicationContext;

    @Value("${engineering.divine.snapshot.threshold:30}")
    private int snapshotThreshold;

    @Bean
    public CommandBus commandBus(TransactionManager transactionManager,AuditCommandDispatchInterceptor auditCommandDispatchInterceptor,BeanValidationInterceptor<CommandMessage<?>> validationInterceptor) {

        SimpleCommandBus commandBus = SimpleCommandBus.builder()
                .transactionManager(transactionManager)
                .build();

        commandBus.registerDispatchInterceptor(auditCommandDispatchInterceptor);
        commandBus.registerDispatchInterceptor(validationInterceptor);

        return commandBus;
    }

    @Bean
    public QueryBus queryBus(TransactionManager transactionManager,BeanValidationInterceptor<QueryMessage<?,?>> validationInterceptor) {
        SimpleQueryBus queryBus = SimpleQueryBus.builder()
                .transactionManager(transactionManager)
                .build();

        queryBus.registerDispatchInterceptor(validationInterceptor);

        return queryBus;
    }

    @Bean
    @Primary
    EventStore eventStore(GraphManager graphManager,BinarySerialiser serialiser) {
        EventStorageEngine storageEngine = GraphEventStorageEngine
                .builder()
                .graphManager(graphManager)
                .serialiser(serialiser)
                .build();

        return EmbeddedEventStore.builder()
                .storageEngine(storageEngine)
                .build();
    }

    @Bean
    Snapshotter snapshotter(EventStore eventStore) {
        SpringAggregateSnapshotterFactoryBean factoryBean = new SpringAggregateSnapshotterFactoryBean();
        factoryBean.setApplicationContext(applicationContext);
        factoryBean.setEventStore(eventStore);
        factoryBean.setExecutor(Executors.newSingleThreadExecutor());
        return factoryBean.getObject();
    }

    @Bean
    SnapshotTriggerDefinition snapshotTriggerDefinition(Snapshotter snapshotter) {
        return new EventCountSnapshotTriggerDefinition(snapshotter,snapshotThreshold);
    }

    @Bean
    ArtefactDefinitionRepository artefactDefinitionRepository(EventStore eventStore) {
        Repository<ArtefactDefinition> delegate = EventSourcingRepository
                .builder(ArtefactDefinition.class)
                .eventStore(eventStore)
                .build();

        return new DefaultArtefactDefinitionRepository(delegate);
    }

    @Bean
    BeanValidationInterceptor<CommandMessage<?>> beanValidationCommandInterceptor() {
        return new BeanValidationInterceptor();
    }

    @Bean
    BeanValidationInterceptor<QueryMessage<?,?>> beanValidationQueryInterceptor() {
        return new BeanValidationInterceptor();
    }

    @Autowired
    public void configure(EventProcessingConfigurer configurer) {
        configurer.usingSubscribingEventProcessors();
        configurer.registerDefaultListenerInvocationErrorHandler(configuration -> PropagatingErrorHandler.instance());
    }

    @Autowired
    public void configure(Configurer configurer,GitHubCommandHandler commandHandler,GitHubQueryHandler queryHandler) {
        configurer.registerCommandHandler(c -> commandHandler);
        configurer.registerQueryHandler(c -> queryHandler);
    }

    @Override
    public void setApplicationContext(ApplicationContext applicationContext) throws BeansException {
        this.applicationContext = applicationContext;
    }
}

  1. 命令A产生一个新的@RestController public class Controller { ... @RequestMapping("/doA") public CompletableFuture<Void> doA(@RequestBody CommandA cmdA) { ... // Do something else before cmdA CommandX cmdX = new CommandX(); commandGateway.sendAndWait(cmdX); ... commandGateway.sendAndWait(cmdA); } }
@Aggregate
  1. @Aggregate public class MyFooAggregate { @CommandHandler public MyFooAggregate(CommandA cmd,MetaData metaData) { apply(new FooCreated(),metaData); } ... } 接获@Saga事件并发出新命令。没有针对sagas的独特配置类。
FooCreated
  1. 不是集合的专用命令处理程序负责命令B。它使用接口@Saga public class MySaga { // (end will not be the same as start in the future) @StartSaga @EndSaga @SagaEventHandler(associationProperty = "id") public void handleFooCreated(FooCreated event,@MetaDataValue("valueX") String valueX,CommandGateway commandGateway) { CommandB cmdB = new CommandB(); ... Map<String,Object> meta = new HashMap<>(); meta.put("valueX",valueX); CommandMessage<CommandB> cmdMsg = GenericCommandMessage.asCommandMessage(cmdB); cmdMsg.withMetaData(meta); // because I don't need to wait for the result,I'll just "send" it commandGateway.send(cmdMsg); } } ,实现为该接口调度另一个命令。该处理程序已在配置中注册(请参见MyProvider)。
AxonConfig
  1. @Component public class CommandHandler { MyProvider provider; @CommandHandler public void doB(CommandB cmdB) { ... provider.provideMeWithSomething(); ...  } } 的实现最终调度了命令C。
MyProvider
  1. 命令C产生一个新的@Component public class MyDefaultProvider implements MyProvider { @Override public Object provideMeWithSomething() { CommandC cmdC = new CommandC(); commandGateway.sendAndWait(cmdC); ... } } 。创建此聚合所调度的事件是@Aggregate中正在处理的事件,但找不到到达@EventSourcingHandler的事件。
@EventHandler
  1. 同一类@Aggregate public class MyBarAggregate { @CommandHandler public MyBarAggregate(CommandC cmdC) { apply(new BarCreated()); } ... } 中的@EventSourcingHandler被调用,但不是负责编写读取模型的公用MyBarAggregate
@EventHandler

但是,@Aggregate public class MyBarAggregate { ... @EventSourcingHandler public handleBarCreated(BarCreated event) { // DOES get called ... } } @Component public class EventHandler { @EventHandler public handleBarCreated(BarCreated event) { // DOES NOT get called ... } } 被直接调度时(例如,从CommandC内部),两个事件处理程序都会被调用。其他@RestController确实会被调用,只有在这种特定情况下才有此特定实例。

解决方法

首先,我在考虑您使用的EventProcessor的类型,试图找出问题所在。如配置所示(感谢添加),您正在使用SubscribingEventProcessor

从本质上讲,这意味着发布命令(在本例中为Saga)的同一线程(至少应该)调用了@EventHandler注释方法,因为这就是SubscribingEventProcessor的工作方式。尤其是如果您正在执行CommandGateway#sendAndWait(Object),这意味着锁定Saga的线程还将锁定聚集以处理命令,并将负责向SubscribingEventProcessor的事件提供相同的事件。所说的事件处理程序(未被调用)。

因此,第二,您如何调度该命令?不能共享确切的代码很好,但是sample / pseudocode应该可行吧? 第三,传奇如何配置?只是具有@Saga构造型的常规Spring自动配置,还是有独特的配置类?

说实话,我仍然很难理解为什么没有调用负责SubscribingEventProcessor注释功能的@EventHandler。您可以确认是否未调用属于此SubscribingEventProcessor所有事件处理程序,或者仅仅是该事件处理类吗?

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


依赖报错 idea导入项目后依赖报错,解决方案:https://blog.csdn.net/weixin_42420249/article/details/81191861 依赖版本报错:更换其他版本 无法下载依赖可参考:https://blog.csdn.net/weixin_42628809/a
错误1:代码生成器依赖和mybatis依赖冲突 启动项目时报错如下 2021-12-03 13:33:33.927 ERROR 7228 [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPL
错误1:gradle项目控制台输出为乱码 # 解决方案:https://blog.csdn.net/weixin_43501566/article/details/112482302 # 在gradle-wrapper.properties 添加以下内容 org.gradle.jvmargs=-Df
错误还原:在查询的过程中,传入的workType为0时,该条件不起作用 &lt;select id=&quot;xxx&quot;&gt; SELECT di.id, di.name, di.work_type, di.updated... &lt;where&gt; &lt;if test=&qu
报错如下,gcc版本太低 ^ server.c:5346:31: 错误:‘struct redisServer’没有名为‘server_cpulist’的成员 redisSetCpuAffinity(server.server_cpulist); ^ server.c: 在函数‘hasActiveC
解决方案1 1、改项目中.idea/workspace.xml配置文件,增加dynamic.classpath参数 2、搜索PropertiesComponent,添加如下 &lt;property name=&quot;dynamic.classpath&quot; value=&quot;tru
删除根组件app.vue中的默认代码后报错:Module Error (from ./node_modules/eslint-loader/index.js): 解决方案:关闭ESlint代码检测,在项目根目录创建vue.config.js,在文件中添加 module.exports = { lin
查看spark默认的python版本 [root@master day27]# pyspark /home/software/spark-2.3.4-bin-hadoop2.7/conf/spark-env.sh: line 2: /usr/local/hadoop/bin/hadoop: No s
使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams[&#39;font.sans-serif&#39;] = [&#39;SimHei&#39;] # 能正确显示负号 p
错误1:Request method ‘DELETE‘ not supported 错误还原:controller层有一个接口,访问该接口时报错:Request method ‘DELETE‘ not supported 错误原因:没有接收到前端传入的参数,修改为如下 参考 错误2:cannot r
错误1:启动docker镜像时报错:Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法:重启docker -&gt; systemctl r
错误1:private field ‘xxx‘ is never assigned 按Altʾnter快捷键,选择第2项 参考:https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2:启动时报错,不能找到主启动类 #
报错如下,通过源不能下载,最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
错误1:maven打包报错 错误还原:使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
错误1:服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping(&quot;/hires&quot;) public class FeignControl
错误1:运行项目后报如下错误 解决方案 报错2:Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案:在pom.
参考 错误原因 过滤器或拦截器在生效时,redisTemplate还没有注入 解决方案:在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate&lt;String
使用vite构建项目报错 C:\Users\ychen\work&gt;npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-