0x004e9ba7 in PyCFunction_Call ()
#7 0x005372f4 in PyEval_EvalFrameEx ()
#8 0x00540199 in ?? ()
And I can confirm that with Debian it does not hang.
Does anyone have an idea what the reason could be?
On Thu, Feb 22, 2018 at 4:49 PM, andi welchlin <andi.welch...@gmail.com>
o change to the older qpid-python client to use 0-10.
>
> Robbie
>
> On 21 February 2018 at 10:44, andi welchlin <andi.welch...@gmail.com>
> wrote:
> > I used the current broker 1.37.0 now and wanted to use proton 0.19 but
> > cmake complains that is is only tested
stop.py", line 67, in
handler._stop()
File "./clean_stop.py", line 44, in _stop
self.thread.join()
File "/usr/lib/python3.5/threading.py", line 1054, in join
self._wait_for_tstate_lock()
File "/usr/lib/python3.5/threading.py", line 1070, in
_wait_for_tstate_lock
eli
Hi Gordon,
I saw that your first line is:
#!/usr/bin/env python
Does clean_stop.py also work for you when you change it to:
#!/usr/bin/env python3
?
Regards,
Andreas
On Thu, Feb 22, 2018 at 1:14 PM, andi welchlin <andi.welch...@gmail.com>
wrote:
> I tested with Prot
Proton 0.19.0
Ubuntu 16.04 LTS with all patches installed
Python 3.5.2
I will try with Proton 0.20
On Thu, Feb 22, 2018 at 12:06 PM, Gordon Sim <g...@redhat.com> wrote:
> On 22/02/18 10:33, andi welchlin wrote:
>
>> Hello Gordon,
>>
>> I tried somthing similar, bu
Hello Gordon,
I tried somthing similar, but it hangs, anyway.
When I run your program with the changes it hangs. The output ist:
andreas:/home/andreas/src/python/test_dmitry_restart_receiver
>./test_shutdown.py
run container
press enteron start
call stop
call join
on_stop
on_stop
on_stop
nt):
print("on_disconnected")
try:
handler = AmqpReceiver()
input("press enter")
handler._stop()
except Exception as ex:
print("got EXCEPTION")
print(ex)
On Thu, Feb 22, 2018 at 9:32 AM, Gordon Sim <g...@redhat.com>
Hello all,
I tried to stop the Proton MessagingHandler by calling
self.container.stop() but this causes an endless loop (cpu goes to 100%).
So I just could help myself to throw an exception. But I think this is not
a good solution.
Can someone tell me, how I can leave container.run()
:36 PM, Gordon Sim <g...@redhat.com> wrote:
> On 21/02/18 21:33, andi welchlin wrote:
>
>> Hello all,
>>
>> I connected a Proton MessagingHandler (Python3) to a QPID C++ Broker 0.37.
>>
>> I want to close the handler gracefully but I could not manage to
Hello all,
I connected a Proton MessagingHandler (Python3) to a QPID C++ Broker 0.37.
I want to close the handler gracefully but I could not manage to do so.
When I call connection.close() the state is afterwards: LOCAL_UNINIT,
REMOTE_ACTIVE
So it does not close the remote connection (or the
proton.
Regards,
Andreas
On Wed, Feb 21, 2018 at 9:33 AM, andi welchlin <andi.welch...@gmail.com>
wrote:
> Hi Gordon, hi Chuck,
>
> thank you for the information.
>
> I tested using Proton Python clients (python3) version 0.16 and qpidd c++
> version 1.36.0.
&g
<cro...@redhat.com> wrote:
>
>
> - Original Message -
> > From: "Gordon Sim" <g...@redhat.com>
> > To: users@qpid.apache.org
> > Sent: Tuesday, February 20, 2018 3:36:37 PM
> > Subject: Re: C++ Broker Performance with large
Hello all,
I tested throughput of the Qpid C++ Broker (compiled as Release).
It was tested on a virtual machine with 15 GB RAM.
First I sent a 100 MB message into a persistent queue. From sender to
receiver it took 16 seconds for one message.
Afterwards I sent a 300 MB message, this one took
, Gordon Sim <g...@redhat.com> wrote:
> On 22/01/18 13:24, andi welchlin wrote:
>
>> Hello all,
>>
>> I want to share an exchange between two brokers (bidirectional).
>>
>> I understood that the right way to do this is using a dynamic route like:
>
Hello all,
I want to share an exchange between two brokers (bidirectional).
I understood that the right way to do this is using a dynamic route like:
qpid-route dynamic add $broker1 $broker2 $exchange_name
qpid-route dynamic add $broker2 $broker1 $exchange_name
I also want to achieve that no
> libwebsockets
> you have installed and the full cmake and build output? I will look into
> making dispatch work with the older version, or at least update the cmake
> test so dispatch won't try to build against a version that doesn't work.
>
> On Wed, Dec 6, 2017 at 5:14 AM, andi welch
Hello all,
I tried to build the QPID Dispatch Router and failed (On Ubuntu 16.04 LTS):
I used proton 0.18.1 and qpid-dispatch 1.0.0.
Running cmake seems to be fine:
---
I could do it without a key like:
qpid-route route add localhost:9001 localhost:9002 ex ''
But will this lead to defined behaviour? With a key given which is empty?
On Tue, Nov 28, 2017 at 5:19 PM, andi welchlin <andi.welch...@gmail.com>
wrote:
> Hello,
>
> I tried to create
[]
-
Cheers,
Andreas
On Tue, Nov 28, 2017 at 5:30 PM, Gordon Sim <g...@redhat.com> wrote:
> On 28/11/17 16:19, andi welchlin wrote:
>
>> Hello,
>>
>> I tried to create a route between exchanges. When I sent a message to the
>> exchan
Hello,
I tried to create a route between exchanges. When I sent a message to the
exchange on the first broker I did not get the message when I tried to read
from the second broker.
What I did is simple:
- Startet two qpid daemons one on port 9001 and one on port 9002.
- qpid-config -b
n be used only in some scenarios.
>
> I never used federation, so I cannot help with the second case.
>
> What is your use case for knowing the sender user id? Do you need it for
> some security purposes?
>
> Jakub
>
> On Tue, Nov 21, 2017 at 5:48 PM, andi welchlin <and
Hello all,
I was asking myself if the messages which go through QPID brokers are
anonymous so that you can not find out who the sender was.
I speak about AMQP 1.0.
First Case (one broker):
If a producer sends a message to a QPID broker and a consumer is receiving
it. Is it possible for the
Hello All,
I need to use a Python3 AMQP 1.0 API in order to access a Qpid C++ Broker.
So I am going for the Proton API since the Qpid Python API is only usable
with Python 2.
In the past I used the C++ Qpid API with SSL and it worked fine. There you
just had to set three environment variables
): Started
> node-03.subdomain.domain.com
>
> node-03_fence_xvm (stonith:fence_xvm): Started
> node-02.subdomain.domain.com
>
>
> Daemon Status:
>
> corosync: active/enabled
>
> pacemaker: active/enabled
>
> pcsd: active/enabled
>
>
> https://qp
change
> acl allow group1 bind exchange name=EX1
>
> Depending on your client you might be able to specify the queue name in
> more detail. For example the qpid-receive client (using the old Qpid C++
> API) would create the queue named similar to
> "EX1_8f4ea08f-d211-41c0-97cf-652
Hello everyone,
I looked into ACL documentation of Qpid C++ broker (1.36.0) and tested it a
bit.
I would like to allow for one usergroup to write to a queue with a specific
name, but deny it for all other users.
But I saw that i can not do the following:
acl allow group1 publish queue
t 12:51 PM, andi welchlin <andi.welch...@gmail.com>
wrote:
> Hi Gordon,
>
> It contains two files:
>
> qpidd.conf
> qpidd.sasldb
>
>
>
>
>
> On Fri, Nov 10, 2017 at 12:05 PM, Gordon Sim <g...@redhat.com> wrote:
>
>> On 10/11/17 10:31, andi
Hi Gordon,
It contains two files:
qpidd.conf
qpidd.sasldb
On Fri, Nov 10, 2017 at 12:05 PM, Gordon Sim <g...@redhat.com> wrote:
> On 10/11/17 10:31, andi welchlin wrote:
>
>> Hello all,
>>
>> I tried to configure SASL for Qpid C++ broker 1.36.0 but it se
Hello all,
I tried to configure SASL for Qpid C++ broker 1.36.0 but it seems like I
missed something.
What I did:
Installed Cyrus SASL.
Created a SASL database with a user "bob" using:
saslpasswd2 -f qpidd.sasldb -u QPID bob
Checked the db using sasldblistusers2 and it
> On Wed, Nov 8, 2017 at 1:18 PM, Steve Huston <shus...@riverace.com> wrote:
>
> > I have used the qpid C++ broker in clusters. On RHEL 6. Works very well.
> >
> > > -Original Message-
> > > From: andi welchlin [mailto:andi.welch...@gmail.com]
> > > Sen
Hello All,
I could solve the problem.
qpid-send is using amqp 0.10 by default but it needs to use amqp 1.0. Then
it works.
Kind Regards,
Andreas
31 matches
Mail list logo
