{"action":"opened","issue":{"url":"https://api.github.com/repos/Particular/NServiceBus/issues/3648","repository_url":"https://api.github.com/repos/Particular/NServiceBus","labels_url":"https://api.github.com/repos/Particular/NServiceBus/issues/3648/labels{/name}","comments_url":"https://api.github.com/repos/Particular/NServiceBus/issues/3648/comments","events_url":"https://api.github.com/repos/Particular/NServiceBus/issues/3648/events","html_url":"https://github.com/Particular/NServiceBus/issues/3648","id":144676741,"number":3648,"title":"NServiceBus does not respect MaximumConcurrencyLevel when using Azure ServiceBus","user":{"login":"particularbot","id":6763890,"avatar_url":"https://avatars.githubusercontent.com/u/6763890?v=3","gravatar_id":"","url":"https://api.github.com/users/particularbot","html_url":"https://github.com/particularbot","followers_url":"https://api.github.com/users/particularbot/followers","following_url":"https://api.github.com/users/particularbot/following{/other_user}","gists_url":"https://api.github.com/users/particularbot/gists{/gist_id}","starred_url":"https://api.github.com/users/particularbot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/particularbot/subscriptions","organizations_url":"https://api.github.com/users/particularbot/orgs","repos_url":"https://api.github.com/users/particularbot/repos","events_url":"https://api.github.com/users/particularbot/events{/privacy}","received_events_url":"https://api.github.com/users/particularbot/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-03-30T18:13:33Z","updated_at":"2016-03-30T18:13:33Z","closed_at":null,"body":"**Issue by [RipalV](https://github.com/RipalV)** _3/30/2016 4:17:10 PM +00:00_ _Originally opened as https://github.com/Particular/NServiceBus.Azure/issues/278_\r\n\r\n----\r\n\r\nNServiceBus is processing messages single threaded when using Azure ServiceBus with BatchSize and MaximumConcurrencyLevel set to a value more than 1.\r\nWe are using NServiceBus 5.2.9 and NServiceBus.Azure.Transports.WindowsAzureServiceBus 6.3.2 and below is the configuration that we specify.\r\nAzureServiceBusQueueConfig & TransportConfig has below configuration and using valid license.\r\n\r\n`    public class AzureServiceBusQueueConfigProvider : IProvideConfiguration<AzureServiceBusQueueConfig>\r\n    {\r\n        public AzureServiceBusQueueConfig GetConfiguration()\r\n        {\r\n            return new AzureServiceBusQueueConfig\r\n                       {\r\n                           BatchSize = 3,\r\n                           MaxDeliveryCount = 3,\r\n                           LockDuration = 120000\r\n                       };\r\n        }\r\n    }\r\n    public class TransportConfigProvider : IProvideConfiguration<TransportConfig>\r\n    {\r\n        public TransportConfig GetConfiguration()\r\n        {\r\n            return new TransportConfig\r\n            {\r\n                MaximumConcurrencyLevel = 3\r\n            };\r\n        }\r\n    }\r\n`\r\n\r\nBelow NServiceBus help page suggests setting **MaximumConcurrencyLevel**:\r\nhttp://docs.particular.net/nservicebus/azure/azure-servicebus-transport#scenarios-cpu-vs-io-bound-processing\r\n\r\nBut it is making no difference, still processes single threaded, I was expecting it to have 3 threads as per above config.\r\nBreakpoint inside `GetConfiguration` for `IProvideConfiguration<TransportConfig>` is not getting hit at all, which suggests NServiceBus is not looking at TransportConfig when using Azure ServiceBus.\r\nI have also tried specifying this configuration in web.config, but has made no difference.\r\n\r\nIs that something I am missing here? Issue could be reproduced from the above code snippet.\r\n"}}