[zeromq-dev] Java/Windows issues

[Robin Weisberg]

So we tried pulling out from Git and we ran into some issues w/ this version
and TCP (probably not TCP related though).

First on Java/Windows we previously ran into an issue where when using one
Zmq object soon as you started publishing, receiving stopped working. We
solved this by separating out listening and sending into 2 different Zmq
objects.
Secondly, this workaround doesn't appear to work in the new version. Using 2
different zmq objects causes a crash. The crash occurs in locator.cpp line
108.

Also code that previously worked on Linux/C crashes now when binding to a
remote exchange after binding a global queue (the bindings are using
different dispatchers/locators because we had issues w/ sending and
receiving using the same dispathers/locators). The crash was:

  Broken pipe
nbytes != -1 (tcp_socket.cpp:306)
Aborted (core dumped)

Changing the code to share locators across multiple dispatchers caused the
code not to crash.

How stable should we expect head to be at this point? Is there more than
just 1.0.1 bug fixes going into it? Is there a way to get only bug fixes (a
branch or similar). It really would be nice to get a 1.0.1 version w/ just
bug fixes. At this point I'm going to go through the mail list archives and
try applying some of the key patches to the 1.0.0 version to get something
usable.

Thanks,
Robin


On Tue, Aug 11, 2009 at 3:27 AM, Pavol Malosek <malosek at fastmq.com> wrote:

>  Hello,
>
> Note that we have moved to the github lately, so clone the master zeromq1
> repository.
>
> git clone git://github.com/sustrik/zeromq1.git zeromq
>
> Docs how to build zeromq from sources can be found at
> http://www.zeromq.org/build-v06
> If you have any problem with build process we can make lin/win dist
> packages for you.
>
> malo
>
>
>
> ----- Original Message -----
> *From:* Robin Weisberg <robin at scout-trading.com>
> *To:* Pavol Malosek <malosek at fastmq.com>
> *Cc:* Martin Sustrik <sustrik at fastmq.com> ; zeromq-dev at lists.zeromq.org
> *Sent:* Tuesday, August 11, 2009 2:50 AM
> *Subject:* Re: [zeromq-dev] Java/Windows issues
>
> That's great, at this point there has been a bunch of bug fixes. Is the
> best way to get all of the fixes to check out trunk?
>
> On Mon, Aug 10, 2009 at 10:41 AM, Pavol Malosek <malosek at fastmq.com>wrote:
>
>> Hello Robin,
>>
>> The "other" issue (linux PGM sender restart detection by the win PGM
>> client) has been solved in commit 09fa91ef478ee7842622a860bf561bc1bb698487.
>> I have made few more changes the win PGM code as well so please test it
>> more carefully.
>>
>> Thanks!
>>
>> malo
>>
>>
>>  ----- Original Message ----- From: Robin Weisberg
>>> To: Pavol Malosek
>>> Cc: Martin Sustrik ; zeromq-dev at lists.zeromq.org
>>> Sent: Thursday, August 06, 2009 3:52 PM
>>> Subject: Re: [zeromq-dev] Java/Windows issues
>>>
>>>
>>> That's great, thanks!
>>>
>>> Has anyone had a chance to look at the other issue? Let me know if you
>>> have having
>>> trouble reproducing it, I can try to isolate it.
>>>
>>> Other issue was: "I have a linux c++ publisher publishing using pgm to
>>> multiple
>>> java windows clients. The linux client is registering a global exchange
>>> and the
>>> windows clients register a local queue to that exchange. It appears that
>>> after
>>> restarting the linux publisher the windows client stops receiving
>>> messages until it is also restarted."
>>> I've tested Linux to Linux w/ the same app and no issue w/ restarting.
>>> Also TCP doesn't have
>>> this issue. May be an issue w/ the windows pgm implementation.
>>>
>>
>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20090825/5c298da3/attachment.htm>