personball / abplus Goto Github PK

大神你好，我已经解决掉了所有异常，但是依然没有收到应答消息，我在Warn日志里面收到以下异常，请问这个插件内部有权限验证模块吗？当前用户已经登录系统了呀，为什么会报这个警告呢，希望能得到你的回复
WARN 2019-12-20 11:45:22,511 [ker 1] us.Retry.ErrorTracking.InMemErrorTracker - Unhandled exception 2 while handling message with ID "4cb46c5b-c35f-466f-964a-ae6a5b50875e"
Abp.Authorization.AbpAuthorizationException: 当前用户没有登录到系统！
at Abp.Authorization.AuthorizationHelper.AuthorizeAsync(IEnumerable1 authorizeAttributes) in D:\Github\aspnetboilerplate\src\Abp\Authorization\AuthorizationHelper.cs:line 42 at Abp.Authorization.AuthorizationHelper.CheckPermissions(MethodInfo methodInfo, Type type) in D:\Github\aspnetboilerplate\src\Abp\Authorization\AuthorizationHelper.cs:line 107 at Abp.Authorization.AuthorizationHelper.AuthorizeAsync(MethodInfo methodInfo, Type type) in D:\Github\aspnetboilerplate\src\Abp\Authorization\AuthorizationHelper.cs:line 56 at Nito.AsyncEx.Synchronous.TaskExtensions.WaitAndUnwrapException(Task task) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location where exception was thrown --- at System.Threading.Tasks.Task.ExecuteWithThreadLocal(Task& currentTaskSlot) --- End of stack trace from previous location where exception was thrown --- at Nito.AsyncEx.Synchronous.TaskExtensions.WaitAndUnwrapException(Task task) at Nito.AsyncEx.AsyncContext.Run(Func1 action)
at Abp.Authorization.AuthorizationInterceptor.Intercept(IInvocation invocation) in D:\Github\aspnetboilerplate\src\Abp\Authorization\AuthorizationInterceptor.cs:line 20
at Castle.DynamicProxy.AbstractInvocation.Proceed()
at Abp.Domain.Uow.UnitOfWorkInterceptor.PerformAsyncUow(IInvocation invocation, UnitOfWorkOptions options) in D:\Github\aspnetboilerplate\src\Abp\Domain\Uow\UnitOfWorkInterceptor.cs:line 78
at Castle.DynamicProxy.AbstractInvocation.Proceed()
at Abp.Auditing.AuditingInterceptor.PerformAsyncAuditing(IInvocation invocation, AuditInfo auditInfo) in D:\Github\aspnetboilerplate\src\Abp\Auditing\AuditingInterceptor.cs:line 86
at Castle.DynamicProxy.AbstractInvocation.Proceed()
at Castle.DynamicProxy.AbstractInvocation.Proceed()
at Castle.Proxies.IHandleMessages1Proxy.Handle(TestMessage message) at Rebus.Pipeline.Receive.HandlerInvoker1.Invoke() in C:\projects-rebus\Rebus\Rebus\Pipeline\Receive\HandlerInvoker.cs:line 154
at Rebus.Pipeline.Receive.DispatchIncomingMessageStep.Process(IncomingStepContext context, Func1 next) in C:\projects-rebus\Rebus\Rebus\Pipeline\Receive\DispatchIncomingMessageStep.cs:line 67 at Rebus.Sagas.LoadSagaDataStep.Process(IncomingStepContext context, Func1 next) in C:\projects-rebus\Rebus\Rebus\Sagas\LoadSagaDataStep.cs:line 66
at Rebus.Pipeline.Receive.ActivateHandlersStep.Process(IncomingStepContext context, Func1 next) in C:\projects-rebus\Rebus\Rebus\Pipeline\Receive\ActivateHandlersStep.cs:line 47 at Rebus.Pipeline.Receive.HandleRoutingSlipsStep.Process(IncomingStepContext context, Func1 next) in C:\projects-rebus\Rebus\Rebus\Pipeline\Receive\HandleRoutingSlipsStep.cs:line 42
at Rebus.Retry.Simple.FailedMessageWrapperStep.Process(IncomingStepContext context, Func1 next) in C:\projects-rebus\Rebus\Rebus\Retry\Simple\FailedMessageWrapperStep.cs:line 42 at Rebus.Pipeline.Receive.DeserializeIncomingMessageStep.Process(IncomingStepContext context, Func1 next) in C:\projects-rebus\Rebus\Rebus\Pipeline\Receive\DeserializeIncomingMessageStep.cs:line 34
at Rebus.Pipeline.Receive.HandleDeferredMessagesStep.Process(IncomingStepContext context, Func1 next) in C:\projects-rebus\Rebus\Rebus\Pipeline\Receive\HandleDeferredMessagesStep.cs:line 121 at Rebus.Retry.FailFast.FailFastStep.Process(IncomingStepContext context, Func1 next) in C:\projects-rebus\Rebus\Rebus\Retry\FailFast\FailFastStep.cs:line 41
at Rebus.Retry.Simple.SimpleRetryStrategyStep.DispatchWithTrackerIdentifier(Func`1 next, String identifierToTrackMessageBy, ITransactionContext transactionContext, String messageId, String secondLevelMessageId) in C:\projects-rebus\Rebus\Rebus\Retry\Simple\SimpleRetryStrategyStep.cs:line 120

消息能持久化吗？怎么处理

问什么不通过Castle的程序集注册Convention的模式扫描IHandleMessage接口直接注册队列处理程序，反而要额外指定程序集的形式去获取？ 直接通过程序集注册感觉集成度更高也减少使用方面的交互（不然觉得为什么塞个程序集进去莫名其妙，就感觉集成度很低）

mq部分依赖包，检测不能完全兼容

rebus-org/Rebus#163
https://www.rabbitmq.com/blog/2012/05/11/some-queuing-theory-throughput-latency-and-bandwidth/
https://github.com/rebus-org/Rebus/pull/164/files

{
     code:0
     message:"success"
     result:{}
}

如果要改成以上这种，可以在abp什么地方改的，提供的思路就可以了，因为我看见你博客有这个目录，所以想提早问一下这个，谢谢= =

貌似这两个类是跟Ef的热加载有关？

添加自动发现和注册 IEntityTypeConfiguration的辅助方法

你好，我想请问一下
我多个生产者、 多个生产责 配置不同的队列名 相对应的有对应的消费者。 但是现在在
_bus = rebusConfig.Transport(c => c.UseRabbitMq(moduleConfig.ConnectString, moduleConfig.QueueName)).Start();
transport第二个队列名称时　提示：An IBus service is already registered in this container. If you want to host multiple Rebus instances in a single process, please use separate container instances for them.

告诉我这个Ｉbus 已经在容器中注册了 我想达到的目的就是不同业务 使用不同队列

您好作者，我觉得你应该是位**的大神，所以就没有将问题翻译成英文，毕竟我的英语也很歪。我在使用你的插件时，遇到这个错误：
InvalidOperationException: An IBus service is already registered in this container. If you want to host multiple Rebus instances in a single process, please use separate container instances for them.

事情的起因是我在我的项目里面使用了队列，队列的发布端在展现层的控制器里面，订阅端在应用层里面，也就是发布端和订阅端都在同一个项目里面，然后就报这个错了，把订阅端的代码注释了就好了，请问一下怎么实现，在单个进程中托管多个Rebus实例

其实这个错误很明显，但是菜的一笔的我，不知道怎么解决，希望能得到您的帮助

1.根据Core程序集中开发人员自定义的EventData，反射自动生成相应的Message
2.根据1自动生成的Message程序集，自动批量生成发布消息的Module

Hi - Thanks very much for your work here. Did you get SignalR chat to work with a Redis server? I've got your code running and it seems to work when all users are connected to the same web server. But if the users are connected to different web servers, the users appear to be "offline". I can see the users registered in the Redis server in the Abplus.RealTime.OnlineClients.Clients and Users. So I'm not entirely sure what the issue is. It seems like Abp maybe defaulting back to using the original Abp Chat functionality. Any help would be appreciated.

Thanks again,
Craig