Re: [VOTE] Release Apache Qpid JMS 0.28.0

On Wed, Dec 13, 2017 at 1:29 PM, Jiri Danek <jda...@redhat.com> wrote: > 3. Execute the following > > java -jar cli-qpid-jms-1.2.2-SNAPSHOT-0.27.0.jar sender... > I meant 0.28.0.jar, sorry. > The problem seems to be in org.apache.qpid.proton.codec.DecoderImpl#readC

Re: [VOTE] Release Apache Qpid JMS 0.28.0

On Wed, Dec 13, 2017 at 10:25 AM, Jiri Danek <jda...@redhat.com> wrote: > On Mon, Dec 11, 2017 at 7:21 PM, Robbie Gemmell <robbie.gemm...@gmail.com> > wrote: > >> P.S. If you want to test it out using maven (e.g with the examples src, or >> your own things), you

Re: [VOTE] Release Apache Qpid JMS 0.28.0

On Mon, Dec 11, 2017 at 7:21 PM, Robbie Gemmell wrote: > P.S. If you want to test it out using maven (e.g with the examples src, or > your own things), you can temporarily add this to your poms to access the > staging repo: > > > > staging >

Re: Electron/Amqp MessageAnnotations in Golang

On Fri, Nov 10, 2017 at 1:10 PM, Alessio Gottardo wrote: > > Out of curiosity is there a specific reason for `panic`ing in the > `default` case instead of returning an `error`?I just became aware of this > `recover` mechanism in go to handle a runtime `panic` thrown

Re: [VOTE] Release Apache Qpid JMS 0.26.0

+1 (nonbinding) added the staging maven repository to a test project https://github.com/rh-messaging/cli-java, executed tests multiple times against Artemis 2.4.0-SNAPSHOT broker, always passed, including the SO_LINGER thing, did that on OpenJDK 8, OracleJDK 8 and also OracleJDK 9, no problems

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: Meaning of http: yes in qdrouterd.conf

On Mon, May 29, 2017 at 8:56 PM, Gordon Sim <g...@redhat.com> wrote: > On 29/05/17 19:12, Alan Conway wrote: > >> On Mon, 2017-05-29 at 16:03 +0200, Jiri Danek wrote: >> >>> Hello, I've added http: yes to the listener in the default broker >>> config. &

Meaning of http: yes in qdrouterd.conf

Hello, I've added http: yes to the listener in the default broker config. So my only listener on the router looks like this listener { host: 0.0.0.0 port: amqp authenticatePeer: no saslMechanisms: ANONYMOUS http: yes } I am now unable to connect with qdstat to the broker

Re: Dispatch router 2-phase start

allow only management on this extra port... > > ____ > From: Jiri Danek <jda...@redhat.com> > Sent: Monday, May 15, 2017 12:04:50 PM > To: users > Subject: Re: Dispatch router 2-phase start > > On Mon, May 15, 2017 at 12:00 PM, Adel Boutros

Re: Dispatch router 2-phase start

On Mon, May 15, 2017 at 12:00 PM, Adel Boutros wrote: > Hello Gordon, > > > With what you are proposing, the order of the configuration becomes > critical because if the public listener is configured before the connectors > and autolinks, I would have the same issue with

Re: Using Python Qpid Proton reactor with another event loop in the same application; messages are getting sent coalesced somehow

On Fri, May 5, 2017 at 10:12 AM, Gordon Sim wrote: > > A proton container instance is not threadsafe, so all calls to it and the > connections it manages should be done on the containers event thread (i.e. > the one calling run). > > You can trigger a custom 'event' to be

Using Python Qpid Proton reactor with another event loop in the same application; messages are getting sent coalesced somehow

Hello the list, I want to ask for help with my application. It is a rather trivial group chat written in Python using the Python Qpid Proton library and the Tkinter library for GUI. I have two problems regarding this application. First, I want to ask if I designed it correctly. I am spawning

End-to-end WebDriver test for Qpid Dispatch Router console

Hello folks, for a while I've been working on WebDriver (Selenium 2.0) tests for the Dispatch web console. The idea is to have automatic check that the console is working and usable. I'd like to share it now in order to get feedback and possibly even adoption. This started as a learning project

Re: [Qpid-Dispatch] qdmanage query doesn't take into account the name option when passed

Hello Adel, On Fri, Jul 1, 2016 at 5:23 PM, Adel Boutros wrote: > I have one more question: What is considered a "Management entity"? > > I have a feeling the "READ" only works with the "connector" type because > with the other types, I am getting some weird exceptions: >

Re: [Qpid-Dispatch] Dynamic port allocation from the command line

On Wed, Jun 29, 2016 at 3:05 PM, Adel Boutros wrote: ... > > > Hello, > > > > > > In Qpid Java Broker, we can set any port dynamically in the > config.json file > > > by using properties and setting them on the command line. Is there > something > > > similar for the