Hi all,

For the benefit of the list, because we thrashed this out on IRC, the
cause of this problem turned out to be creating sockets in one thread
and passing them to another.  It was an easy error to make, since the
main() has to start a queue device as a background thread, so David
put that piece into a separate thread but not the socket creation
part.

On the way I cleaned up / rewrote the code and it's here:
http://gist.github.com/572417

-Pieter

On Thu, Sep 9, 2010 at 8:25 PM, david starkweather <[email protected]> wrote:
> oh wait minute.  the last lines i don't notice.
> I only get this in testpub.c:
>
> bind to lo:4000
> create worker thread
> WORKER: ready to recieve messages
> subscribe
> MAIN: set up queue dev
> MAIN: set up fwd dev
> MAIN: wait for msg to fwd
> recieved cmd 1
> recieved nb 25
>
>
> I wonder how its forwarding on yours and not mine?
>
>
> On Thu, 2010-09-09 at 19:59 +0200, Pieter Hintjens wrote:
>> On Thu, Sep 9, 2010 at 7:17 PM, david starkweather <[email protected]> 
>> wrote:
>>
>> > Ok, managed to make minimal test case here:
>> > http://pastebin.com/apnrqk2C
>>
>> Yes, this is much simpler and easier to work with.  Thanks.
>>
>> When I run the server I get this, every single time:
>>
>> bind to lo:4000
>> create worker thread
>> subscribe
>> srv: srv.c:117: main: Assertion `rc == 0' failed.
>> Aborted (core dumped)
>>
>> Adding a sleep(1) before the connect fixes that, it's a normal
>> synchronization issue.
>>
>> Now the client says this:
>>
>> send multipart message: uint8_t | uint32_t
>> sent cmd = 1, nb = 25
>> ^C
>>
>> And the server says this:
>>
>> bind to lo:4000
>> create worker thread
>> subscribe
>> WORKER: ready to recieve messages
>> MAIN: set up queue dev
>> MAIN: set up fwd dev
>> MAIN: wait for msg to fwd
>> recieved cmd 1
>> recieved nb 25
>> MAIN:recvd msg 0
>> MAIN: send, more flag, 1
>> MAIN: wait for msg to fwd
>> MAIN:recvd msg 1
>> MAIN: send, more flag, 0
>> MAIN: wait for msg to fwd
>> ^C
>> Is this the proper (working) sequence, or is this showing the issue?
>>
>> -
>> Pieter Hintjens
>> iMatix - www.imatix.com
>> _______________________________________________
>> zeromq-dev mailing list
>> [email protected]
>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
> _______________________________________________
> zeromq-dev mailing list
> [email protected]
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
>



-- 
-
Pieter Hintjens
iMatix - www.imatix.com
_______________________________________________
zeromq-dev mailing list
[email protected]
http://lists.zeromq.org/mailman/listinfo/zeromq-dev

Reply via email to