Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>So I know enough about what happened to throw out an "Answer".</p> <p>When I setup my NServiceBus self hosting I had a call that loaded the message handlers.</p> <pre><code>NServiceBus.Configure.With().LoadMessageHandlers() </code></pre> <p>(There are more configurations, but I omitted them for brevity)</p> <p>When you call this, NServiceBus scans the assmeblies for a class that implements <code>IHandleMessages&lt;T&gt;</code>.</p> <p>So, somehow, on my Test Environment Machine, the ServiceBus scan of the directory for a class that calls IHandleMessages was failing to find my class (even though the assembly was absolutely there).</p> <p>Turns out that if NServiceBus does not find something that handles a message it will <strong>THROW IT AWAY</strong>!!!</p> <p>This is a total <strong>design bug</strong> in my opinion. The whole idea of NServiceBus is to not lose your data, but in this case it does just that!</p> <p>Now, once you know about this pitfall, there are several ways around it.</p> <ol> <li><p>Expressly state what your handler(s) should be:</p> <p><code>NServiceBus.Configure.With().LoadMessageHandlers&lt;First&lt;MyMessageType&gt;&gt;()</code></p></li> <li><p>Even further protection is to add another handler that will handle "Everything else". <code>IMessage</code> is the base for all message payloads, so if you put a handler on it, it will pickup everything.<br> If you set IMessage to <a href="http://docs.particular.net/nservicebus/handlers/handler-ordering" rel="nofollow">handle after</a> your messages get handled, then it will handle everything that NServiceBus can't find a handler for. If you throw and exception in that <code>Handle</code> method that will cause NServiceBus to to move the message to the <code>error</code> queue. (What I think should be the <strong>default</strong> behavior.)</p></li> </ol>
    singulars
    1. This table or related slice is empty.
    1. POSomething making NServiceBus lose messages
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USPeter
    1. USVaccano
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POSomething making NServiceBus lose messages
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COWas your work around to state all your message handlers there or just one in the message handling assembly?
      singulars
      1. PO
      1. USGalen
    2. CO@Galen - I have only one message handler. And I explicitly state what it is in my config now.
      singulars
      1. PO
      1. USVaccano
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload