Re: [VOTE] Release Apache Qpid Proton-J 0.26.0

[Timothy Bish]

+1

* Validated signatures and checksums
* Checked for license and notice files in binary and source archives
* Ran mvn apache-rat:check to validate source files have licenses
* Built from source and ran the tests
* Build ActiveMQ, ActiveMQ Artemis and Qpid JMS using the staged bits 
and ran the AMQP tests


On 02/22/2018 01:39 PM, Robbie Gemmell wrote:

Hi folks,

I have put together a spin for a Qpid Proton-J 0.26.0 release, please
test it and vote accordingly.

The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.26.0-rc1/

The maven artifacts are staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1130

The JIRAs assigned are:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12342429

Regards,
Robbie

P.S. If you want to test things out using maven with your own build
you can temporarily add this to your poms to access the staging repo:

   
 
   staging
   
https://repository.apache.org/content/repositories/orgapacheqpid-1130
 
   

The dependency for proton-j would then be:

   
 org.apache.qpid
 proton-j
 0.26.0
   

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org




--
Tim Bish
twitter: @tabish121
blog: http://timbish.blogspot.com/


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

[VOTE] Release Apache Qpid Proton-J 0.26.0

[Robbie Gemmell]

Hi folks,

I have put together a spin for a Qpid Proton-J 0.26.0 release, please
test it and vote accordingly.

The source and binary archives can be grabbed from:
https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.26.0-rc1/

The maven artifacts are staged for now at:
https://repository.apache.org/content/repositories/orgapacheqpid-1130

The JIRAs assigned are:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12313720=12342429

Regards,
Robbie

P.S. If you want to test things out using maven with your own build
you can temporarily add this to your poms to access the staging repo:

  

  staging
  
https://repository.apache.org/content/repositories/orgapacheqpid-1130

  

The dependency for proton-j would then be:

  
org.apache.qpid
proton-j
0.26.0
  

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

RE: JMS JNDI destination

[Cyril Micoud]

Hi all,

Can you provide me an example...

On my side I got:

2018-02-22 18:24:01,288 WARN  - Open of resource:(JmsConsumerInfo: { 
ID:14d11742-f82d-4ca6-8568-d0b173feb6ca:1:1:1, destination = topic }) failed: 
Could not find destination for source 
'Source{address=topic,durable=none,expiryPolicy=link-detach,dynamic=false,defaultOutcome=Modified{deliveryFailed=true},outcomes=[amqp:accepted:list,
 amqp:released:list, amqp:rejected:list],capabilities=[topic]}' [condition = 
amqp:not-found] - 
[org.apache.qpid.jms.provider.amqp.builders.AmqpResourceBuilder#handleClosed:196]
 
[SERVER] Caught exception, exiting.
javax.jms.InvalidDestinationException: Could not find destination for source 
'Source{address=topic,durable=none,expiryPolicy=link-detach,dynamic=false,defaultOutcome=Modified{deliveryFailed=true},outcomes=[amqp:accepted:list,
 amqp:released:list, amqp:rejected:list],capabilities=[topic]}' [condition = 
amqp:not-found]
at 
org.apache.qpid.jms.provider.amqp.AmqpSupport.convertToException(AmqpSupport.java:150)
at 
org.apache.qpid.jms.provider.amqp.AmqpSupport.convertToException(AmqpSupport.java:117)

Best regards,

Cyril

-Message d'origine-
De : Jan Bares, WOOD & Co. [mailto:jan.ba...@wood.cz] 
Envoyé : mercredi 24 janvier 2018 15:05
À : users@qpid.apache.org
Objet : RE: JMS JNDI destination



> -Original Message-
> From: Gordon Sim [mailto:g...@redhat.com]
> Sent: Tuesday, January 23, 2018 6:55 PM
> To: users@qpid.apache.org
> Subject: Re: JMS JNDI destination
>
> On 23/01/18 17:37, Jan Bares, WOOD & Co. wrote:
> > I want to send a message via direct Exchange and routing key, it's 
> > not clear
> what I should write in jndi.properties and how I can get the 
> destination in code? The examples apparently send directly to the 
> queue. Using JMS client 0.28.
>
> With the c++ broker at present, you have to set the exchange name as 
> the destination (probably a topic makes sense, but this may not 
> matter), and then set the subject on the message to be the routing 
> key. With the JMS client I believe you can set the subject through the 
> setJMSType() method.

