Closed CRuppert closed 9 years ago
@CRuppert are you referring to the critical bug regarding timeouts? The fix was in NServiceBus.Azure, not the host. Could you please let know all the packages and their exact versions you're using?
@SeanFeldman Yeah, the timeouts issue is what started the upgrades. I know it was just for the Azure package, but while I was at it, I upgraded the rest of the packages.
<package id="NServiceBus" version="5.2.8" targetFramework="net45" />
<package id="NServiceBus.Azure" version="6.2.3" targetFramework="net45" />
<package id="NServiceBus.Azure.Transports.WindowsAzureServiceBus" version="6.3.2" targetFramework="net45" />
<package id="NServiceBus.CastleWindsor" version="5.0.0" targetFramework="net45" />
<package id="NServiceBus.Hosting.Azure" version="6.2.4" targetFramework="net45" />
<package id="NServiceBus.Hosting.Azure.HostProcess" version="6.2.4" targetFramework="net45" />
<package id="NServiceBus.Log4Net" version="1.0.0" targetFramework="net45" />
<package id="NServiceBus.Persistence.MongoDb" version="5.0.27.0" targetFramework="net45" />
<package id="ServiceControl.Plugin.Nsb5.Heartbeat" version="1.1.0" targetFramework="net45" />
<package id="WindowsAzure.ServiceBus" version="2.6.0" targetFramework="net45" />
<package id="WindowsAzure.Storage" version="4.3.0" targetFramework="net45" />
I have it nailed down to what I described though. Execute the endpoint without the arg and it bombs because of an empty string error. Throw it in with the name of my endpoint's assembly and it fires right up.
I have quickly verified that host is working as before. @CRuppert could you please try this sample and see if it's working for you or provide a simple repro?
Sorry @SeanFeldman, our bad. Someone had some incorrect references. Unfortunately the error messaging for the host stuff did not indicate that as per usual. Apologies!
No worries at all @CRuppert
Upgraded to latest as per product advisory this morning, was still in the 6.2 line prior to update.
First noticed when I could not debug. Throws as
you can resolve this by passing
/scannedAssemblies=<EndpointAssemblyName>
on the command line and everything executes fine.However, there is no way to do this when running in the Azure DynamicHost. The thrown exception is slightly different when running via Azure DynamicHost, but the problem is the same.
This is a critical issue, as it prevents dynamic endpoints from hosting anything.
Full Stack trace as I've been able to capture is: