<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, May 1, 2014 at 4:01 PM, MinRK <span dir="ltr"><<a href="mailto:benjaminrk@gmail.com" target="_blank">benjaminrk@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">All of those DEALER sockets should be ROUTER sockets. The DEALER behavior is correct for only one peer, but it will round-robin replies if there is more than one.</div>
</blockquote><div><br></div><div>If I change the ShellChannel to ROUTER then the kernel will no longer respond.</div><div><br></div><div>If I change the others to ROUTER, then I don't see a difference with prior behavior.</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"> Clearly some documentation is wrong. Where did you get the suggestion that they should be DEALER sockets?</div>
</blockquote><div><br></div><div>Probably a combination of finding what would work, and looking at other code (it is sometimes hard to translate code and docs between different ZMQ libraries).</div><div><br></div><div>Thank you for helping me track this down!</div>
<div><br></div><div>-Doug</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><span class="HOEnZb"><font color="#888888"><div>
<br></div><div>-MinRK</div></font></span></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, May 1, 2014 at 12:45 PM, Doug Blank <span dir="ltr"><<a href="mailto:doug.blank@gmail.com" target="_blank">doug.blank@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>On Thu, May 1, 2014 at 2:37 PM, MinRK <span dir="ltr"><<a href="mailto:benjaminrk@gmail.com" target="_blank">benjaminrk@gmail.com</a>></span> wrote:<br>
</div></div></div><div class="gmail_extra"><div class="gmail_quote"><div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr">What are your socket types on the Kernel side?</div>
</blockquote><div><br></div></div><div>Here is the definitions for our channels:</div><div><br></div><div> <span style="white-space:pre-wrap">public class ShellChannel : Channel {
</span><div><span style="white-space:pre-wrap"> </span> base(session, auth, transport, address, port, SocketType.DEALER) {</div><div> }</div><div> }</div><span style="white-space:pre-wrap"> public class IOPubChannel : Channel {
</span><div><span style="white-space:pre-wrap"> </span> base(session, auth, transport, address, port, SocketType.PUB) {<br></div><div> }</div><div> }</div><span style="white-space:pre-wrap"></span><span style="white-space:pre-wrap"> public class ControlChannel : Channel {
</span><div><span style="white-space:pre-wrap"> </span> base(session, auth, transport, address, port, SocketType.DEALER) {<br></div><div> }</div><div> }</div><span style="white-space:pre-wrap"></span><span style="white-space:pre-wrap"> public class StdInChannel : Channel {
</span><div><span style="white-space:pre-wrap"> </span> base(session, auth, transport, address, port, SocketType.DEALER) {<br></div><div> }</div><div> }</div><span style="white-space:pre-wrap"></span><span style="white-space:pre-wrap"> public class HeartBeatChannel : Channel {</span> <div>
<span style="white-space:pre-wrap"> </span> base(session, auth, transport, address, port, SocketType.REP) {<br></div><div><div> }</div><div> }</div></div></div><div><br></div><div>Could that really effect multi-frontend, but not single?</div>
<span><font color="#888888">
<div><br></div><div>-Doug</div></font></span><div><div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class="gmail_extra"><br><br><div class="gmail_quote"><div><div>On Thu, May 1, 2014 at 9:58 AM, Doug Blank <span dir="ltr"><<a href="mailto:doug.blank@gmail.com" target="_blank">doug.blank@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div><div><div dir="ltr">Devs, I have been trying to find the cause of this bug for some time, and I thought that someone might be able to provide a hint as to where to look to find the issue.<div>
<br></div><div>We have an external kernel that works very well when you connect onto it with a single frontend. But when you connect two frontends (console or notebook), then the conversation gets confused.</div>
<div><br></div><div>More detail:</div><div><br></div><div>Terminal 1:</div><div><br></div><div>ipython console --profile calico</div><div><br></div><div>works fine.</div><div><br></div><div>Terminal 2:</div><div><br></div>
<div><div>ipython console --profile calico --existing</div></div><div><br></div><div>starts, but now things are confused. Now, each terminal takes turns being able to get the prompt. If run in notebook, then code execution never signals the end of computing (the [*] never turns to a number, but you can still enter and get results back). In the console, output is received, but the prompt is in the other terminal.</div>
<div><br></div><div>It works fine with a single front end.</div><div><br></div><div>Any ideas appreciated!</div><span><font color="#888888"><div><br></div><div>-Doug</div></font></span></div>
<br></div></div>_______________________________________________<br>
IPython-dev mailing list<br>
<a href="mailto:IPython-dev@scipy.org" target="_blank">IPython-dev@scipy.org</a><br>
<a href="http://mail.scipy.org/mailman/listinfo/ipython-dev" target="_blank">http://mail.scipy.org/mailman/listinfo/ipython-dev</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
IPython-dev mailing list<br>
<a href="mailto:IPython-dev@scipy.org" target="_blank">IPython-dev@scipy.org</a><br>
<a href="http://mail.scipy.org/mailman/listinfo/ipython-dev" target="_blank">http://mail.scipy.org/mailman/listinfo/ipython-dev</a><br>
<br></blockquote></div></div></div><br></div></div>
<br>_______________________________________________<br>
IPython-dev mailing list<br>
<a href="mailto:IPython-dev@scipy.org" target="_blank">IPython-dev@scipy.org</a><br>
<a href="http://mail.scipy.org/mailman/listinfo/ipython-dev" target="_blank">http://mail.scipy.org/mailman/listinfo/ipython-dev</a><br>
<br></blockquote></div><br></div>
</div></div><br>_______________________________________________<br>
IPython-dev mailing list<br>
<a href="mailto:IPython-dev@scipy.org">IPython-dev@scipy.org</a><br>
<a href="http://mail.scipy.org/mailman/listinfo/ipython-dev" target="_blank">http://mail.scipy.org/mailman/listinfo/ipython-dev</a><br>
<br></blockquote></div><br></div></div>