Re: Serious Bug in AMQP 1.0 JMS Client with persistent messages

On 01/08/2014 03:41 PM, Rob Godfrey wrote: On 8 January 2014 21:27, Fraser Adams fraser.ad...@blueyonder.co.uk wrote: On 08/01/14 18:55, Rob Godfrey wrote: Hi Uli, To enable synchronous publishing you need to either set the Java system property qpid.sync_publish to true, or have

Re: Serious Bug in AMQP 1.0 JMS Client with persistent messages

On 01/08/2014 05:34 PM, uromahn wrote: With the patch added to my local sources, I ran a bunch of different tests against an ActiveMQ 5.9.0 and 5.10-SNAPSHOT broker using the patched as well as unpatched client library. To summarize my findings: 1. running the patched client against ActiveMQ

Re: Welcome Tim Bish as a Qpid committer (was Re: Proton-based AMQP 1.0 JMS client collaboration)

Mappings TC. Timothy Bish, one of the committers/PMC members at the Apache ActiveMQ project, is going to join me working on this effort going forward. Tim has previously done a lot of work on an JMS 1.1 AMQP 1.0 client using Proton for AMQP 1.0 support, with his existing code being available

Re: [VOTE] Migrate the repo for the new JMS client work to use Git

On 09/16/2014 12:35 PM, Robbie Gemmell wrote: Hello all, I mentioned this briefly in a previous thread, and have decided just to call a vote on the subject. I would like to migrate the repo for the new JMS client work to use Git rather than Subversion. This wont affect the rest of the Qpid

Re: Timeline to drop Java 6 support for Proton?

Just for information purposes the next release of ActiveMQ which hopes to use Proton 0.8 once it's released has now moved onto support for JDK 7 and dropped official support for JDK 6. On 09/24/2014 10:24 AM, Robbie Gemmell wrote: The compilation issue I missed in the patch was test-only this

Any ETA on a QPid 0.32 release

We've been working on improving the AMQP 1.0 support in ActiveMQ and I've found that the trunk code for QPid JMS client contains some fixes that would be nice to have in for testing the fixes that are in the pipeline for the broker. Was wondering if there is any idea on when the 0.32 release

Re: towards releasing the new AMQP 1.0 JMS client

On 02/19/2015 08:01 AM, Robbie Gemmell wrote: Any more opinions out there on the name/version of the new client? If not, I'll likely proceed to update the version to 0.1.0[-SNAPSHOT], leave the module names as qpid-jms-foo, and begin working on setting up a Jenkins job to publish snapshots to

Re: [VOTE] Release Qpid JMS 0.1.0

+1 * Verified the signatures matched * Built source bundle and ran tests * Tested ActiveMQ using staged jars * Checked that all artefacts have proper license and notice files included. On 03/16/2015 03:53 PM, Robbie Gemmell wrote: Hi all, We have reached a point that it would be useful to do

Re: Qpid JMS 0.1.0-beta

On 03/09/2015 03:21 PM, Robbie Gemmell wrote: Hi everyone, I have posted a beta build for the new JMS client, in order to test out the release process more and give people something fixed to test around with before we release. The source and binary archives for the beta can be grabbed from:

Re: 0.32 release update - RC 2 is available

I wouldn't treat it as a blocker for the release, I'm pretty sure this has been popping up in our CI for some time now. On 03/12/2015 12:36 PM, Rob Godfrey wrote: From looking at the code I don't think this is a new issue... I think the same deadlock path would have been present in 0.30 and

Re: Qpid JMS 0.1.0-beta

On 03/11/2015 10:15 AM, Jakub Scholz wrote: Hi Robbie, I played with it a bit ... what I noticed is that it looks like it completely ignores the truststore which I pass to the client using the transport.trustStoreLocation option. Can it be that the

Re: Qpid JMS 0.1.0 and SASL EXTERNAL

On 03/26/2015 08:19 AM, Jakub Scholz wrote: Hi Robbie, Tim, I was wondering ... does the new JMS client already support SASL EXTERNAL authentication? It looks like it selects the EXTERNAL mechanism when it is offered by the broker, but it looks like it never responds to the challenge sent by

Re: [VOTE] Release Qpid JMS client 0.2.0

+1 I performed the following checks * Inspected the LICENSE and NOTICE files in both src and bin archives * Validated the signatures for both archives. * Built the project from the source archive and ran all tests (no failures). * Reviewed the included documentation. * Ran the example against an

Re: Qpid JMS discorvery

On 06/08/2015 07:21 AM, Erik Aschenbrenner wrote: Dear Qpid users, the Qpid JMS 0.2.0 release contains the library qpid-jms-discovery-0.2.0.jar. What is it good for? Regards, Erik -- View this message in context: http://qpid.2158936.n2.nabble.com/Qpid-JMS-discorvery-tp7625966.html

Re: Changing from old Qpid JMS client to Qpid JMS 0.2.0

On 06/03/2015 09:45 AM, Erik Aschenbrenner wrote: Dear Qpid-Users, I just tried to use the new proton based Qpid JMS 0.2.0 client. I removed the jars of the old client (Qpid JMS 0.32) and added the jars of the new client to my project. When I try to start my application I'm getting this

Re: [VOTE] Release Qpid JMS client 0.3.0

+1 Built from source, ran the tests. Validated the sigs Checked that the license and notices were present. Ran the example Tested ActiveMQ Unit Test suite using this 0.3.0 jars On 06/11/2015 02:46 PM, Robbie Gemmell wrote: Hi all, We have made a bunch of fixes and improvements since the

Re: Welcome Jakub Scholz as Qpid committer and PMC member

On 05/22/2015 02:24 PM, Robbie Gemmell wrote: The Qpid PMC has voted to grant commit rights and PMC membership to Jakub Scholz in recognition of his contributions to the project. Please join me in extending Jakub a warm welcome! Robbie

Re: [VOTE] Release Qpid Proton 0.10 (RC2)

On 08/10/2015 02:34 PM, Robbie Gemmell wrote: Hi all, I have put up a second cut for 0.10, please test it and vote accordingly. This fixes a crash (PROTON-976) reported against the previous spin, and adds a known issue (PROTON-975) of possible failure using the DIGEST-MD5 mechanism against

Re: [VOTE] Release Qpid JMS client 0.4.0

On 08/14/2015 08:47 AM, Robbie Gemmell wrote: Hi all, Its time for the 0.4.0 Qpid JMS client release, now that Proton 0.10 is available. I have put together a first spin, please test it and vote accordingly. The source and binary archives can be grabbed from here:

Re: [VOTE] Release Qpid JMS client 0.6.0

+1 * Validated signature and checksums * Check license and notices in src and bin archives * Built from source and ran all tests * Ran examples against ActiveMQ broker * Ran ActiveMQ internal AMQP tests using the deployed artifacts. On 10/08/2015 02:09 PM, Robbie Gemmell wrote: > Hi folks, > > I

Re: Qpid JMS client able to send but not receive

You need to call connection.start() in order to begin processing of incoming messages when dealing with JMS connections. On 12/17/2015 06:43 PM, Mark Soderquist wrote: > I have implemented a simple client with the qpid-jms-client 0.6.0 client > against Qpid 6.0.0 Java Broker. I have successfully

Re: [VOTE] Release Qpid JMS client 0.7.0

+1 Checked the signatures and checksums Checked that license and notice files were included. Built the source archive and ran tests. Used the staged artifacts to run the ActiveMQ AMQP JMS tests. Ran the examples from the source build against ActiveMQ On 12/18/2015 11:55 AM, Robbie Gemmell wrote:

Re: [VOTE] Release Qpid JMS client 0.10.0

+1 * checked the license and notice files in the archives * built from source and ran all tests. * ran the example against an ActiveMQ broker * ran the ActiveMQ broker tests using the artifacts from the staging repo * gave the updated docs a once over. On 06/27/2016 12:33 PM, Robbie Gemmell

Re: [VOTE] Release Qpid JMS client 0.8.0

