Brighter icon indicating copy to clipboard operation
Brighter copied to clipboard
verified publisher icon BrighterCommand

[Bug] Inbox table is not getting populated when using EntityFrameworkCore-WebApi example

Open omelianlevkovych opened this issue 3 years ago • 4 comments

Describe the bug

The consumer Inbox table (Salutations database) is empty after handling the message broker message, even though the entity table (Salutations table) is getting populated.
I assume that from the box behavior is when getting the new entity instance in my consumer database I should also have new Inbox row in the database. Please correct me if I am wrong here.

It works when the UseInboxAsync attribute is used for the consumer handler.

To Reproduce

  • I am using Production launch settings dotnet run --launch-profile Production for the both GreetingsWeb and SalutationsAnalytics projects
  • Therefore I have spinned MySQL database instance via docker-compose (also with the phpmyadmin page for it and Rabbit Message Queue as a message broker)

Salutations table: image Inbox table: image

Further technical details

  • Latest Brighter version 9.1.2
  • Windows 10 OS with docker for RMQ, MySQL & phpmyadmin
  • > dotnet --info
.NET SDK (reflecting any global.json):
 Version:   6.0.300-preview.22154.4
 Commit:    1eb22793b6

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.22000
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\6.0.300-preview.22154.4\

.NET SDKs installed:
  5.0.302 [C:\Program Files\dotnet\sdk]
  6.0.200 [C:\Program Files\dotnet\sdk]
  6.0.300-preview.22154.4 [C:\Program Files\dotnet\sdk]m Files\dotnet\sdk\6.0.300-preview.22154.4\

omelianlevkovych avatar Mar 29 '22 19:03 omelianlevkovych

Sorry its taken me so long to response, I'll see if I can look at this over the next few days, I've yet to play with inbox as yet

preardon avatar Apr 12 '22 07:04 preardon

@preardon @IlSocio Yeah, I spotted this bug as well when working with @omelianlevkovych. It looks as though the global inbox has broken, whereas the explicit inbox still works. That suggests a problem with the pipeline registration of global inbox.

Workaround is to use the attribute on the handler for now.

iancooper avatar May 25 '22 07:05 iancooper

@preardon @IlSocio I'll pick this one up.

iancooper avatar May 25 '22 07:05 iancooper

Needs to check if the InboxConfiguration as part of ServiceActivator configuration fixes this

iancooper avatar Feb 07 '24 17:02 iancooper