Problem solved... the Message held an instance to an NH proxied
entity. this caused a stack overflow issue when serializing the
message. I am now just passing the entity's id and loading it when
necessary.

On Jul 1, 5:20 pm, Jason Meckley <[email protected]> wrote:
> here is my scenerio. i have 3 NH listeners Post Insert/Update/Delete.
> They resolve a service from the container to actually send the
> message.
> the logic is pretty simple...
>
> if(@event.Entity is NOT a certain type) return;
> Container.Current.Resolve<AService>().DoRealWork(@event.Entity);
>
> The AService class is
> public class AService
> {
>         private readonly IServiceBus Bus;
>
>         public AService(IServiceBus bus)
>         {
>                 Bus = bus;
>         }
>
>         public void DoTheRealWork(MyEntity entity)
>         {
>                 var date = entity.Date;
>                 var item = entity.Item;
>
>                 
> log4net.LogManager.GetLogger(GetType().FullName).Error("sending
> message...");
>
>                 Bus.Send(new Message{StartOn = date, Item = item});
>
>                 
> log4net.LogManager.GetLogger(GetType().FullName).Error("message
> sent.");
>         }
>
> }
>
> pretty straight forward. However here is the problem.  the system
> "hangs" on Bus.Send();
> using the very crude logging above, only the first message is logged
> "sending message". The second message "message sent" is never logged.
>
> i register my consumers and IBusConfigurationAware before adding the
> facility. the IBusConfigurationAware registers a NH module to manage
> session.
>
> finally, I'm using rhino queues, not msmq.
>
> I'm stumped on this one.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to