Thank you Gordon, it works, topic must be used.

Kind regards, Jan


Jan Bares
Calypso / Java Lead Developer

Hradecka 10
Czech Republic
Mobile: +420 776 333 676

In association with
WOOD & Company Financial Services, a.s.
http://www.wood.cz



DISCLAIMER

 WOOD & Company Financial Services, a.s. and its branches are 
authorized and regulated by the CNB as Home State regulator and in Poland by 
the KNF, in Slovakia by the NBS, in Italy by the CONSOB and in the UK by the 
FCA as Host State regulators. For further information about WOOD & Co., its 
investment services, financial instruments and associated risks, safeguard 
client assets (incl. compensation schemes) and contractual relationship please 
see our website at www.wood.com under section Corporate 
Governance.
 Unless otherwise stated, this transmission is neither an offer nor the 
solicitation of an offer to sell or purchase any investment. All estimates, 
opinions and other information contained herein are subject to change without 
notice and are provided in good faith but without legal responsibility or 
liability. Opinion may be personal to the author and may not reflect the 
opinions of WOOD & Co. Communications from sales persons, sales traders or 
traders should not be regarded as investment research and may contain opinions 
or trading ideas which are different from WOOD & Co. investment research 
opinions.
 This e-mail and any attachments are confidential and may be privileged 
or otherwise protected from disclosure. If you are not a named addressee you 
must not use, disclose, distribute, copy, print or rely on this e-mail and any 
of its attachments. Please notify the sender that you have received this email 
by mistake by replying to the email, and then delete the email and any copies 
of it. Although WOOD & Co. routinely screens e-mails for viruses, addressees 
should scan this e-mail and any attachments for viruses. WOOD & Co. makes no 
representation or warranty as to the absence of viruses in this e-mail or any 
attachments. Please note that to ensure regulatory compliance and for the 
protection of our clients and business, we may monitor and read e-mails sent to 
and from our server(s).