+1 * Checked signatures and checksums * Built the source bundle and ran the tests * Ran the included example against an ActiveMQ broker * Tested the ActiveMQ broker AMQP module using the staged artifacts * Reviewed the license and notice files in both the src and bin archives On 02/16/2016 12:15

Re: Unhandled exception when using High Availabilty in Qpid Java Broker 6.0.0

On 03/10/2016 06:12 PM, Rob Godfrey wrote: On 10 March 2016 at 23:44, Adel Boutros wrote: If I compile while skipping tests and deploy the jar then the broker no longer crashes. Nevertheless, the client doesn't try the 2nd URL, instead it fails with the below stack. If I

Re: Unhandled exception when using High Availabilty in Qpid Java Broker 6.0.0

On 03/10/2016 05:44 PM, Adel Boutros wrote: If I compile while skipping tests and deploy the jar then the broker no longer crashes. Nevertheless, the client doesn't try the 2nd URL, instead it fails with the below stack. If I put back the MASTER URL before the Replicate URL, then everything

Re: JMS client - send timeout

No, there is not currently a configurable send timeout implemented on the client. I've opened QPIDJMS-157 to track the feature request. You can configure the failover bits to give up after some number of attempts currently which would cause the sends to break. On 03/16/2016 06:02 AM, Julien

Re: Anyone have an example of using message setProperty()?

On 04/07/2016 04:55 PM, Flores, Paul A. wrote: At client site. Need a clear example of the usage of setProperty() Can you provide a bit more context on what code you are referring to and what you want to accomplish? Thanks for your help it is appreciated! Paul

Re: [VOTE] Release Qpid JMS client 0.9.0

+1 * Checked the signatures and sums * Built the src and ran all tests * Ran the example against an ActiveMQ 5 broker * Ran the AMQP test suite in ActiveMQ 5 using the staged artifact * Checked the LICENSE and NOTICE files * Reviewed the Documentation file On 04/07/2016 01:04 PM, Robbie

Re: AMQP 1.0 Qpid JMS and an Issue with Failover/Reconnect

On 03/22/2016 12:51 PM, Aleks Balaban wrote: Thank you for writing back. My client quite minimalistic JMS client application with usual JMS stuff such as Connection, Session objects and "onMessage" listeners, which does nothing but connect to an AMQP server and waits to receive

Re: AMQP 1.0 Qpid JMS and an Issue with Failover/Reconnect

On 03/23/2016 08:56 AM, Aleks Balaban wrote: Tim, Thx, good to know that the failover works! Obviously I've been doing something wrong. Well, as you requested here is my JMS/AMQP client source (I have removed the SSL initialization part used for amqps conncetion ): Your code relies on

Re: Welcome Ganesh Murthy as an Apache Qpid committer

Nice job Ganesh! Welcome! On 03/01/2016 12:30 PM, Robbie Gemmell wrote: The Qpid PMC have voted to grant commit rights to Ganesh Murthy in recognition of his contributions to the project. Welcome, Ganesh! Robbie - To

Re: [VOTE] merge the proton mailing list into the users/dev lists

+1 On 03/30/2016 06:25 AM, Robbie Gemmell wrote: Hello folks, Many moons ago, a seperate mailing list was established for Proton, back when it was purely a protocol engine other components would use. Its scope has since expanded beyond that and the separate mailing list has I feel been an

Re: Questions about disabling sending of UserID with messages QPID-7159/QPIDJMS-163

On 03/30/2016 07:12 AM, Robbie Gemmell wrote: On 30 March 2016 at 11:40, Oleksandr Rudyy wrote: Hi Robbie, I would like to clarify the name of a connection parameter to disable sending of UserID for both new and legacy JMS clients. New JIRA QPIDJMS-163 requires to implement

Re: AMQP 1.0 Qpid JMS and an Issue with Failover/Reconnect

I'd recommend that you post some code to show what your client is doing. The logs really don't provide enough information to diagnose what might be going on. On 03/22/2016 11:07 AM, Aleks Balaban wrote: Hi, Im using Qpid JMS 0.8.0 library in order to implement a standalone Java AMQP

Re: [DISCUSS] removing the 'proton/contrib/proton-hawtdispatch' module

Agreed, this seems like code that would be better off living in the hawtdispatch project if someone really wanted to pick up that torch. On 04/26/2016 12:37 PM, Robbie Gemmell wrote: As per the subject, I'd like to suggest removing 'proton/contrib/proton-hawtdispatch' module. hawtdispatch

Re: [VOTE] Migrate Qpid C++ and Qpid Python to Git

+1 On 04/26/2016 10:40 AM, Justin Ross wrote: As proposed and discussed at the following links: http://qpid.2158936.n2.nabble.com/Qpid-source-code-reorg-update-tt7641526.html http://qpid.2158936.n2.nabble.com/Qpid-Subversion-reorganization-proposal-tt7639094.html

Re: [DISCUSS] removing the 'proton/contrib/proton-jms' module

On 04/26/2016 10:41 AM, Robbie Gemmell wrote: As per the subject, I'd like to suggest removing 'proton/contrib/proton-jms' module. It was written as part of adding AMQP 1.0 support to the ActiveMQ 5.x broker and then contributed to Proton, and used across ActiveMQ 5.x/Artemis/Apollo. The code

Re: [VOTE] Release Qpid Proton 0.12.2

On 04/14/2016 01:28 PM, Robbie Gemmell wrote: Hi all, I have put up an RC for 0.12.2, please test it and vote accordingly. The source release archive and sig/checksums can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/proton/0.12.2-rc1/ Maven artifacts for the Java bits can be

Re: [VOTE] move the website bits to a Git repo

+1 On 04/19/2016 08:03 PM, Robbie Gemmell wrote: Hi folks, Short version: As per the title, I'd like to vote on moving the website bits to a Git repo, specifically "qpid-site". Further info: The site is one of the single largest groups of stuff we have, both with regard to its previous

Re: Cannot conect while using ActiveMQ with Qpid JMS client

What is the connection URI that you are giving the client JmsConnectionFactory? On 07/19/2016 08:28 AM, DraCzech wrote: One thing I found out is that activemq-amqp artifact has proton-j compile dependency: +- org.apache.activemq:activemq-amqp:jar:5.13.3:compile | \-

Re: [VOTE] Release Qpid Proton-J 0.17.0

+1 * Review the license and notice files * Verified the signatures and checksums * Checked using the rat check goal that all files are licensed properly * Built from source and ran the tests * Built Qpid JMS using the staged artifact and ran the tests * Built ActiveMQ using the staged artifact

Re: [JMS]How to verify the connection is ready for creating session

On 02/14/2017 02:32 PM, pqvchen1 wrote: Just question further, is there a way that I can check whether the connection or session is healthy? and ready to send/receive message before I doing so? thanks again. Final question. You can send a message, and if it throws an exception then it's not

Re: [JMS]How to verify the connection is ready for creating session

On 02/14/2017 02:12 PM, pqvchen1 wrote: Thanks for reply. So can I just keep that connection open and not close even after the session is done? and reuse the connection for next createSession? Yes, the Connection can remain open an be used to create multiple sessions either at once or many

Re: [VOTE] Release Qpid JMS client 0.20.0

On 01/16/2017 02:29 PM, Adel Boutros wrote: Hello Robbie, Out of curiosity, can you please explain why the release is 0.20.0 and not 0.12.0? When will an official 1.0.0 be out? The main reason for the bump is that this version now implements the JMS 2.0 API and is therefore a larger shift

Re: [VOTE] Release Qpid JMS client 0.20.0

+1 * Validated the signatures and sums * Reviewed the License and Notice files * Reviewed the documentation file * Built from source and ran the tests * Used the staged artifacts in the ActiveMQ AMQP test suite * Ran the provided examples against an ActiveMQ broker On 01/16/2017 01:38 PM,

Re: Performance degradation with Qpid JMS Client 0.20.0

On 02/28/2017 08:10 AM, Oleksandr Rudyy wrote: Hi all, After upgrading Qpid JMS Client from version 0.11.0 to version 0.20.0 our performance test results dropped approximately on 20-25% in the performance tests testing transaction performance with trunk version of Qpid Java Broker. Changing

