c# - NServiceBus message removed from queue w/o a trace -


i created new nservicebus azure worker role.

the configuration simply:

nservicebus.configure.with(busassemblies)                         .log4net()                         .license(config.default.nservicebus_license)                         .defineendpointname(endpointname)                          .unitybuilder(servicebusdiconfiguration.container)                         .azureconfigurationsource()                         .azuresagapersister()                         .azuresubcriptionstorage()                         .azuredatabus()                         .jsonserializer()                         .azureservicebusmessagequeue()                         .unicastbus()                         .loadmessagehandlers()                         .createbus()                         .start() 

the client configuration identical above except addition call .donotautosubscribe(). client uses bus.send(message) input queue of listener.

azure bus queue reported messages being sent input queue , removed accordingly (with listeners running - , not otherwise). yes- messages being removed queue. handlers not being fired, , there no error message in either event viewers or console (when using dev fabric).

enter image description here

the error , don't think it's relevant because it's not being logged @ time message removed queue - rather logging @ start time, error follow:

[monagenthost] error: ma event: 2013-05-12t22:52:54.925z [monagenthost] error:     2 [monagenthost] error:     12084 [monagenthost] error:     6180 [monagenthost] error:     nettransport [monagenthost] error:     0 [monagenthost] error:     880e569e-d37b-4262-bdae-dbe5133 [monagenthost] error:     netutils.cpp [monagenthost] error:     openhttpsession [monagenthost] error:     749 [monagenthost] error:     0 [monagenthost] error:     2f94 [monagenthost] error:      [monagenthost] error:     winhttpgetproxyforurl(http://127.0.0.1) failed error_winhttp_autodetection_failed (12180) 

this driving me crazy. can't believe designed api complicated , opaque - makes windows complication foundation seems trivial in comparison. please me figure out went wrong, hint appreciated, eg. in file/folder error logs work too!

thanks!

i had same problem recently, there issue azureservicebus transport when define own endpoint name , host locally (not in azure worker role) not work. has been fixed yves used workaround specify full endpoint name (including service url) in app.config section azure servicebus transport.

  <configsections> <section name="unicastbusconfig" type="nservicebus.config.unicastbusconfig, nservicebus.core" /> <section name="azureservicebusqueueconfig" type="nservicebus.config.azureservicebusqueueconfig, nservicebus.azure" /> <section name="messageforwardingincaseoffaultconfig" type="nservicebus.config.messageforwardingincaseoffaultconfig, nservicebus.core" /> <section name="logging" type="nservicebus.config.logging, nservicebus.core" />   </configsections>   <azureservicebusqueueconfig queuename="myendpoint@mynamespace.servicebus.windows.net" connectionstring="endpoint=sb://mynamespace.servicebus.windows.net/;sharedsecretissuer=owner;sharedsecretvalue=mysecret" /> 

Comments

Popular posts from this blog

php - cannot display multiple markers in google maps v3 from traceroute result -

c# - DetailsView in ASP.Net - How to add another column on the side/add a control in each row? -

javascript - firefox memory leak -