RE: [Qpid Java Broker 6.0.4] [Linux] Stop script keeps trying to kill a dead broker

Hello, Thanks for the information. There's one thing that's still not clear though, what do you really mean by graceful shutdown? When you first mentioned this what came to my mind is that the broker will finish the tasks at hand before actually shutting down. But further testing shows that

Ruby Qpid Proton Gem release

Dear all, I hope this is the right place to ask about the planned releases. I have integrated Qpid Proton ruby gem into PR [1] to allow retrieval of events over AMQP. Problem is that this depends on a patch discussed in PROTON-1532 [2] and resolved upstream. For the time being I am using my

Removal of deprecated items from the Dispatch Router schema

A few entities and attributes were deprecated in the 0.6.0 version of Qpid Dispatch Router. As we are coming up on a 1.0 release of the Router, we are going to be entirely removing these deprecated items from the router schema. Any Router code that helped support these deprecated items will also

Re: [VOTE] Release Apache Qpid JMS 0.25.0

On 19 September 2017 at 15:50, Jiri Danek wrote: > +1 (nonbinding) > > Used the maven repo with https://github.com/rh-messaging-qe/cli-java and > executed the few tests there against ActiveMQ Artemis 2.4.0-SNAPSHOT > broker. Result is that

Re: JMS message consumer behavior

Feel free to raise a JIRA at https://issues.apache.org/jira/projects/QPIDJMS. If a server is aggressively handing messages out to other consumers before an existing consumer releases or consumes it and counts that as redelivery, and an application has a somewhat odd setup, then I can see that yes

qpid-interop-test release candidate

Hi, I have put together a candidate release for qpid-interop-test v 0.1. Please 'kick the tires' and give it a test. Feedback and issues would be welcome. The source can be obtained from: https://dist.apache.org/repos/dist/dev/qpid/qpid-interop-test/0.1-rc1/ Instructions for building and

Re: [VOTE] Release Apache Qpid JMS 0.25.0

+1 (nonbinding) Used the maven repo with https://github.com/rh-messaging-qe/cli-java and executed the few tests there against ActiveMQ Artemis 2.4.0-SNAPSHOT broker. Result is that https://issues.apache.org/jira/browse/QPIDJMS-314 is apparently still not resolved (as expected), but without

Re: JMS message consumer behavior

On 19 September 2017 at 13:10, Clemens Vasters wrote: > This may be my ignorance of JMS details, but why does a Qpid JMS consumer go > off and happily prefetch messages when its associated Session/Connection > hasn't even been start()'ed yet? > Mainly its just

Re: Qpid dispatcher without broker

For an overview of the router and configuration start with http://qpid.apache.org/releases/qpid-dispatch-0.8.0/book/book.html For your clients, there's really no configuration difference - they should simply be pointed to the host/port of the router rather than a broker. You can use the router to

Re: [Qpid Java Broker 6.0.4] [Linux] Stop script keeps trying to kill a dead broker