Re: [VOTE] Release Qpid Proton 0.14.0

+1 * Built from source and ran all the tests * Checked signature and sums * Validated License and NOTICE files * Ran Qpid JMS tests using the 0.14.0 maven dep * Ran ActiveMQ 5.x tests using the 0.14.0 maven dep On 08/17/2016 10:06 AM, Justin Ross wrote: The artifacts proposed for release:

Re: [VOTE] Release Qpid JMS client 0.11.1

+1 * Reviewed the bin and src for license and notice files * Checked signatures and checksums * Built from source and ran the tests * Built ActiveMQ using staged bits and ran its tests * Ran the included example against an ActiveMQ 5.14.1 broker On 09/30/2016 11:24 AM, Robbie Gemmell wrote: Hi

Re: [VOTE] Release Qpid Proton 0.15.0

+1 * Validated signatures and checksums * Built from source using CMake and Maven (proton-j) and ran tests * Tested ActiveMQ broker using the staged libraries On 10/10/2016 01:20 PM, Robbie Gemmell wrote: Hi folks, I have put together a spin for a 0.15.0 Qpid Proton release as proposed,

Re: [VOTE] Release Qpid Proton 0.16.0

+1 * Checked signatures and checksums * Built from source and ran tests using cmake * Built proton-j using maven and ran the tests * Reviewed License, Notice, and other documentation files * Built ActiveMQ using the staged artifacts and ran the AMQP tests * Built Qpid JMS using the staged

Re: [Qpid JMS 0.11.1] Nullpointer exception when providing an empty string to the ConnectionFactory

On 01/13/2017 10:08 AM, Adel Boutros wrote: Hello Tim, I took a look on the master brunch of the github repo and indeed it seems to be fixed. Regards, Adel I made some additional changes to make the error reporting more consistent. From: Timothy Bish

Re: Qpid JMS client JmsConnection.close() hangs

Close timeout handling has been fixed up a fair bit with issue: https://issues.apache.org/jira/browse/QPIDJMS-228 On 11/25/2016 11:04 AM, Robbie Gemmell wrote: "I also think I see an issue with the closeTimeout handling in that in one place it seems likely to be using the requestTimeout value

Re: [VOTE] Migrate Qpid Broker J and Qpid JMS AMQP 0-x Client from SVN to GIT

+1 On 04/04/2017 08:44 AM, Keith W wrote: As already proposed and discussed in the following thread: http://qpid.2158936.n2.nabble.com/DISCUSS-Migrate-Qpid-Broker-for-Java-and-Qpid-JMS-AMQP-0-x-Client-from-SVN-to-GIT-tt7661505.html#none In summary, the proposal is: Qpid Broker J: Current

Re: One subscription, multiple consumers.

On 04/11/2017 12:42 PM, Robbie Gemmell wrote: For the most part topic subscriptions only ever had a single subscriber asociated with them, until at some point someone thought it would be useful to support more. Some systems can do that, others cant, others still have specific mechanisms to

Re: [VOTE] Release Apache Qpid JMS 0.22.0

On 04/17/2017 01:34 PM, Robbie Gemmell wrote: Hi folks, I have put together a spin for a 0.22.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.22.0-rc1/ The maven

Re: Performance degradation with Qpid JMS Client 0.20.0

ary 2017 at 17:04, Timothy Bish <tabish...@gmail.com> wrote: On 02/28/2017 08:10 AM, Oleksandr Rudyy wrote: Hi all, After upgrading Qpid JMS Client from version 0.11.0 to version 0.20.0 our performance test results dropped approximately on 20-25% in the performance tests testing tr

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

+1 * validated signatures and sums * built from source and ran the tests, * built ActiveMQ using the staged artifacts and ran the tests * built Qpid JMS using the staged artifacts and ran the tests. * Checked the License and NOTICE files Issue with downloading the sha file from the site as it

Re: [VOTE] Release Apache Qpid JMS 0.21.0

+1 * Validated the signatures and checksums * Checked for license and notice files in the source and binary archives * Built from source and ran the tests. * Checked the binary archive for the proper files * Built an ActiveMQ 5.x broker against the staged bits and ran the AMQP tests. On

