Yes, this epic journey can come to an end!
the short answer:
I was no starting the one-way bus when the application started. I was
waiting until the first time the bus was needed.
the long answer:
when the bus was resolved JIT the esent database was created under the
current user's identity. This wasn't an issue with two-way bus because I
would use a bootstrapper and the bootstrapper started the bus automatically.
By resolving the one-way bus when the web site starts it will automatically
create the bus under the IIS account, rather than a user's account.
so the resolution is simple
public class InfrastructureInstaller : IWindsorInstaller
{
public void Install(IWindsorContainer container, IConfigurationStore
store)
{
//resolving the container calls RhinoQueuesTransport.Start()
which will properly create the esent database
container
.AddFacility<OnewayRhinoServiceBusFacility>("one.way.bus");
.Resolve<IOnewayBus>();
}
}
Thank you to all who helped on this issue.
@Mike, thanks for pointing out the configurable port on one-way bus. while
it wasn't a problem on this project, it would be on my next project. That is
now a nightmare avoided.
--
You received this message because you are subscribed to the Google Groups
"Rhino Tools Dev" group.
To post to this group, send email to rhino-tools-dev@googlegroups.com.
To unsubscribe from this group, send email to
rhino-tools-dev+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/rhino-tools-dev?hl=en.