Sorry Alex :( From: Robbie Gemmell Sent: Tuesday, September 19, 2017 1:48:48 PM To: users@qpid.apache.org Subject: Re: [Qpid Java Broker 6.0.4] [Linux] Stop script keeps trying to kill a dead broker Alex or Oleksandr, rather than Rudyy

Re: Plans for the Qpid Dispatch Router 1.0.0

Kai, DISPATCH-775 is in. The Fix-Version was mistakenly not set on the Jira. -Ted On Tue, Sep 19, 2017 at 8:27 AM, Kai wrote: > Would be great to have https://issues.apache.org/jira/browse/DISPATCH-775 > in there. > > Regards, > Kai > > On Tue, Sep 19, 2017 at 12:26

Re: [VOTE] Release Apache Qpid JMS 0.25.0

+1 Built from source and ran tests (saw 1 (non recurring) test failure, discussed off list with Robbie - looks like a ActiveMQ issue) Ran Qpid Broker-J AMQP 1.0 tests (from master) using 0.25.0 client -- Rob On 18 September 2017 at 18:45, Robbie Gemmell wrote: > Hi

Re: Plans for the Qpid Dispatch Router 1.0.0

Would be great to have https://issues.apache.org/jira/browse/DISPATCH-775 in there. Regards, Kai On Tue, Sep 19, 2017 at 12:26 PM Adel Boutros wrote: > Hello Ted, > > > A nice early Christmas gift for me would be > https://issues.apache.org/jira/browse/DISPATCH-773 (You

JMS message consumer behavior

This may be my ignorance of JMS details, but why does a Qpid JMS consumer go off and happily prefetch messages when its associated Session/Connection hasn't even been start()'ed yet? I just got misled by the trace output into believing that my app code's receive/callback usage was wrong.

Re: [VOTE] Release Apache Qpid JMS 0.25.0

On 19 September 2017 at 12:51, Gordon Sim wrote: > On 19/09/17 11:28, Robbie Gemmell wrote: >> >> On 19 September 2017 at 11:20, Gordon Sim wrote: >>> >>> I did see the following test failures, but suspect this is just a >>> configuration issue(?). >>>

Re: [VOTE] Release Apache Qpid JMS 0.25.0

On 19/09/17 11:28, Robbie Gemmell wrote: On 19 September 2017 at 11:20, Gordon Sim wrote: I did see the following test failures, but suspect this is just a configuration issue(?). Failed tests:

Qpid dispatcher without broker

Hi, I am currently evaluating messaging in a Java environment. My use case is following. I want to be able to broadcast announce messages to some small networks which might have a qpid dispatcher reachable. Later I want to be able to setup a worker pattern. Each worker sitting in either

Re: [VOTE] Release Apache Qpid JMS 0.25.0

On 19 September 2017 at 11:20, Gordon Sim wrote: > On 18/09/17 17:45, Robbie Gemmell wrote: >> >> Hi folks, >> >> I have put together a spin for a 0.25.0 Qpid JMS client release, please >> give it a test out and vote accordingly. >> >> The source and binary archives can be

Re: Plans for the Qpid Dispatch Router 1.0.0

Hello Ted, A nice early Christmas gift for me would be https://issues.apache.org/jira/browse/DISPATCH-773 (You don't have to be that generous though if it is not possible). Regards, Adel From: Ted Ross Sent: Monday, September 18, 2017

Re: [Qpid Java Broker 6.0.4] [Linux] Stop script keeps trying to kill a dead broker

Hello Rudyy, +1 for the enhancements  Regards, Adel From: Oleksandr Rudyy Sent: Tuesday, September 19, 2017 11:17:15 AM To: users@qpid.apache.org Subject: Re: [Qpid Java Broker 6.0.4] [Linux] Stop script keeps trying to kill a dead broker

Re: [VOTE] Release Apache Qpid JMS 0.25.0

On 18 September 2017 at 17:45, Robbie Gemmell wrote: > Hi folks, > > I have put together a spin for a 0.25.0 Qpid JMS client release, please > give it a test out and vote accordingly. > > The source and binary archives can be grabbed from: >

Re: [VOTE] Release Apache Qpid JMS 0.25.0

On 18/09/17 17:45, Robbie Gemmell wrote: Hi folks, I have put together a spin for a 0.25.0 Qpid JMS client release, please give it a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/jms/0.25.0-rc1/ The maven

Re: [Qpid Java Broker 6.0.4] [Linux] Stop script keeps trying to kill a dead broker

Hi Olivier, Rob have already provided comprehensive answers on your questions. One thing I would like to add is that both REST API and stop script should shutdown broker gracefully. The script uses signals: it sends SIGTERM to initiate the graceful shutdown. Only if process is still alive after

Re: [Qpid Java Broker 6.0.4] [Linux] Stop script keeps trying to kill a dead broker

On 18 September 2017 at 22:53, VERMEULEN Olivier < olivier.vermeu...@murex.com> wrote: > Hello, > > Following up on Adel's email. > I took a look at the initiateShutdown endpoint you mentioned. > I tested it and it seems to work but I don't see it in any documentation, > not even in the broker

RE: Proton bindings for python3

> -Original Message- > From: Ken Giusti [mailto:kgiu...@redhat.com] > Sent: Freitag, 15. September 2017 15:15 > To: users > Subject: Re: Proton bindings for python3 > > Hi Philipp, > > There's a couple of ways to install the binding via pip: > > 1) from the