Re: synchronous sending - using javax.jms.MessageProducer::send

On 03/07/2017 09:21 AM, Vince Cole wrote: I have a requirement to for my JMS client to block, and only return once the message has been accepted onto the specified queue or topic. If the message is not accepted, then an exception should be thrown. We don't care whether anything actually consumes

Re: [DISCUSS] release checksum filename extension

On 03/07/2017 12:23 PM, Robbie Gemmell wrote: According to http://www.apache.org/dev/release-distribution.html#sigs-and-sums .sha is actually required: "An SHA checksum SHOULD also be created and MUST be suffixed .sha. The checksum SHOULD be generated using SHA512." I find the extension a

Re: [Qpid JMS client] Asynchronous send JMS 2.0

On 07/14/2017 09:34 AM, Vavricka wrote: Hi, qpid jms client version - 0.23.0 qpid c++ broker version - 0.34 I am unable to send messages asynchronously using the JMS 2.0 API. Connection string is same for JMS 1.1 and JMS 2.0 -

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

On 08/02/2017 10:33 AM, Robbie Gemmell wrote: Hi folks, I have put together a first spin for a Qpid Proton-J 0.20.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.20.0-rc1/ (Note: the

Re: Create durable subscription to Azure Service Bus

On 08/07/2017 09:26 AM, 4 Integration wrote: Hi, Testing QPid JMS (AMQP v1.0) with Azure Service Bus (SB). Trying to get durable subscriptions to work. I have created a topic in SB When starting my test app I get: javax.jms.JMSException: The messaging entity

Re: [VOTE] Release Apache Qpid JMS 0.24.0

On 08/04/2017 05:42 PM, Robbie Gemmell wrote: Hi folks, I have put together a spin for a 0.24.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.24.0-rc1/ The maven

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

+1 * Checked signatures and checksums * Built from source and ran tests * used mvn apache-rat:check to look for missing license headers * Checked for license and notice files in the archives * Used staged version with Qpid JMS to run all tests * Used staged version with ActiveMQ 5.x to run the

Re: [VOTE] Release Apache Qpid JMS 0.23.0

+1 * Verified signatures and checksums * Built from source archive and ran all tests * Used apache-rat:check to look for missing license files * Validated that LICENSE and NOTICE files are in place * Ran the example included in the binary against ActiveMQ and ActiveMQ Artemis * Built ActiveMQ

Re: AmqpProvider - Transport connection remotely closed

The error alone without any other context simply indicates that the remote end suddenly broke the connection to the client, as to why you'd want to try and do some more digging. One thing to do in these cases is to try and capture an AMQP protocol trace to see what's happening on the wire,

Re: 2017-05-09 22:20:29,796 | ERROR | mix-7.0.0/deploy | BlueprintDeploymentListener | 105 - org.apache.karaf.deployer.blueprint - 4.0.8 | Unable to parse deployed file /tmp/apache-servicemix-7.0.0/de

It's XML so an & is expressed as "" "amqps://esesslx0827.ss.sw.ericsson.se:9443?transport.keyStoreLocation=etc/qpid.jkstransport.keyStorePassword=test123" On 05/09/2017 06:26 PM, jeunii wrote: I am trying to setup a connection using SSL. My config initially was ::

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

On 09/13/2017 10:35 AM, Robbie Gemmell wrote: Hi folks, I have put together a first spin for a Qpid Proton-J 0.22.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.22.0-rc1/ The maven

Re: [VOTE] Release Apache Qpid JMS 0.25.0

On 09/18/2017 12:45 PM, 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: [VOTE] Release Apache Qpid JMS 0.26.0

On 10/04/2017 07:35 AM, Robbie Gemmell wrote: Hi folks, I have put together a spin for a 0.26.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.26.0-rc1/ The maven

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

On 10/12/2017 12:39 PM, Robbie Gemmell wrote: Hi folks, I have put together a first spin for a Qpid Proton-J 0.23.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.23.0-rc1/ The maven

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

On 08/31/2017 10:15 AM, Robbie Gemmell wrote: Hi folks, I have put together a first spin for a Qpid Proton-J 0.21.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.21.0-rc1/ The maven

Re: [VOTE] Release Apache Qpid Proton 0.18.0

+1 * Validated signature and checksum * Verified License and Notice files present * Built from source and ran self tests. On 10/18/2017 01:29 PM, Robbie Gemmell wrote: Hi folks, I have put together a first spin for a Qpid Proton 0.18.0 release, please test it and vote accordingly. The source

Re: [VOTE] Release Apache Qpid JMS 0.28.0

On 12/13/2017 08:39 AM, Jiri Danek wrote: On Wed, Dec 13, 2017 at 1:29 PM, Jiri Danek 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

Re: [VOTE] Release Apache Qpid Proton 0.19.0

On 12/19/2017 04:17 PM, Robbie Gemmell wrote: Hi folks, I have put together a spin for a Qpid Proton 0.19.0 release, please give it a test out and vote accordingly. The source archive can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/proton/0.19.0-rc1/ The JIRAs currently

Re: [VOTE] Release Apache Qpid CPP 1.37.0

On 11/21/2017 01:20 PM, Robbie Gemmell wrote: Hi folks, I have put together a spin for a Qpid CPP 1.37.0 release, please give it a test out and vote accordingly. The source archive can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/cpp/1.37.0-rc1/ The JIRAs currently assigned

Re: [VOTE] Release Apache Qpid JMS 0.27.0

On 11/01/2017 12:37 PM, Robbie Gemmell wrote: Hi folks, I have put together a spin for a 0.27.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.27.0-rc1/ The maven

Re: [VOTE] Release Apache Qpid JMS 0.28.0

On 12/11/2017 01:21 PM, Robbie Gemmell wrote: Hi folks, I have put together a spin for a 0.28.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.28.0-rc1/ The maven

Re: Connection problem with Azure Service Bus Queue

On 12/01/2017 12:38 PM, Gordon Sim wrote: On 01/12/17 14:37, Шелест Ігор wrote: hello_world called on_container_start called[00CB1200]:  -> SASL [00CB1200]:  <- SASL [00CB1200]:0 <- @sasl-mechanisms(64) [sasl-server-mechanisms=@PN_SYMBOL[:MSSBCBS, :PLAIN, :ANONYMOUS, :EXTERNAL]] [00CB1200]:0 ->

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

On 12/08/2017 12:36 PM, Robbie Gemmell wrote: Hi folks, I have put together a first spin for a Qpid Proton-J 0.24.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.24.0-rc1/ The maven

Re: Proposed update to minimum tool requirements for proton-c

On 10/20/2017 03:47 PM, Andrew Stitcher wrote: In the course of the 0.18 release process I've been looking at the minimum build tool versions supported - specifically CMake and C/C++ compilers. I've reached the following conclusions: We should move to a minimum supported cmake of 2.8.12.2, gcc

Re: [VOTE] Release Apache Qpid JMS AMQP 0-x 6.3.1

On 05/15/2018 07:36 AM, Oleksandr Rudyy wrote: Hi folks, I built a candidate release for version 6.3.1 of Qpid JMS AMQP 0-x. Please test and vote accordingly. The source and binary bundles can be taken from: https://dist.apache.org/repos/dist/dev/qpid/jms-amqp-0-x/6.3.1/ The maven artifacts

Re: [VOTE] Release Apache Qpid Proton 0.23.0

On 05/23/2018 03:53 PM, Robbie Gemmell wrote: I have put together a spin for a Qpid Proton 0.23.0 release, please give it a test out and vote accordingly. The source archive can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/proton/0.23.0-rc1/ The JIRAs assigned are:

Re: [VOTE] Release Qpid Dispatch Router 1.1.0 (RC6)

+1 * Validated signatures and checksums * Check for license and notice files * Built from source and ran the tests On 06/07/2018 05:01 PM, Ganesh Murthy wrote: Hello All, Please cast your vote on this thread to release RC6 as the official Qpid Dispatch Router version 1.1.0. RC6

Re: Message going in topic with the use of "session.createQueue(name)"

On 06/13/2018 10:51 AM, Abhishek Kumar wrote: Hi Team, *Test Scenario*: We are having an issue. I have created Destination dest = session.createQueue("test-resource"); *Behaviour:* Message should go to "queue", and if "queue" is not available then *throw exception*. Is this correct outcome?

Re: Message going in topic with the use of "session.createQueue(name)"

On 06/13/2018 04:20 PM, akabhishek1 wrote: Hi Tim, Thanks a lot for your quick reply and clarification. Log file is correct. Please take a look on below link and find again "test-send". http://qpid.2158936.n2.nabble.com/file/t396358/QPid_Send_Topic_Logs.txt

Re: Message going in topic with the use of "session.createQueue(name)"

On 06/13/2018 02:54 PM, akabhishek1 wrote: HI Tim, Thanks a lot for your reply. Yes correct i am using "qpid-jms-client" to connect azure service bus. Please find attached "QPid_Send_Topic_Logs.txt" log file and test class "TestQpidSend.java". *Steps To Reproduce* 1. Create topic "test-topic"

Re: [VOTE] Release Apache Qpid JMS 0.33.0

On 06/11/2018 01:32 PM, Robbie Gemmell wrote: Hi folks, I have put together a spin for a 0.33.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.33.0-rc1/ The maven

Re: qpid-jms: How to get message rejection/redelivery work correctly

On 06/02/2018 07:41 AM, jo.stenb...@offilive.com wrote: Hi, we are using the qpid-jms client with Artemis 2.6. I am having big troubles getting message rejection/redelivery working as expected. I already opened an issue against Artemis https://issues.apache.org/jira/browse/ARTEMIS-1618

Re: [VOTE] Release Apache Qpid Proton 0.24.0

On 06/26/2018 10:56 AM, Robbie Gemmell wrote: Hi folks, I have put together a spin for a Qpid Proton 0.24.0 release, please give it a test out and vote accordingly. The files can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/proton/0.24.0-rc1/ The JIRAs assigned are:

Re: [VOTE] Release Apache Qpid JMS 0.34.0

On 06/25/2018 04:11 PM, Robbie Gemmell wrote: Hi folks, I have put together a spin for a 0.34.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.34.0-rc1/ The maven

Re: [VOTE] Release Apache Qpid JMS 0.29.0

On 01/19/2018 07:30 AM, Robbie Gemmell wrote: Hi folks, I have put together a spin for a 0.29.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.29.0-rc1/ The maven

Re: [VOTE] Release Apache Qpid Proton 0.20.0

On 01/25/2018 07:46 AM, Robbie Gemmell wrote: Hi folks, I have put together a spin for a Qpid Proton 0.20.0 release, please give it a test out and vote accordingly. The source archive can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/proton/0.20.0-rc1/ The JIRAs currently

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

On 01/11/2018 01:34 PM, Robbie Gemmell wrote: Hi folks, I have put together a first spin for a Qpid Proton-J 0.25.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.25.0-rc1/ The maven

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

+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

Re: [VOTE] Release Apache Qpid Proton 0.19.0 (RC2)

On 12/20/2017 01:30 PM, Robbie Gemmell wrote: Hi folks, I have put together a second spin for a Qpid Proton 0.19.0 release, please give it a test out and vote accordingly. The source archive can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/proton/0.19.0-rc2/ The JIRAs

Re: [VOTE] Release Apache Qpid Proton-J 0.28.1 (RC2)

On 08/02/2018 01:20 PM, Robbie Gemmell wrote: Hi folks, I have put together a second spin for a Qpid Proton-J 0.28.1 release, please test it and vote accordingly. The files can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.28.1-rc2/ The maven artifacts are staged for

Re: [VOTE] Release Apache Qpid Proton-J 0.27.3 (RC2)

On 08/02/2018 01:19 PM, Robbie Gemmell wrote: I have put together a second spin for a Qpid Proton-J 0.27.3 release, please test it and vote accordingly. The files can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/proton-j/0.27.3-rc2/ The maven artifacts are staged for now at:

  1   2   3   4   >