B CB  [  
X  ܚX KK[XZ[
 \ \  ][  X  ܚX P\Y
 \X K ܙ B  ܈Y][ۘ[  [X[  K[XZ[
 \ \  Z[\Y
 \X K ܙ B B

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: C++ Broker Performance with large messages

[andi welchlin]

Thank you for the hints.

I can confirm that the throughput is far better with QPID Proton 0.20 (and
the C++ Broker 0.37).

The new results are:
15 seconds for a 300 MB message
23 seconds for a 500 MB message
47 seconds for a 800 MB message

(all numbers are averages)

Kind Regards,
Andreas


On Wed, Feb 21, 2018 at 11:57 AM, Robbie Gemmell 
wrote:

> The warning is mainly just the result that Proton 0.19.0 was released
> after qpid-cpp 1.37.0 was. They were verified together when 0.19.0 was
> released, and I dont think there is any known issue using them
> together. Given the latter is released less often that warning should
> probably be made less alarming, its been there since the early days of
> Proton when it was actually useful to know.
>
> You cant make Proton talk AMQP 0-10, it only supports AMQP 1.0. You
> would have to change to the older qpid-python client to use 0-10.
>
> Robbie
>
> On 21 February 2018 at 10:44, andi welchlin 
> 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 with 0.18.1.
> >
> > So I tried this and the results became worse than with 1.36.0 / 0.16.
> Now a
> > 300 MB message takes about 151 seconds, before it was 126.
> >
> > AMQP 1.0 is used
> >
> > Since you mentioned it could be a problem with AMQP 1.0 I would like to
> > switch to AMQP 0.10.
> >
> > I am using Python and connect like this within the MessagingHandler:
> >
> > self.conn = self.container.connect(self.host, reconnect = False)
> >
> > How can I switch the protocol to 0.10? I did not find an example how to
> do
> > this with qpid proton.
> >
> > Regards,
> > Andreas
> >
> >
> >
> >
> >
> >
> > On Wed, Feb 21, 2018 at 9:33 AM, andi welchlin 
> > 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.
> >>
> >> I will take the newest versions of both and retest. Will come back with
> >> the results.
> >>
> >> Thank you,
> >> Andreas
> >>
> >>
> >> On Tue, Feb 20, 2018 at 10:15 PM, Chuck Rolke 
> wrote:
> >>
> >>>
> >>>
> >>> - Original Message -
> >>> > From: "Gordon Sim" 
> >>> > To: users@qpid.apache.org
> >>> > Sent: Tuesday, February 20, 2018 3:36:37 PM
> >>> > Subject: Re: C++ Broker Performance with large messages
> >>> >
> >>> > On 20/02/18 16:51, andi welchlin wrote:
> >>> > > 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 125 seconds. So
> >>> this is
> >>> > > not 3 times more (as I would have expected but 7,5 times more).
> >>> > >
> >>> > > Any suggestions how to improve throughput?
> >>> > >
> >>> > > Do you have an idea why 300 MB is 7,5 times slower than 100 MB?
> >>> >
> >>> > Is this over AMQP 1.0? Also what clients have you tested with and is
> >>> > there any differences there?
> >>> >
> >>>
> >>> Some AMQP 1.0 qpid-proton -based sending clients before 0.19 suffered
> >>> from large
> >>> output buffer issues. See https://issues.apache.org/jira
> >>> /browse/PROTON-1687
> >>> and related issues.
> >>>
> >>> >
> >>> > 
> -
> >>> > To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> >>> > For additional commands, e-mail: users-h...@qpid.apache.org
> >>> >
> >>> >
> >>>
> >>> -
> >>> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> >>> For additional commands, e-mail: users-h...@qpid.apache.org
> >>>
> >>>
> >>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: QPID Proton 0.19 Python: Exit MessagingHandler.run()

[andi welchlin]

My output with tracing:

run container
on start
press enter[0x7f2f6c008f90]:  -> SASL
[0x7f2f6c008f90]:  <- SASL
[0x7f2f6c008f90]:0 <- @sasl-mechanisms(64)
[sasl-server-mechanisms=@PN_SYMBOL[:ANONYMOUS, :AMQPLAIN, :PLAIN]]
[0x7f2f6c008f90]:0 -> @sasl-init(65) [mechanism=:ANONYMOUS,
initial-response=b"anonymous"]
[0x7f2f6c008f90]:0 <- @sasl-outcome(68) [code=0]
[0x7f2f6c008f90]:  -> AMQP
[0x7f2f6c008f90]:0 -> @open(16)
[container-id="7c856344-8010-44dc-ac56-bbdcddb52acd",
hostname="localhost:amqp", channel-max=32767]
[0x7f2f6c008f90]:0 -> @begin(17) [next-outgoing-id=0,
incoming-window=2147483647, outgoing-window=2147483647]
[0x7f2f6c008f90]:0 -> @attach(18)
[name="7c856344-8010-44dc-ac56-bbdcddb52acd-test.awe.queue", handle=0,
role=true, snd-settle-mode=2, rcv-settle-mode=0, source=@source(40)
[address="test.awe.queue", durable=0, timeout=0, dynamic=false],
target=@target(41) [durable=0, timeout=0, dynamic=false],
initial-delivery-count=0]
[0x7f2f6c008f90]:0 -> @flow(19) [incoming-window=2147483647,
next-outgoing-id=0, outgoing-window=2147483647, handle=0, delivery-count=0,
link-credit=50, drain=false]
[0x7f2f6c008f90]:  <- AMQP
[0x7f2f6c008f90]:0 <- @open(16) [container-id="rabbit@andreas-VirtualBox",
channel-max=32767, idle-time-out=6,
properties={:"cluster_name"="rabbit@andreas-VirtualBox",
:copyright="Copyright (C) 2007-2015 Pivotal Software, Inc.",
:information="Licensed under the MPL.  See http://www.rabbitmq.com/;,
:platform="Erlang/OTP", :product="RabbitMQ", :version="3.5.7"}]
[0x7f2f6c008f90]:0 <- @begin(17) [remote-channel=0, next-outgoing-id=0,
incoming-window=65535, outgoing-window=65535, handle-max=4294967295]
[0x7f2f6c008f90]:0 <- @attach(18)
[name="7c856344-8010-44dc-ac56-bbdcddb52acd-test.awe.queue", handle=0,
role=false, snd-settle-mode=0, rcv-settle-mode=0, source=@source(40)
[address="test.awe.queue", durable=0, timeout=0, dynamic=false,
default-outcome=@released(38) [],
outcomes=@PN_SYMBOL[:"amqp:accepted:list", :"amqp:rejected:list",
:"amqp:released:list"]], initial-delivery-count=0]
*[0x7f2f6c008f90]:0 <- @flow(19) [next-incoming-id=0,
incoming-window=65535, next-outgoing-id=0, outgoing-window=65535, handle=0,
delivery-count=0, link-credit=50, available=0, drain=false]*

call stop
call join
on_stop
on_stop
on_stop
on_stop
 [ a log of stop lines deleted ] ...
on_stop
on_stop
on_stop
on_stop
Exception ignored in: 
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/proton/wrapper.py", line 95, in
__del__
pn_decref(self._impl)
  File "/usr/lib/python3/dist-packages/proton/wrapper.py", line 63, in
__getattr__
attrs = self.__dict__["_attrs"]
KeyError: ('_attrs',)
^CTraceback (most recent call last):
  File "./clean_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
elif lock.acquire(block, timeout):
KeyboardInterrupt


On Thu, Feb 22, 2018 at 4:26 PM, Gordon Sim  wrote:

> On 22/02/18 15:22, andi welchlin wrote:
>
>> 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
>>
>> ?
>>
>>
> Yes (output with tracing on below):
>
> $ PN_TRACE_FRM=1 ./clean_stop.py run container
>> press enteron start
>> [0x7f39ac009120]:  -> SASL
>> [0x7f39ac009120]:  <- SASL
>> [0x7f39ac009120]:0 <- @sasl-mechanisms(64) [sasl-server-mechanisms=@PN_SY
>> MBOL[:ANONYMOUS]]
>> [0x7f39ac009120]:0 -> @sasl-init(65) [mechanism=:ANONYMOUS,
>> initial-response=b"anonymous@localhost.localdomain"]
>> [0x7f39ac009120]:0 <- @sasl-outcome(68) [code=0]
>> [0x7f39ac009120]:  -> AMQP
>> [0x7f39ac009120]:0 -> @open(16) 
>> [container-id="dc3bcfe2-23b0-47d0-bcaa-848d290b347c",
>> hostname="localhost", channel-max=32767]
>> [0x7f39ac009120]:0 -> @begin(17) [next-outgoing-id=0, incoming-window=
>> 2147483647, outgoing-window=2147483647]
>> [0x7f39ac009120]:0 -> @attach(18) 
>> [name="dc3bcfe2-23b0-47d0-bcaa-848d290b347c-test.awe.queue",
>> handle=0, role=true, snd-settle-mode=2, rcv-settle-mode=0,
>> source=@source(40) [address="test.awe.queue", durable=0, timeout=0,
>> dynamic=false], target=@target(41) [durable=0, timeout=0, dynamic=false],
>> initial-delivery-count=0, max-message-size=0]
>> [0x7f39ac009120]:0 -> @flow(19) [incoming-window=2147483647,
>> next-outgoing-id=0, outgoing-window=2147483647, handle=0,
>> delivery-count=0, link-credit=50, drain=false]
>> [0x7f39ac009120]:  <- AMQP
>> [0x7f39ac009120]:0 <- @open(16) [container-id="Router.A",
>> max-frame-size=16384, channel-max=32767, idle-time-out=8000,
>> offered-capabilities=:"ANONYMOUS-RELAY", 
>> properties={:product="qpid-dispatch-router",
>> :version="1.0.0"}]
>> [0x7f39ac009120]:0 <- @begin(17) [remote-channel=0, next-outgoing-id=0,
>> 

Re: QPID Proton 0.19 Python: Exit MessagingHandler.run()

[Gordon Sim]

On 22/02/18 15:22, andi welchlin wrote:

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

?



Yes (output with tracing on below):

$ PN_TRACE_FRM=1 ./clean_stop.py 
run container

press enteron start
[0x7f39ac009120]:  -> SASL
[0x7f39ac009120]:  <- SASL
[0x7f39ac009120]:0 <- @sasl-mechanisms(64) 
[sasl-server-mechanisms=@PN_SYMBOL[:ANONYMOUS]]
[0x7f39ac009120]:0 -> @sasl-init(65) [mechanism=:ANONYMOUS, 
initial-response=b"anonymous@localhost.localdomain"]
[0x7f39ac009120]:0 <- @sasl-outcome(68) [code=0]
[0x7f39ac009120]:  -> AMQP
[0x7f39ac009120]:0 -> @open(16) [container-id="dc3bcfe2-23b0-47d0-bcaa-848d290b347c", 
hostname="localhost", channel-max=32767]
[0x7f39ac009120]:0 -> @begin(17) [next-outgoing-id=0, 
incoming-window=2147483647, outgoing-window=2147483647]
[0x7f39ac009120]:0 -> @attach(18) 
[name="dc3bcfe2-23b0-47d0-bcaa-848d290b347c-test.awe.queue", handle=0, role=true, 
snd-settle-mode=2, rcv-settle-mode=0, source=@source(40) [address="test.awe.queue", 
durable=0, timeout=0, dynamic=false], target=@target(41) [durable=0, timeout=0, dynamic=false], 
initial-delivery-count=0, max-message-size=0]
[0x7f39ac009120]:0 -> @flow(19) [incoming-window=2147483647, 
next-outgoing-id=0, outgoing-window=2147483647, handle=0, delivery-count=0, 
link-credit=50, drain=false]
[0x7f39ac009120]:  <- AMQP
[0x7f39ac009120]:0 <- @open(16) [container-id="Router.A", max-frame-size=16384, channel-max=32767, 
idle-time-out=8000, offered-capabilities=:"ANONYMOUS-RELAY", 
properties={:product="qpid-dispatch-router", :version="1.0.0"}]
[0x7f39ac009120]:0 <- @begin(17) [remote-channel=0, next-outgoing-id=0, 
incoming-window=2147483647, outgoing-window=2147483647]
[0x7f39ac009120]:0 <- @attach(18) 
[name="dc3bcfe2-23b0-47d0-bcaa-848d290b347c-test.awe.queue", handle=0, role=false, 
snd-settle-mode=2, rcv-settle-mode=0, source=@source(40) [address="test.awe.queue", 
durable=0, timeout=0, dynamic=false], target=@target(41) [durable=0, timeout=0, dynamic=false], 
initial-delivery-count=0, max-message-size=0]

call stop
call join
on_stop
after container.run()
done stop



-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: QPID Proton 0.19 Python: Exit MessagingHandler.run()

[andi welchlin]

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 
wrote:

> I tested with Proton 0.20.0 and it is still the same.
>
> On Thu, Feb 22, 2018 at 12:43 PM, andi welchlin 
> wrote:
>
>> 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  wrote:
>>
>>> On 22/02/18 10:33, andi welchlin wrote:
>>>
 Hello Gordon,

 I tried somthing similar, but it hangs, anyway.

 When I run your program with the changes it hangs.

>>>
>>> What platform are you on? (It works for me with python 3.5.4 on fedora
>>> 25 with latest python-qpid-proton).
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
>>> For additional commands, e-mail: users-h...@qpid.apache.org
>>>
>>>
>>
>

Re: [VOTE] Release Qpid Dispatch Router 1.0.1 (RC1)

[Robbie Gemmell]

https://issues.apache.org/jira/browse/DISPATCH-893 should probably
have been included too. I overlooked it on an earlier skim as it was
resolved without a fix version assigned.

More of a reason for a 1.0.2 or ensuring 1.1.0 isnt too distant,
rather than cause for a respin.

Robbie

On 22 February 2018 at 11:37, Robbie Gemmell  wrote:
> +1
>
> I checked things over as follows:
>  - Verified the signature and checksum files.
>  - Checked LICENCE+NOTICE files present.
>  - Ran mvn apache-rat:check to check the licence headers.
>  - Built the router on Fedora 26 against an install of Proton 0.20.0
> and ran the tests.
>  - Ran the JMS client examples against the router.
>  - Built the router on Fedora 27 against Proton 0.18.1.
>
> Robbie
>
> On 20 February 2018 at 20:27, Ted Ross  wrote:
>> Please vote on this thread to release qpid-dispatch 1.0.1-rc1 as the
>> official 1.0.1.
>>
>> The release can be found here:
>>
>> https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.0.1-rc1/
>>
>> The following defects were fixed in this release:
>>
>> DISPATCH-874 - unable to load .json or .woff2 files from local
>> file system from http port
>> DISPATCH-881 - Inbound pre-settled messages causes memory leak of 
>> deliveries
>> DISPATCH-882 - router buffers messages for slow presettled receiver
>> DISPATCH-883 - Router crashes when it processes management request
>> for connections
>> DISPATCH-887 - Dispatch reestablishes connection inspite of
>> deleting the connector
>> DISPATCH-889 - linkRoute patterns beginning with #/string match
>> substrings after the /
>> DISPATCH-895 - qpid-dispatch crashes with a SEGFAULT in libqpid-proton
>> DISPATCH-900 - Memory leak when repeatedly opening and closing 
>> connections
>> DISPATCH-908 - Router loses dispositions over receive link on
>> qpid-interop-test 2-node test
>> DISPATCH-914 - qd_connector_t leaks mutexes
>> DISPATCH-920 - Enabled policy blocks inter-router links
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
>> For additional commands, e-mail: users-h...@qpid.apache.org
>>

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: QPID Proton 0.19 Python: Exit MessagingHandler.run()

[andi welchlin]

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  wrote:

> On 22/02/18 10:33, andi welchlin wrote:
>
>> Hello Gordon,
>>
>> I tried somthing similar, but it hangs, anyway.
>>
>> When I run your program with the changes it hangs.
>>
>
> What platform are you on? (It works for me with python 3.5.4 on fedora 25
> with latest python-qpid-proton).
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: [VOTE] Release Qpid Dispatch Router 1.0.1 (RC1)

[Robbie Gemmell]

+1

I checked things over as follows:
 - Verified the signature and checksum files.
 - Checked LICENCE+NOTICE files present.
 - Ran mvn apache-rat:check to check the licence headers.
 - Built the router on Fedora 26 against an install of Proton 0.20.0
and ran the tests.
 - Ran the JMS client examples against the router.
 - Built the router on Fedora 27 against Proton 0.18.1.

Robbie

On 20 February 2018 at 20:27, Ted Ross  wrote:
> Please vote on this thread to release qpid-dispatch 1.0.1-rc1 as the
> official 1.0.1.
>
> The release can be found here:
>
> https://dist.apache.org/repos/dist/dev/qpid/dispatch/1.0.1-rc1/
>
> The following defects were fixed in this release:
>
> DISPATCH-874 - unable to load .json or .woff2 files from local
> file system from http port
> DISPATCH-881 - Inbound pre-settled messages causes memory leak of 
> deliveries
> DISPATCH-882 - router buffers messages for slow presettled receiver
> DISPATCH-883 - Router crashes when it processes management request
> for connections
> DISPATCH-887 - Dispatch reestablishes connection inspite of
> deleting the connector
> DISPATCH-889 - linkRoute patterns beginning with #/string match
> substrings after the /
> DISPATCH-895 - qpid-dispatch crashes with a SEGFAULT in libqpid-proton
> DISPATCH-900 - Memory leak when repeatedly opening and closing connections
> DISPATCH-908 - Router loses dispositions over receive link on
> qpid-interop-test 2-node test
> DISPATCH-914 - qd_connector_t leaks mutexes
> DISPATCH-920 - Enabled policy blocks inter-router links
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: QPID Proton 0.19 Python: Exit MessagingHandler.run()

[Gordon Sim]

On 22/02/18 10:33, andi welchlin wrote:

Hello Gordon,

I tried somthing similar, but it hangs, anyway.

When I run your program with the changes it hangs.


What platform are you on? (It works for me with python 3.5.4 on fedora 
25 with latest python-qpid-proton).


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: QPID Proton 0.19 Python: Exit MessagingHandler.run()

[andi welchlin]

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
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
on_stop
Exception ignored in: 
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/proton/wrapper.py", line 95, in
__del__
pn_decref(self._impl)
  File "/usr/lib/python3/dist-packages/proton/wrapper.py", line 63, in
__getattr__
attrs = self.__dict__["_attrs"]
KeyError: ('_attrs',)


Do you know how to solve this?

Thanks,
Andreas

On Thu, Feb 22, 2018 at 11:16 AM, Gordon Sim  wrote:

> The container is single-threaded, so invoking methods on it from another
> thread is not safe (it would be nice if close() were an exception here, but
> I guess it is not).
>
> What you can do is inject an application defined event into the loop to do
> the shutdown. E.g. as in attached modification to your example.
>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>

Re: QPID Proton 0.19 Python: Exit MessagingHandler.run()

[Gordon Sim]

The container is single-threaded, so invoking methods on it from another 
thread is not safe (it would be nice if close() were an exception here, 
but I guess it is not).


What you can do is inject an application defined event into the loop to 
do the shutdown. E.g. as in attached modification to your example.
#!/usr/bin/env python

from proton.reactor import ApplicationEvent, Container, EventInjector
from proton.handlers import MessagingHandler
from proton import Message, Connection

import threading
import sys

class AmqpReceiver(MessagingHandler):
def __init__(self):
super(AmqpReceiver, self).__init__(prefetch=50)
#self.host = "localhost:9001"
self.host = "localhost"

self.container = Container(self)
self.events = EventInjector()
self.container.selectable(self.events)
self.conn = None
self.receiver = None
self.thread = threading.Thread(target=self.run)
self.thread.daemon = True
self.thread.start()

def on_message(self, event):
print("got message: event: ", event.message)

def on_start(self, event):
print("on start")
self.conn = self.container.connect(self.host, reconnect=False)
self.receiver = self.container.create_receiver(self.conn,
"test.awe.queue")

def run(self):
print("run container")
self.container.run()
print("after container.run()")
sys.stdout.flush()

def _stop(self):
print('call stop')
self.events.trigger(ApplicationEvent('stop'))
print('call join')
self.thread.join()
print('done stop')

def on_stop(self, event):
print("on_stop")
self.container.stop()

def on_connection_closed(self, event):
print("on_connection_closed")

def on_session_closed(self, event):
print("on_session_closed")

def on_link_closed(self, event):
print("on_link_closed")

def on_disconnected(self, event):
print("on_disconnected")


try:
handler = AmqpReceiver()
value = input("press enter")
handler._stop()
except Exception as ex:
print("got EXCEPTION")
print(ex)


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: QPID Proton 0.19 Python: Exit MessagingHandler.run()

[andi welchlin]

Yes, sure:

#!/usr/bin/env python3

from proton.reactor import Container
from proton.handlers import MessagingHandler
from proton import Message, Connection

import threading
import sys

class AmqpReceiver(MessagingHandler):
def __init__(self):
super().__init__(prefetch=50)
self.host = "localhost:9001"

self.container = Container(self)
self.conn = None
self.receiver = None
self.thread = threading.Thread(target=self.run)
self.thread.daemon = True
self.thread.start()

def on_message(self, event):
print("got message: event: ", event.message)

def on_start(self, event):
print("on start")
self.conn = self.container.connect(self.host, reconnect=False)
self.receiver = self.container.create_receiver(self.conn,
"test.awe.queue")

def run(self):
print("run container")
self.container.run()
print("after container.run()")
sys.stdout.flush()

def _stop(self):
print('call stop')
self.container.stop()
print('call join')
self.thread.join()
print('done stop')

def on_connection_closed(self, event):
print("on_connection_closed")

def on_session_closed(self, event):
print("on_session_closed")

def on_link_closed(self, event):
print("on_link_closed")

def on_disconnected(self, event):
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  wrote:

> On 22/02/18 08:05, andi welchlin wrote:
>
>> 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() gracefully?
>>
>
> If all connections it is managing are closed and there are no timed events
> pending, it should exit by itself.
>
> Do you have an example you can share showing the problem?
>
> -
> To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
> For additional commands, e-mail: users-h...@qpid.apache.org
>
>

Re: QPID Proton 0.19 Python: Exit MessagingHandler.run()

[Gordon Sim]

On 22/02/18 08:05, andi welchlin wrote:

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() gracefully?


If all connections it is managing are closed and there are no timed 
events pending, it should exit by itself.


Do you have an example you can share showing the problem?

-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

Re: QPID Proton 0.19 connection.close() does not close remote connection

[Gordon Sim]

On 22/02/18 07:53, andi welchlin wrote:

Hello Gordon,

thank you for the hint. This was exactly what I needed.
Now I call close and in the method on_connection_closed() I stop the
container.
The connection is then closed remotely.

Would be nice to reflect this in the Proton examples.


When the container has nothing left to do, e.g. if the last socket 
closes and is removed from the loop and there are no timer actions 
pending or anything, it will automatically exit. The examples mostly 
rely on that.


-
To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org
For additional commands, e-mail: users-h...@qpid.apache.org

QPID Proton 0.19 Python: Exit MessagingHandler.run()

[andi welchlin]

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() gracefully?

Kind Regards,
Andreas