Skip to content

CAP message compatible #459

@cocosip

Description

@cocosip

Producer: CAP 2.6.0 +Kafka 2.1 + asp.net core 2.2
Consumer: CAP 3.0 preview +Kafka 2.1+ .net core 3.1
Error:

2019-12-19 15:31:57.6045|DotNetCore.CAP.Internal.Bootstrapper|DEBUG|### CAP background task is starting. 
2019-12-19 15:31:57.6045|DotNetCore.CAP.Processor.CapProcessingServer|INFO|Starting the processing server. 
2019-12-19 15:31:57.6045|DotNetCore.CAP.Processor.TransportCheckProcessor|DEBUG|Transport connection checking... 
2019-12-19 15:31:58.2683|DotNetCore.CAP.Processor.TransportCheckProcessor|DEBUG|Transport connection healthy! 
2019-12-19 15:31:58.2865|DotNetCore.CAP.Processor.CollectorProcessor|DEBUG|Collecting expired data from table: PublishedMessages 
2019-12-19 15:31:58.2884|DotNetCore.CAP.Processor.CollectorProcessor|DEBUG|Collecting expired data from table: ReceivedMessages 
2019-12-19 15:31:58.2884|DotNetCore.CAP.Internal.Bootstrapper|INFO|### CAP started! 
2019-12-19 15:31:58.3097|Microsoft.Hosting.Lifetime|INFO|Application started. Press Ctrl+C to shut down. 
2019-12-19 15:31:58.3097|Microsoft.Hosting.Lifetime|INFO|Hosting environment: Production 
2019-12-19 15:31:58.3097|Microsoft.Hosting.Lifetime|INFO|Content root path: G:\DotNet测试代码\CAPDemo\CAPConsumer1\bin\Debug\netcoreapp3.1\ 
2019-12-19 15:31:58.3097|Microsoft.Extensions.Hosting.Internal.Host|DEBUG|Hosting started 
2019-12-19 15:32:01.3925|DotNetCore.CAP.Internal.ConsumerRegister|DEBUG|Received message. id:, name:  
2019-12-19 15:32:01.4158|DotNetCore.CAP.Internal.ConsumerRegister|ERROR|An exception occurred when process received message. Message:'DotNetCore.CAP.Messages.TransportMessage'. The given key 'cap-msg-type' was not present in the dictionary.

When producer publish message, consumer can't get it. Is there any way that is compatible?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions