search

Particular / NServiceBus

Build, version, and monitor better microservices with the most powerful service platform for .NET
https://particular.net/nservicebus/
Other
2.09k stars 648 forks source link

Windows Service timing out #533

Closed HEskandari closed 11 years ago

HEskandari commented 12 years ago

I'm installing the NServiceBus host as a service and I'm deploying and starting multiple instances of the service (different configs) using a deployment script. some of them are failing to start up properly and time out. I'm using NET START to start the services. There are numerous assemblies in the application folder and scanning all of them to find the endpoint and configurations can cause time outs.

I can start the services in the Control Panel -> Services after they time out or by running NET START again.

Think happens when the service being started does not report back that it is alive and is initializing. AFAIK this could be handled by calling SetServiceStatus when windows service is being installed.

Wondering if this is related to NServiceBus Host or I should report this back to TopShelf?

SimonCropp commented 12 years ago

bump

johnsimons commented 12 years ago

Just wondering if you explicitly configure the endpoint type via the config file would it still time out ? Like this:

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
  <appSettings>
    <add key="EndpointConfigurationType" value="YourNamespace.YourTypeName, YourAssembly"/>
  </appSettings>
</configuration>

Also, we have done quite a few improvements at start-up in v4 (not released yet) so it will be interesting to find out if those changes would improve this situation.

johnsimons commented 11 years ago

Can you try v4 and see if this is still an issue?

SimonCropp commented 11 years ago

I have moved over to self hosting for all my services and have no perf problems. After seeing how easy it is to self host i dont think i will ever go back to the NSB Host

SimonCropp commented 11 years ago

@HEskandari can you retest this?

SimonCropp commented 11 years ago

no response so closing