Custom queue object not receiving in Steeltoe rabbitMQ messaging

[ahmedanwar100]

Custom queue object not receiving in Steeltoe rabbitMQ messaging

[ahmedanwar100]

i think we have to serialize the object like this
_rabbitTemplate.ConvertAndSend(RECEIVE_AND_CONVERT_QUEUE, JsonConvert.SerializeObject(customMsg));

and then make Listner like this

[RabbitListener(RECEIVE_AND_CONVERT_QUEUE)] public void ListenForAMessage(string msg) { var x=JsonConvert.DeserializeObject<CustomQueue>(msg); _logger.LogInformation($"Received the message '{msg}' from the queue."); }

[dtillman]

@bradLucifer : Yes, the problem you are seeing is that by default we use BinaryFormatter to serialize objects. As a result on the receiving side the deserialization attempts to deserialize the payload and expects to find the type available so that it can create an instance of it. The type if finds is not the same one that is being sent because the assemblies they are in are different. So you have a couple options:

1. Put the common type CustomQueue in a separate project and reference it the other two rabbitmq projects. That way the type will be common and in a shared assembly accessible by both.
2. Switch to using Json for the serialization protocol.
   Dave

[ahmedanwar100]

thanks for your reply. can you send me a sample project, it will really help me Thanks in advance

…

On Tue, Jan 18, 2022 at 10:23 PM Dave Tillman ***@***.***> wrote: @bradLucifer <https://github.com/bradLucifer> : Yes, the problem you are seeing is that by default we use BinaryFormatter to serialize objects. As a result on the receiving side the deserialization attempts to deserialize the payload and expects to find the type available so that it can create an instance of it. The type if finds is not the same one that is being sent because the assemblies they are in are different. So you have a couple options: 1. Put the common type CustomQueue in a separate project and reference it the other two rabbitmq projects. That way the type will be common and in a shared assembly accessible by both. 2. Switch to using Json for the serialization protocol. Dave — Reply to this email directly, view it on GitHub <#232 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AILYWTSH4K2ZGSXAI6JPSILUWWO2VANCNFSM5LQXHCZA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[dtillman]

@bradLucifer : Which do you prefer .. 1. Common project/.NET Serialization 2. JSON?

[ahmedanwar100]

If you have time then i want to look both

…

On Wed, Jan 19, 2022, 12:00 AM Dave Tillman ***@***.***> wrote: @bradLucifer <https://github.com/bradLucifer> : Which do you prefer .. 1. Common project/.NET Serialization 2. JSON? — Reply to this email directly, view it on GitHub <#232 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AILYWTXM4OG7MWODY3SM5I3UWW2EZANCNFSM5LQXHCZA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[dtillman]

@bradLucifer : https://github.com/SteeltoeOSS/Samples/tree/main/Messaging/src/RabbitMQWeb2

I think this should help... See the Startup.cs file in each project for how to enable/disable the .NET serialization vs JSON.

[ahmedanwar100]

Hi, binary serialization is obsolete and i want to use json serialization. Can you explain it a little bit

…

On Wed, Jan 19, 2022 at 2:51 AM Dave Tillman ***@***.***> wrote: @bradLucifer <https://github.com/bradLucifer> : https://github.com/SteeltoeOSS/Samples/tree/main/Messaging/src/RabbitMQWeb2 I think this should help... See the Startup.cs file in each project for how to enable/disable the .NET serialization vs JSON. — Reply to this email directly, view it on GitHub <#232 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AILYWTTGMC5IZCGS7TP5ZGTUWXOE5ANCNFSM5LQXHCZA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[dtillman]

In the startup.cs files for both projects, see the following comments.:

// Add Steeltoe Rabbit services, use default .NET serialization
//services.AddRabbitServices();

// Add Steeltoe Rabbit services, use JSON serialization
services.AddRabbitServices(true);

[ahmedanwar100]

Thanks a lot.

…

On Mon, Feb 7, 2022 at 8:40 PM Dave Tillman ***@***.***> wrote: In the startup.cs files for both projects, see the following comments.: // Add Steeltoe Rabbit services, use default .NET serialization //services.AddRabbitServices(); // Add Steeltoe Rabbit services, use JSON serialization services.AddRabbitServices(true); — Reply to this email directly, view it on GitHub <#232 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AILYWTXAVFZ3BOWPSWYJSLTUZ7RW3ANCNFSM5LQXHCZA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[ahmedanwar100]

sorry to disturb you again. But We have a flow request -> MicroService1 (this service raise a event) -> Microservice2 (this service saves the data) I have a scenario where i want to inform the UI that data is saved successfully through microservice2 so what will be best approach that should be adopted. I have a approach: 1. Create a notification microservice and raise a event from Microservice2 which will be listened by Notification Service and it will have a signalR set up in it and UI will be informed through it. have you any other options, it will be really helpful if you suggest any approach Thanks in advance

…

On Wed, Feb 9, 2022 at 3:19 PM Ahmed Anwer ***@***.***> wrote: Thanks a lot. On Mon, Feb 7, 2022 at 8:40 PM Dave Tillman ***@***.***> wrote: > In the startup.cs files for both projects, see the following comments.: > > // Add Steeltoe Rabbit services, use default .NET serialization > //services.AddRabbitServices(); > > // Add Steeltoe Rabbit services, use JSON serialization > services.AddRabbitServices(true); > > — > Reply to this email directly, view it on GitHub > <#232 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AILYWTXAVFZ3BOWPSWYJSLTUZ7RW3ANCNFSM5LQXHCZA> > . > Triage notifications on the go with GitHub Mobile for iOS > <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or Android > <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. > > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

[ahmedanwar100]

Hi, getting a warning on Server in logs Container AcknowledgeMode must be MANUAL for a Future<?> return type; otherwise the container will ack the message immediately

…

On Mon, Feb 14, 2022 at 1:35 PM Ahmed Anwer ***@***.***> wrote: sorry to disturb you again. But We have a flow request -> MicroService1 (this service raise a event) -> Microservice2 (this service saves the data) I have a scenario where i want to inform the UI that data is saved successfully through microservice2 so what will be best approach that should be adopted. I have a approach: 1. Create a notification microservice and raise a event from Microservice2 which will be listened by Notification Service and it will have a signalR set up in it and UI will be informed through it. have you any other options, it will be really helpful if you suggest any approach Thanks in advance On Wed, Feb 9, 2022 at 3:19 PM Ahmed Anwer ***@***.***> wrote: > Thanks a lot. > > On Mon, Feb 7, 2022 at 8:40 PM Dave Tillman ***@***.***> > wrote: > >> In the startup.cs files for both projects, see the following comments.: >> >> // Add Steeltoe Rabbit services, use default .NET serialization >> //services.AddRabbitServices(); >> >> // Add Steeltoe Rabbit services, use JSON serialization >> services.AddRabbitServices(true); >> >> — >> Reply to this email directly, view it on GitHub >> <#232 (comment)>, >> or unsubscribe >> <https://github.com/notifications/unsubscribe-auth/AILYWTXAVFZ3BOWPSWYJSLTUZ7RW3ANCNFSM5LQXHCZA> >> . >> Triage notifications on the go with GitHub Mobile for iOS >> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> >> or Android >> <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. >> >> You are receiving this because you were mentioned.Message ID: >> ***@***.***> >> >