Usage of the client library under high loads

[cregonat]

Hi guys,

I'm working on a project using this library and I'm getting some some strange behaviour with the client under high loads. I.E. when the program sends many messages asynchronously, not all of them are sent. Client is configured this way right now:

"asynchronous":{ "processingTasks":1, "timeToLive":"4.00:00:0", "readTimeout":"00:01:00" },
"maxSenders":10, "maxFactories":10, "myHerId":135652 },
with this configuration, if I send two messages almost at the same time, only one of them will be sent. however, if a pause of 20 seconds between messages is used, then both of the messages will be sent.

Any help with this is appreciated,
Thanks!

[kennethmyhra]

Hey @cregonat,

Which version are you using? If you have migrated from the 3.x to 4.0 library make sure that you are awaiting the methods. The 4.0 library makes more use of the async/await pattern.

The client is currently used under high load and have been so for a long time, both 4.0 and the older versions, and we have not experienced such problems.

Looking at your configuration, the MaxFactories is not recommended to be above 1. It sets up several AMQP Connections and even with our load we do not need more than 1 AMQP Connection.

[cregonat]

Thanks for the answer Kenneth,
We're using the 3.x version. I'll try using 1 for maxFactories.

[kennethmyhra]

@cregonat Could you send me an e-mail kenneth.myhra at nhn.no. I would like to know more about the context you are using this library since the scope of this project is quite narrow, scoped to the Norwegian Health Sector.

I'd also like to make you aware that the 3.x library will be deprecated this year since we are moving away from the Service Bus Message Protocol to AMQP 1.0.