Hi
We have a solution where we via a File Adapter publish a large amount of "AD Update" messages (>500) within seconds and they are subscribed to by the "Microsoft Active Directory Adapter"
Our Active Directory is not happy with so many requests sent in a few seconds and many requests time out.
We are thinking of ways to handle this and were hoping for some good thinking from fellow Neuron developers:
1. We could add all requests ton a table and then read them at a reasonable speed, and then send to AD Adapter.
2. We could work with "Retry Count" and "Retry Interval" on Adapter Policies, so requests that timeout are sent again eg. 1 minute later.
3. We could try using MQ for the solution.
4. Something else?
Any ideas are very welcome ;-)
Regards André
Tags:
Hi André
I would also look into throttling. As I read it this is what it basically is about and what is causing the timeouts.
Under the Networking Tab for the Topic you can specify Publish Throttling and specify Messages per second, Messages per Minute, KB per time etc. Sounds like 10 messages per second could be a way to go, but this is usually a case of experimenting a bit and seeing if the server can handle the load.
I bellieve that the throttling setting should solve it for you.
Otherwise, you can also set more detailed restrictions on the topic in the Properties Pane such as:
- Allow Output Batching (set this to False)
- Max Concurrent Calls
- Max Concurrent Sessions
- Max Concurrent Instances
- Max Connections (could also be set to 10)
Best regards,
Christian
Excellent Christian
Throttling was just what we were looking for.
And can see that it works very well after a small test.
Thx
André
Great. That's good to hear :-)
Neuron ESB Product Support Forums and Communities
© 2024 Created by Neuron Admin. Powered by