Comments (6)
more info
2014-03-19 10:32:46.854 +10:00 [Debug] Constructing bus...
2014-03-19 10:32:46.879 +10:00 [Debug] Creating message pumps and subscriptions.
2014-03-19 10:32:46.892 +10:00 [Debug] Creating command message pumps
2014-03-19 10:32:46.893 +10:00 [Debug] Creating message pump for command type "ConvertToPDFCommand"
2014-03-19 10:32:46.904 +10:00 [Debug] Creating request message pumps
2014-03-19 10:32:46.907 +10:00 [Debug] Creating multicast request message pumps
2014-03-19 10:32:46.909 +10:00 [Debug] Creating multicast event message pumps
2014-03-19 10:32:46.912 +10:00 [Debug] Creating competing event message pumps
2014-03-19 10:32:46.912 +10:00 [Debug] Message pumps and subscriptions are all created.
2014-03-19 10:32:46.914 +10:00 [Debug] Bus built. Job done!
2014-03-19 10:32:46.925 +10:00 [Debug] Bus starting...
2014-03-19 10:32:46.937 +10:00 [Debug] Message pump for "inputqueue.order.endpoint.MACHINENAME" starting...
2014-03-19 10:32:46.937 +10:00 [Debug] Message pump for "q.pdf.messages.converttopdfcommand" starting...
2014-03-19 10:32:46.959 +10:00 [Debug] Fetching existing queues...
2014-03-19 10:32:48.302 +10:00 [Debug] Message pump for "inputqueue.order.endpoint.MACHINENAME" started
2014-03-19 10:32:48.348 +10:00 [Debug] Dispatching message: "Microsoft.ServiceBus.Messaging.BrokeredMessage{MessageId:1d3cd07401ba48fc9f2db2acb879854a}" from null
from nimbus.
OK, so what I've determined so far (and enough to implement a work-around):
We're using Nancy+Autofac. Configuration happens in the bootstrapper, but doesn't activate. The first handler has a bus dependency so nimbus was activating during a nancy request. Not sure what was at play there, but I found that by resolving IBus straight after the container initialisation caused everything to work just fine.
from nimbus.
Something I have done with autofac is register the bus as follow
builder.RegisterNimbus(handlerTypesProvider);
builder.Register(componentContext => new BusBuilder()
.Configure()
.WithConnectionString(connectionString)
.WithNames("MyApp", Environment.MachineName)
.WithTypesFrom(handlerTypesProvider)
.WithAutofacDefaults(componentContext)
.Build())
.As<IBus>()
.AsSelf()
.SingleInstance();
and on service / application start call container.Resolve<Bus>().Start()
this has another nice affect doing any convention tests (can all message types resolve from the container) doesn't start the bus.
from nimbus.
Yeah cheers. Our solution was pretty much similar :)
from nimbus.
@lukeschafer Were you calling Start or Autoactivate on the bus as part of your container configuration like we do here ? If you did that and it's not starting automatically that's a worry.
from nimbus.
Yeah we were using auto activate.
On 29/03/2014 11:13 AM, "Damian Maclennan" [email protected] wrote:
@lukeschafer https://github.com/lukeschafer Were you calling Start or
Autoactivate on the bus as part of your container configuration like we
do herehttp://nimbusapi.github.io/doc/Configuring-Nimbus-With-Autofac.html? If you did that and it's not starting automatically that's a worry.Reply to this email directly or view it on GitHubhttps://github.com//issues/61#issuecomment-38982506
.
from nimbus.
Related Issues (20)
- (Non-)reliable Azure/WSB messaging in V3 HOT 5
- MessageIds do not correlate between producers and subscribers HOT 1
- When does it really make sense to use a project like Nimbus vs Hangfire? HOT 1
- Question: Are there any plans on supporting creating partitioned azure queues? HOT 1
- Protobuf serializer needs to support NimbusMessage
- BusEventSender.Publish() swallowing exceptions - how does OutboundInterceptor.OnEventPublishingError work? HOT 1
- HeartBeat messages HOT 1
- Memory leak in Nimbus.Infrastructure.Dispatching.SubsequentDispatchContext HOT 1
- MessageLoggingExtensions throws exception on formatting output on any ILogger implementation HOT 2
- NuGet packages from myget.org only shows 50 latest versions HOT 1
- Incorrect expiry of RequestResponseCorrelationWrapper
- DendencyResolutionException: No registration for type Nimbus.Transports.WindowsServiceBus.Filtering.ISqlFilterExpressionGenerator
- Event subscription naming does not use fully-qualified handler type name HOT 9
- Porting Nimbus to Netstandard 2.0 (.NET Core & .NET 4.6.2) HOT 1
- Nimbus.Transports.WindowsServiceBus nuget package introduces FodyWeavers.xml file into target project
- Release dotnet core HOT 2
- AMQP Transport HOT 3
- Required permissions HOT 1
- Azure Service Bus subscriptions not reconnecting
- ASB: First time deployments of new subscriptions failing
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from nimbus.