e: 1
Date: Mon, 15 May 2017 13:39:26 +0100
From: Luca Boccassi
To: ZeroMQ development list
Subject: Re: [zeromq-dev] zeromq-dev Digest, Vol 14, Issue 7
Message-ID: <1494851966.15080.2.ca...@gmail.com>
Content-Type: text/plain; charset="utf-8"
On Mon, 2017-05-15 at 11:57 +1000,
ment list
Subject: Re: [zeromq-dev] Destroying 0MQ context gets indefinitely,
stuck/hangs despite linger=0
Message-ID: <1494499115.4886.3.ca...@gmail.com>
Content-Type: text/plain; charset="utf-8"
On Wed, 2017-05-10 at 15:21 +1000, Tomas Krajca wrote:
Hi Luca and thanks for
:58:42 +0100
From: Luca Boccassi
To: ZeroMQ development list
Cc: "develop...@repositpower.com"
Subject: Re: [zeromq-dev] Destroying 0MQ context gets indefinitely
stuck/hangs despite linger=0
Message-ID: <1494241122.11089.5.ca...@gmail.com>
Content-Type: text/plain; charset="u
was crashing with an assertion.
I am happy to do any more debugging.
Thanks in advance for any help/pointers.
--
<http://www.repositpower.com/>
*Tomas Krajca *
Software architect
m. 02 6162 0277
e. to...@repositpower.com
<https://twitter.com/RepositPower>
<https://www.facebook.com/Repo
been fixed after the first regression but it
must have somehow got back into the master at some point. Can anybody
else confirm this?
Thanks,
Tomas
On 01/29/2015 10:28 AM, Tomas Krajca wrote:
> Hi,
>
> Sorry, I didn't have time to retest it properly. Just close it and I
> will r
lose issue #1302
> <https://github.com/zeromq/libzmq/issues/1302> now?
>
> On Wed, Jan 21, 2015 at 8:13 PM, Tomas Krajca
> wrote:
>
>> >Hi Thomas,
>> >
>> >I can't reproduce the error against the latest libzmq trunk either. It
>> >must hav
>> >the hostname. However it's possible some error handling isn't right
>> >here.
>> >
>> >
>> >On Tue, Jan 20, 2015 at 5:04 AM, Tomas Krajca
>> >wrote:
>>> > >Hi Peter,
>>> > >
>>> > >It's actu
q-master) #1302
> To: ZeroMQ development list
> Cc: Mark Burgess
> Message-ID:
>
> Content-Type: text/plain; charset=UTF-8
>
> Can your C++ programmer make a minimal test case in C that reproduces
> the problem?
>
> On Mon, Jan 19, 2015 at 1:55 AM, Tomas Krajca
Hi,
I've reported this weird bug https://github.com/zeromq/libzmq/issues/1302
that we hit last week, I wonder if anybody experienced the same thing or
can reproduce it. Basically, we saw a progressive file handle leak that
crashed our application after about an hour of network outage.
Any thought
Hi Pieter,
The code should be here http://pastebin.com/9q131Ebx
Regards,
Tomas
On 10/31/2014 04:10 PM, Tomas Krajca wrote:
> Hi Pieter,
>
> I managed to quickly modify the test_metadata.cpp test in libzmq master
> to demonstrate the issue (at least I believe it demonstrates it bu
/blob/master/tests/test_metadata.cpp
with DEALER-DEALER modified to SUB-XPUB and a few other minor
modifications. I get segmentation fault on line 103 when running the test.
The original libzmq test without any modifications passes.
Thanks,
Tomas
On 10/31/2014 10:31 AM, Tomas Krajca wrote:
>
t; Today's Topics:
>
> 1. Re: Failed to unbind socket (which was bind with wild-card *)
>with real endpoint (Patryk)
> 2. zmq_msg_get('User-Id') on XPUB subscribe/unsubscribe messages
>raises Invalid argument exception (pyzmq) (Tomas Krajca)
Hi,
I am not sure whether this is a bug or just has not been implemented for
XPUB sockets. Basically, I use zmq authentication - SUB socket is my
client, XPUB is my server - and I would like to see who subscribed to my
XPUB server. When I try to get a User-Id from the subscribe/unsubscribe
mes
sts.zeromq.org>>
> *Subject:* *Re: [zeromq-dev] 0MQ-based proxy worker crashes with
> "Assertion failed: pipe (bundled/zeromq/src/session_base.cpp:441)"*
> *Reply-To:* ZeroMQ development list <mailto:zeromq-dev@lists.zeromq.org>>
>
> On Tue, Sep 16, 2014 at 12:
proxy worker might have been hitting some sort of race
condition that caused 0MQ to crash (is that possible?). Anyway, we'll keep
working on this theory.
Is there any plan for releasing libzmq 4.0.5?
Thanks,
Tomas
> On 16 Sep 2014, at 12:05 pm, Tomas Krajca wrote:
>
> Hi,
> I&
ut 12 hours, no crash yet - almost 1.000.000 successful
requests.
The annoying part is that it crashes after a long time - a few hundreds
thousands requests before it crashes is normal (hours and hours of uptime).
On Sat, Sep 13, 2014 at 12:25 PM, Tomas Krajca wrote:
> Thanks, that's
Thanks, that's a good idea, I'll give that a go on Monday.
Tomas
> On 13 Sep 2014, at 1:59 am, Martin Hurton wrote:
>
> Hi Tomas, can you please check with the master and report back? Thanks.
>
>> On Sep 9, 2014 3:44 AM, "Tomas Krajca" wrote:
>> Hi
e that you
> can get to crash? That is usually the best way to get the problem
> resolved.
>
> On Fri, Sep 12, 2014 at 8:26 AM, Tomas Krajca wrote:
>> Does anybody have any idea about the original proxy crash? The proxy did
>> about 8 requests just fine today and t
Does anybody have any idea about the original proxy crash? The proxy did about
8 requests just fine today and then it crashed with the pipe assertion
again, really weird.
Thanks,
Tomas
> On 10 Sep 2014, at 10:51 am, Tomas Krajca wrote:
>
> Thanks Justin, zurl is definitely wort
. You can
> speak to it with REQ/REP.
>
> https://github.com/fanout/zurl
>
>> On 09/08/2014 06:44 PM, Tomas Krajca wrote:
>> Hi,
>>
>> I've got a 0MQ-based proxy, clients talk 0MQ to the proxy, the proxy
>> then talks HTTP to do either a GET o
Hi,
I've got a 0MQ-based proxy, clients talk 0MQ to the proxy, the proxy then
talks HTTP to do either a GET on a specific url endpoint or a POST on a
specific endpoint (it always goes to one of these two url endpoints). I've
got a master process that has a zmq.ROUTER towards its clients (zmq.REQ)
21 matches
Mail list logo
