Thanks for your help. It was so strange I though I was just doing something fundamentally stupid. Sounds instead like I have to look a little deeper.
The consumers are registered and everything works great when using Send. If I change the line of code that sends the message to use Notify(), the message goes off into the ether and is never seen again. If I use Publish(), I get an error that says there is no subscriber. I am using Rhino queues in testing but will try MSMQ as I can then look as you suggested. Incidentially, all works great with the Notify() when the subscriber is in another process on a different bus/endpoint. I am already using DEBUG logging and need to dig a little more into what it says. I'll let you know what I find out. On Apr 16, 1:15 pm, Corey Kaylor <[email protected]> wrote: > One other thing that is required is for the consumers to be registered with > the container. If using a bootstrapper, this is done for you automatically. > If not, you must register them yourself. > > > > On Sat, Apr 16, 2011 at 12:11 PM, Corey Kaylor <[email protected]> wrote: > > This should work. If using MSMQ you should be able to see the subscription > > for the endpoint that is doing the publishing? One thing that helps is to > > set log4net configuration to DEBUG. This can tell you everything that > > happens along the way. Including the initial send of the subscription > > messages of the publisher. > > > On Sat, Apr 16, 2011 at 8:29 AM, Tom Cabanski <[email protected]> wrote: > > >> I'm confused. One particular piece of code publishes a message via notify > >> that is supposed to be (optionally) picked up by n consumers including one > >> that the application itself defines. When that consumer is in the same > >> process on the same bus as the publisher, the message never gets to the > >> consumer. When the consumer is on a different bus in a different process, > >> it works as expected. Switching the notify allows the in process consumer > >> to work properly, but does not allow for additional subscribers. Am I > >> doing > >> something wrong? Do I need to send and notify? Any suggestions? > > >> Tom Cabanski > >> Vice President of Technology > >> 5702 Kendall Hill Ln > >> Sugar Land, TX 77479 > >>832-766-5961begin_of_the_skype_highlighting 832-766-5961 end_of_the_skype_highlighting<http://www.onpointod.com> > > >> * > >> * > >> Profiles: <http://http://www.linkedin.com/in/tomcabanski> > >> LinkedIn<http://http://www.linkedin.com/in/tomcabanski> > >> Contact me: [image: Google Talk] [email protected] [image: > >> Skype]tom.cabanski > >> My blog: Developer Station > >> Revisited<http://tom.cabanski.com/2011/04/08/developer-station-revisited/> > >> [image: Twitter] <http://twitter.com/OnpointConnect> Latest Onpoint > >> tweet: I call it passive integration. Whatever the right term, we are > >> seeing more of it in the print industry.http://tinyurl.com/5ucs2ns > >> Follow @OnpointConnect <http://twitter.com/OnpointConnect> > >> <http://twitter.com/?status=@OnpointConnect%20&in_reply_to_status_id=2...> > >> Reply<http://twitter.com/?status=@OnpointConnect%20&in_reply_to_status_id=2...> > >> <http://twitter.com/?status=RT%20%40OnpointConnect%3A%20I%20call%20it%...> > >> Retweet<http://twitter.com/?status=RT%20%40OnpointConnect%3A%20I%20call%20it%...> > >> 08:07 > >> Jan-20<http://twitter.com/OnpointConnect/statuses/28091301090041856> > >> Get this email app! > >> <http://www.wisestamp.com/apps/twitter?utm_source=extension&utm_medium...> > > >> -- > >> You received this message because you are subscribed to the Google Groups > >> "Rhino Tools Dev" group. > >> To post to this group, send email to [email protected]. > >> To unsubscribe from this group, send email to > >> [email protected]. > >> For more options, visit this group at > >>http://groups.google.com/group/rhino-tools-dev?hl=en.- Hide quoted text - > > - Show quoted text - -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
