Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p>However after the dispose doesn't continue like I thought it would. </p> </blockquote> <p>You mean the call to Dispose hangs/blocks? That is because you did not close the client socket before you return from the thread. (My syntax below may be wrong but you get the idea)</p> <pre><code> if (e.Errno == ETERM) { //Catch a termination error. Debug.WriteLine("Terminated! 1"); client.Close(); return; } </code></pre> <p>Setting linger to 0 is not enough - that just prevents the socket closure from blocking. You must still close the socket in your worker thread to prevent the _context.Dispose() from blocking.</p> <blockquote> <p>This is how the ZGuide says to handle destruction of the context and sockets...</p> </blockquote> <p>Well - that's true but there is an important qualifier in the document:</p> <blockquote> <p>We'll get to multithreading in the next chapter, but because some of you will, despite warnings, will try to run before you can safely walk, below is the quick and dirty guide to making a clean exit in a multithreaded ØMQ application.</p> </blockquote> <p>Later in the document they describe how to do a clean shutdown by having a dedicated socket in each thread which listens to a kill signal. Consider enhancing your worker thread by doing something similar. This way you can request each thread to shut itself down by sending each thread a message - each thread then exits its run loop, does a clean close on it's socket(s) and exits. Once all threads have exited you can safely dispose of the context without having any errors.</p>
    singulars
    1. This table or related slice is empty.
    1. POZeroMQ context destruction causes poller to ETERM but doesn't continue
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USGuido Simone
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POZeroMQ context destruction causes poller to ETERM but doesn't continue
      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
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COAwesome work. The initial problem is that my client is not closing when it should, and you have even made suggestions as to the next design pattern to use. Thank you.
      singulars
      1. PO
      1. USJason
    2. CONice description.!
      singulars
      1. PO
      1. UShims056
 

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