Re: [Broker-J v7.0.6] Connection Pool Churning

Hi Sidarth, The stack trace indicates that connection was closed from broker side. The Broker sent the connection close command. For example, this might happen when connection was closed by operator using management API. You might need to look into broker logs for the reasons behind connection clos

Re: Exclusive queues and configuration export

8, Igor Natanzon wrote: > Thanks Alex. The rest api method to set exclusive consumer works perfectly! > > As far as group setup, I am thinking I can ause rest api to pull existing > setup of groups and members, and push the setup to new nodes. Just need to > write a little program

Re: Exclusive queues and configuration export

Hi Igor, The Qpid broker allows to create exclusive queues with one of below exclusivity policies: LINK; only one receiving link can consumer from the queue SESSION; only consumers from one session can consume CONNECTION; only consumers from one connection can consume CONTAINER; only consumers fro

[RESULT][[VOTE] Release Qpid Broker-J 7.1.0 RC2

There were 3 binding +1 votes and no other votes received. The vote has passed. The voting thread can be found here: https://lists.apache.org/thread.html/572242c9aabcfa43c29722d7ad37b8b6dd7dd629582e190647fe7087@%3Cusers.qpid.apache.org%3E I will add the archives to the dist release repo and rele

Re: [VOTE] Release Qpid Broker-J 7.1.0 RC2

distribution * Ran hello world examples using Qpid JMS Client for AMQP 0-x version 6.3.3 and Qpid JMS Client for AMQP 1.0 version 0.40.0 On Mon, 24 Dec 2018 at 21:05, Oleksandr Rudyy wrote: > Hi all, > > I built RC2 for Qpid Broker-J version 7.1.0. > The RC2 coming with the following fixes

[VOTE] Release Qpid Broker-J 7.1.0 RC2

Hi all, I built RC2 for Qpid Broker-J version 7.1.0. The RC2 coming with the following fixes of issues in REST API: QPID-6948: [Broker-J] Fix generation of json response for operations returning void QPID-6948: [Broker-J] Fix hand

Re: [VOTE] Release Qpid Broker-J 7.1.0

Gemmell wrote: > > On Wed, 19 Dec 2018 at 17:09, Oleksandr Rudyy wrote: > > > > Hi folks, > > > > I built release artefacts for Qpid Broker-J version 7.1.0 RC1. > > Please, give them a test out and vote accordingly. > > > > The source and binary archives

Re: [VOTE] Release Qpid Broker-J 7.1.0

tible with previous version of REST API. I would like to fix the defect. Thus, I am cancelling this vote. Kind Regards, Alex On Wed, 19 Dec 2018 at 17:02, Oleksandr Rudyy wrote: > > Hi folks, > > I built release artefacts for Qpid Broker-J version 7.1.0 RC1. > Please, give

Re: Can I expose Java properties set in the Qpid broker server via JMX or the REST API?

Hi Brian, You can add a suffix to the Apache Qpid version which is exposed via Broker attribute 'productVersion'. For example, if version of Qpid Broker is 7.0.6 and suffix is set to 'MY-CORP-1.3', the product version would be '7.0.6;MY-CORP-1.3'. This can be achieved by adding into broker lib fol

[VOTE] Release Qpid Broker-J 7.1.0

Hi folks, I built release artefacts for Qpid Broker-J version 7.1.0 RC1. Please, give them a test out and vote accordingly. The source and binary archives can be grabbed from: https://dist.apache.org/repos/dist/dev/qpid/broker-j/7.1.0-rc1/ The maven artifacts are also staged for now at: https://

Re: [VOTE] Release Apache Qpid JMS 0.40.0

+1 I tested release artefacts as follows: * verified signatures and checksums * built and ran unit tests successfully from source bundle * ran successfully Qpid Broker-J system tests using staged release artefacts (mvn clean install -DskipTests -DskipITs=false -Dnetty-version=4.1.32.Final -Dqpid-j

Re: Availability of holdOnPublishEnabled attribute in Qpid Broker-J 0.32

Hi Sidarth, I am sorry you cannot specify 'holdOnPublishEnabled' argument in queue declare with Qpid Broker-J 7.0.6. The JIRA QPID-7694 was implemented for version 7.1.0. I am about to cut 7.1.x branch and start releasing 7.1.0. (I just need to finish some REST API compatibility layers) In mean ti

Re: Availability of holdOnPublishEnabled attribute in Qpid Broker-J 0.32

Hi Sidarth, The delivery delay functionality was introduced in version 6.0.3 of Qpid Broker-J [1]. Version 0.32 does not have this functionality. Please, upgrade to 7.0. Kind Regards, Alex [1] https://issues.apache.org/jira/browse/QPID-7255 On Thu, 13 Dec 2018 at 18:49, Sidarth Conjeevaram wrot

Re: java qpid server embedded, upgrading from 6.x to 7.x

Thu, 13 Dec 2018 at 00:02, Alex O'Ree wrote: > > The wiki article worked perfectly thanks!. Is there an equivalent for > versions v6.0.0 and v6.1.0? > > On Wed, Dec 12, 2018 at 7:19 AM Alex O'Ree wrote: > > > sweet, thanks! > > > > On Mon, Dec 10, 2

Re: [Java Broker] Connection to broker using public key of certification authority in broker truststore

Hi Tomas, As far as I understood you are trying to set-up client certificate authentication of the client connections over SSL. It should work with Broker-J. For example, system tests [1] and [2] are testing client cert authentication with custom CA. Kind Regards, Alex [1] https://github.com/ap

Re: [NOTICE / DISCUSS] migrating Git repositories to gitbox.apache.org

ill be > necessary) to ensure the accurate info seems reasonable against the > preceding dev period itself. > > Robbie > > On Mon, 10 Dec 2018 at 17:17, Oleksandr Rudyy wrote: > > > > Robbie, > > > > Are you volunteering to migrate all qpid git repos? I can h

Re: [NOTICE / DISCUSS] migrating Git repositories to gitbox.apache.org

Robbie, Are you volunteering to migrate all qpid git repos? I can help you with migration of qpid-broker-j and legacy jms repos. What is your timeline for migration? The reason I am asking is that I was going to cut 7.1.x branch for qpid-broker-j and even produce 7.1.0 RC1 by the end of the week

Re: Java SASL based rest client example

Hi Alex Qpid SASL REST authentication is not a part of Qpid public REST API. We do not expect it to be used outside of Web Management Console. Instead, a basic authentication can be used with REST requests. (It is turned off with plain http by default, but, it is enabled with https). If you are c

Re: java qpid server embedded, upgrading from 6.x to 7.x

Hi Alex, You can have a look at another example of embedding Qpid Broker-J [1] where broker is started using dependencies to broker-core and amqp protocol plugins. This approach is handy when you do not need logback dependencies and have already logging settings configured in your test framework.

Re: [VOTE] Release Apache Qpid JMS 0.39.0

+1 My tests included the following: * verified signatures and checksums * built successfully client from source bundle with running all unit tests * ran successfully system tests for Qpid Broker-J on master using the staged 0.39.0 artefacts (mvn verify -DskipITs=false -Dqpid-jms-client-version=0.

Re: Welcome Roddie Kieley as an Apache Qpid committer

Welcome, Roddie! On Tue, 27 Nov 2018 at 14:38, Robbie Gemmell wrote: > > The Qpid PMC have voted to grant commit rights to Roddie Kieley in > recognition of continued contributions to the project. > > Welcome, Roddie! > > Robbie > > -

Re: [Broker-J] JDBC config store

>> > >> ... > >> > >> "virtualhostnodes" : [ { > >> "name" : "default", > >> "type" : "JSON", > >> "defaultVirtualHostNode" : "true", > >> "virtua

Re: [Broker-J] JDBC config store

Hi Olivier, I am sorry for the inconveniences caused by provided preferences stores configured by default in JDBC system config. I committed changes against QPID-8260 fixing the issue with provided preferences stores in DERBY and JDBC system configs. As Rob has suggested already, you can work

Re: [VOTE] Release Apache Qpid JMS 0.38.0

+1 * Validated signatures and checksums * Built from source and ran the test suite * Run successfully Qpid Broker-J system tests on master with staged qpid-jms-client 0.38.0 artefacts using profile java-mms.1-0 On Mon, 12 Nov 2018 at 18:43, Robbie Gemmell wrote: > > Hi folks, > > I have put toget

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

> While it might have been nice to avoid this until a future point, > given it was a client bug and the situation doesnt arise with the > current release I believe we should proceed as-is. > > Robbie > > On Wed, 7 Nov 2018 at 10:12, Oleksandr Rudyy wrote: > > > > Hi,

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

Hi, I tried to run Qpid Broker-J system tests with qpid-jms-client 0.36.0 and staged org.apache.qpid:proton-j:0.30.0 but JMS 1.1 tests from suite org.apache.qpid.systests.jms_1_1.message.LargeMessageTest failed due to mismatch of received message text and sent message text. The text messages with

Re: Qpid 7.0.6 not listening on HTTPS port at startup

Hi Brian, It does not look to me that https port is declared in broker configuration. Could you please verify that https port declaration is present in /home/boshea/blt/app/main/core/sfdc/qpid/etc/sfdc-broker-configuration.json? I noticed that you started Broker with Qpid legacy jvm settings fo

Re: [VOTE] Release Apache Qpid JMS 0.37.0

+1 * Verified signatures and checksums * Built and ran tests from source bundle * Ran Qpid Broker-J integration tests on master using staged 0.37.0 artifacts On Fri, 28 Sep 2018 at 18:32, Robbie Gemmell wrote: > > Hi folks, > > I have put together a spin for a 0.37.0 Qpid JMS client release, > p

Re: Building Qpid broker 7.0.6 Java version with OpenJDK 1.8.0_162_x64 fails in BDB Link Store Plug-in tests

Hi Brian, You seems using Azul JVM. I do not have Azul JVM to verify your issue but it could be BDB JE related. I found this post [1] on JE forum where Oracle developer suggested that issue would resolved in JE version 7.6 which is not available yet. Kind Regards, Alex [1] https://community.oracl

RESULT][VOTE] Release Qpid for Java 6.1.7

There were 5 binding +1 votes, and no other votes received. The vote has passed. The voting thread can be found here: https://lists.apache.org/thread.html/9b5f42bb4f18c38dda27ac257773172fb8b2e1603eadaec59b567ce4@%3Cusers.qpid.apache.org%3E I will add the archives to the dist release repo and rele

Re: [Broker-J] HTTP management

Hi Olivier, Please note, that JIRA [1] was raised to track issue with bindings using invalid selectors. The fix is scheduled for inclusion into 7.1. Please fill free to contribute a code for the fix. As for returning 400 instead of 404 when exchange does not exist for a requested operation, you c

Re: [VOTE] Release Qpid for Java 6.1.7

, Oleksandr Rudyy wrote: > > Hi all, > > I built a release candidate for 6.1.7 version of the Qpid for Java. > Please give it a test out and vote accordingly. > > The list of defect fixes can be found in Jira: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=1

[VOTE] Release Qpid for Java 6.1.7

Hi all, I built a release candidate for 6.1.7 version of the Qpid for Java. Please give it a test out and vote accordingly. The list of defect fixes can be found in Jira: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520&version=12343003 The source and binary archives can

[RESULT] [VOTE] Release Apache Qpid JMS AMQP 0-x 6.3.3

There were 5 binding +1 votes, with no other votes received. The vote has passed. The voting thread can be found here: https://lists.apache.org/thread.html/e1c1ac3c9fd6c59eb3e4171a9ab76ebe374f0e57b091a618445e29f4@%3Cusers.qpid.apache.org%3E I will add the archives to the dist release repo and rel

Re: [VOTE] Release Apache Qpid JMS 0.36.0

+1 I performed the following tests: * verified checksums and signatures * built and ran tests from source bundle * ran Qpid Broker-J integration tests on master branch using staged 0.36 artefacts, overridden netty version 4.1.28.Final and profiles java-bdb.1-0/java-mms.1-0 On Wed, 15 Aug 2018 at 1

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

+1 * verified signatures and checksums * built from source bundle * ran Qpid Broker-J integration tests for AMQP 0-9 using maven staging artefacts On Mon, 13 Aug 2018 at 18:22, Oleksandr Rudyy wrote: > > Hi, > > I built a candidate release for version 6.3.3 of Qpid JMS AMQP 0-x. &

[VOTE] Release Apache Qpid JMS AMQP 0-x 6.3.3

Hi, I built a candidate release for version 6.3.3 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.3-RC1/ The maven artifacts are also staged at: https://repository.apache.org/con

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

+1 * verified signatures and checksums * built and ran tests from source bundle * ran Qpid Broker-J integration tests using staged maven artefacts On Fri, 10 Aug 2018 at 21:12, Robbie Gemmell wrote: > > I have put together a spin for a Qpid Proton-J 0.29.0 release, please > test it and vote acco

Re: [Broker-J] derby message store

Hi Olivier, Derby message store works the same as JDBC message store. The JDBC transactions are used underneath to guarantee message persistence. The disposition is sent after the underlying JDBC transactions are committed for both transactional and non-transactional deliveries. Do you have any pr

Re: Content is not available for reading on http management page

Hi, The message headers and message content are not provided by Qpid REST API when non-SSL transport is used due to possibility to carry confidential information which can be intercepted on non-secure channels. As warning message suggests you need to use HTTPS in order to see headers and content.

Re: [DISCUSS] Ending support for Java 7 in Proton-J

+1 On 8 August 2018 at 19:04, Robbie Gemmell wrote: > I think this is probably as much a notice as a discussion, however... > > In a previous mail thread [1] some 20 months ago, I proposed requiring > Java 8 support for some components, particularly the JMS client ahead > of its 0.20.0 release, f

Re: Java Broker (7.0.6) stops delivering queue/consumer messages after 4 GB data transfer

; -- Rob > > On Tue, 7 Aug 2018, 10:44 Oleksandr Rudyy, wrote: > >> Hi Mike, >> >> I will merge Rob's fix into 7.0.x branch for inclusion into 7.0.7 release. >> >> Kind Regards, >> Alex >> >> On 6 August 2018 at 20:03, Dyslin, Mike wro

Re: Java Broker (7.0.6) stops delivering queue/consumer messages after 4 GB data transfer

Hi Mike, I will merge Rob's fix into 7.0.x branch for inclusion into 7.0.7 release. Kind Regards, Alex On 6 August 2018 at 20:03, Dyslin, Mike wrote: > Rob, > > I'm running with your fixed jar file now, and passed the 4GB boundary, > currently at 5.11 GB, so your fix seems to work! > > Thanks

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

+1 * Verified signatures and checksums * Built and ran tests from source bundle with environment variable PN_TRACE_FRM=true * Ran successfully Qpid Broker-J integration tests using proton-j staged artefacts On 2 August 2018 at 18:19, Robbie Gemmell wrote: > I have put together a second spin for

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

+1 * Verified signatures and checksums * Built and ran tests from sources with environment variable PN_TRACE_FRM=true * Ran successfully Qpid Broker-J integration tests using proton-j staged artefacts On 2 August 2018 at 18:20, Robbie Gemmell wrote: > Hi folks, > > I have put together a second s

Re: [Broker-J] Reject overflow policy

gh the graphical > interface... > > Olivier > > -Original Message----- > From: Oleksandr Rudyy > Sent: mardi 31 juillet 2018 15:22 > To: users@qpid.apache.org > Subject: Re: [Broker-J] Reject overflow policy > > Hi Olivier, > > By default, Qpid exchanges dro

Re: [Broker-J] Reject overflow policy

t; I get the same error as you now... > There must have been something wrong with my use case the first time. > Thanks for the help and sorry for the trouble > > Olivier > > -Original Message- > From: Oleksandr Rudyy > Sent: mercredi 4 juillet 2018 14:35 > To: use

Re: [VOTE] Release Apache Qpid JMS 0.35.0

+1 My testing included the following: * verified signatures and checksums * built and ran tests from source bundle * ran Broker-J integration tests using 0.35.0 staging artefacts On 20 July 2018 at 11:10, Robbie Gemmell wrote: > I have put together a spin for a 0.35.0 Qpid JMS client release,

[RESULT] [VOTE] Release Apache Qpid JMS AMQP 0-x 6.3.2

There were 3 binding +1 votes, with no other votes received. The vote has passed. The voting thread can be found here: https://lists.apache.org/thread.html/9a0b4f725e126a875089c4dc9835b6d8a4dc2480c94f114bc383416d@%3Cusers.qpid.apache.org%3E I will add the archives to the dist release repo and rel

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

+1 I tested following: * verified checksums and signatures * built and ran tests from source bundle * using staging artefacts and JMS 0.34.0 ran successfully JMS integration tests against Broker-J On 13 July 2018 at 20:39, Robbie Gemmell wrote: > Hi folks, > > I have put together a spin for a Qpi

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

+1 My testing included the following: * verified checksums and signatures * built and ran tests from sources * using staging artefacts and JMS 0.34.0 ran successfully JMS integration tests against Broker-j On 13 July 2018 at 21:33, Robbie Gemmell wrote: > Hi folks, > > I have put together a sp

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

2018 at 22:50, Oleksandr Rudyy wrote: > Hi all, > > I built a candidate release for version 6.3.2 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/

[VOTE] Release Apache Qpid JMS AMQP 0-x 6.3.2

Hi all, I built a candidate release for version 6.3.2 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.2-RC1/ The maven artifacts are also staged at: https://repository.apache.or

Re: [Broker-J] Reject overflow policy

detailed answer. > I'm using a JMS client (qpid-jms-client 0.11.1) with a non-transacted session > and no specific flags. > For this use case I'm publishing directly in a standard queue. > > Olivier > > -Original Message- > From: Oleksandr Rudyy > S

Re: [Broker-J] Reject overflow policy

Hi Olivier, The broker behaviour for reject policy depends on AMQP protocol in use. With AMQP 1-0 an error "Maximum depth exceeded on 'reject-queue' : current=[count: 11, size: 5458], max=[count: 10, size: -1] [condition = amqp:resource-limit-exceeded]" is reported back as part of broker disposit

Re: [Broker-J] JDBC configuration store with Oracle

D-8214 created. > > Olivier > > -Original Message- > From: Oleksandr Rudyy > Sent: mercredi 27 juin 2018 12:04 > To: users@qpid.apache.org > Subject: Re: [Broker-J] JDBC configuration store with Oracle > > Hi Olivier, > > Please raise an improveme

Re: [Broker-J] JDBC configuration store with Oracle

Hi Olivier, Please raise an improvement JIRA about it. I'll try to look into it. Kind Regards, Alex On 26 June 2018 at 12:33, VERMEULEN Olivier wrote: > Hello, > > I have a problem with the 'JDBC' configuration store when using Oracle. > In this mode the Broker creates a table named > 'QPID_CO

Re: [VOTE] Release Apache Qpid JMS 0.34.0

+1 * verified signatures and checksums * verified licence headers using mvn apache-rat:check' * built and ran tests from source distribution * ran Qpid Broker-J integration tests using staged JMS client 0.34.0 artefacts On 25 June 2018 at 21:11, Robbie Gemmell wrote: > Hi folks, > > I have put

Re: [Broker-J 7.0.3] Memory configuration store and messages recovery

with a Dispatch Router to get the configuration. I am sorry for confusion here. Kind Regards, Alex On 25 June 2018 at 10:51, Rob Godfrey wrote: > Hi Alex, > > On Mon, 25 Jun 2018 at 11:44, Oleksandr Rudyy wrote: > >> Hi Olivier, >> >> An implementation of new no

Re: [Broker-J 7.0.3] Memory configuration store and messages recovery

Hi Olivier, An implementation of new non-persistent config store for the dispatch-router is not on the current Qpid roadmap. You are welcome to contribute such implementation. Basically, you need to implement a new type of VirtualHostNode and new type of DurableConfigurationStore. Potentially, a

[RESULT] [VOTE] Release Apache Qpid Broker-J 7.0.6

There were 5 binding +1 votes and no other votes received. The vote has passed. The voting thread can be found here: https://lists.apache.org/thread.html/ea246ffef25ceb7c38a1eb90230e8e567502b6e80b493814e2514880@%3Cusers.qpid.apache.org%3E I will add the archives to the dist release repo and rele

Re: [VOTE] Release Apache Qpid Broker-J 7.0.6

not able to reproduce it with Qpid Broker-J 7.0.6. * ran successfully apache-rat:check and dependency check * started Broker and ran 'hello world' examples using legacy and new JMS clients On 19 June 2018 at 22:45, Oleksandr Rudyy wrote: > Hi all, > > I created an RC1 built

Re: [VOTE] Release Apache Qpid Broker-J 7.0.6

ribing a 404 situation. > > svn cat > https://dist.apache.org/repos/dist/dev/qpid/broker-j/7.0.6-rc1/apache-qpid-broker-j-7.0.6-src.tar.gz.asc > | head -3 > > > 404 - Repository with ID="orgapacheqpid-1146" not > found > > > > > > On 1

[VOTE] Release Apache Qpid Broker-J 7.0.6

Hi all, I created an RC1 built for a Qpid Broker-J 7.0.6 release. Please give it a test out and vote accordingly. The source and binary bundles can be found at https://dist.apache.org/repos/dist/dev/qpid/broker-j/7.0.6-rc1 The maven artifacts are also staged for now at: https://repository.apache

[RESULT] [VOTE] Release Apache Qpid Broker-J 7.0.5

There were 4 binding +1 votes, and no other votes received. The vote has passed. The voting thread can be found here: https://lists.apache.org/thread.html/692913210b54c66ea3f4a46049ba4d39dbec095c16b4ffe7fda47120@%3Cusers.qpid.apache.org%3E I will add the archives to the dist release repo and rele

Re: Embedded QPID broker-j 6.1.6 - intial configuration, AMQP 1.0 client

e code a while ago and when trying to migrate to 7.0 I > had troubles getting some com.sleepycat.je dependency from our company > Nexus. > > Actually, is the syntax / semantics of virtualHostInitialConfiguration > documented anywhere? > > Regards, > Franta > > > On Wed, Jun 6, 2018 at 11:12

Re: [VOTE] Release Apache Qpid JMS 0.33.0

+1 * built from source distribution and ran all tests * ran Qpid Broker-J integration tests with staged 0.33.0 maven artefacts using profiles java-mms.1-0 and java-bdb.1.0 * verified checksums and signatures On 11 June 2018 at 18:32, Robbie Gemmell wrote: > Hi folks, > > I have put together a

Re: [VOTE] Release Apache Qpid Broker-J 7.0.5 RC2

, Oleksandr Rudyy wrote: > Hi all, > > I created an RC2 built for a Qpid Broker-J 7.0.5 release. > Please give it a test out and vote accordingly. > > The source and binary bundles can be found at > https://dist.apache.org/repos/dist/dev/qpid/broker-j/7.0.5-rc2 > > The maven ar

[VOTE] Release Apache Qpid Broker-J 7.0.5 RC2

Hi all, I created an RC2 built for a Qpid Broker-J 7.0.5 release. Please give it a test out and vote accordingly. The source and binary bundles can be found at https://dist.apache.org/repos/dist/dev/qpid/broker-j/7.0.5-rc2 The maven artifacts are also staged for now at: https://repository.apache

[CANCELLED] [VOTE] Release Apache Qpid Broker-J 7.0.5

The vote is cancelled due to a discovery of another critical defect: https://issues.apache.org/jira/browse/QPID-8207 I will fix the defect and spin another release.

Re: [VOTE] Release Apache Qpid Broker-J 7.0.5

-1 I found another critical defect in evaluation of flow to disk threshold: https://issues.apache.org/jira/browse/QPID-8207 I would like to cancel this vote and spin another RC with a fix for the found defect. On 7 June 2018 at 16:15, Oleksandr Rudyy wrote: > Hi all, > > I have put

[VOTE] Release Apache Qpid Broker-J 7.0.5

Hi all, I have put together a spin for a Qpid Broker-J 7.0.5 release. Please give it a test out and vote accordingly. The source and binary bundles can be found at https://dist.apache.org/repos/dist/dev/qpid/broker-j/7.0.5-rc1 The maven artifacts are also staged for now at: https://repository.ap

Re: Embedded QPID broker-j 6.1.6 - intial configuration, AMQP 1.0 client

Franta, Are there any specific reasons why do you prefer to use version 6.1.6 over 7.0? I would strongly suggest using 7.0 as AMQP 1.0 layer there was significantly reworked and a number of improvements and bug fixes have been implemented. Kind Regards, Alex On 6 June 2018 at 00:55, Oleksandr

Re: Embedded QPID broker-j 6.1.6 - intial configuration, AMQP 1.0 client

Hi Franta, A wiki at [1] illustrates how to embed Qpid Broker-J 7.x. I while ago I attached a couple of examples how to embed 6.x to JIRA [2]. I am not sure how useful they can be. You can define the required queues and exchanges as part of virtual host node attribute "virtualHostInitialConfigura

[RESULT] [VOTE] Release Apache Qpid Broker-J 7.0.4

There were 4 binding +1 votes, 2 non-binding +1 community votes, and no other votes received. The vote has passed. The voting thread can be found here: https://lists.apache.org/thread.html/8d77c031ec176bb8e534d6fb16add8c5b3b9abe881a3e44c74ffabbb@%3Cusers.qpid.apache.org%3E I will add the archives

Re: [VOTE] Release Apache Qpid Broker-J 7.0.4

8 at 14:59, Oleksandr Rudyy wrote: > Hi all, > > I built a release candidate for a Qpid Broker-J 7.0.4. > 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/broker-j/7.0.4-rc1 &

[VOTE] Release Apache Qpid Broker-J 7.0.4

Hi all, I built a release candidate for a Qpid Broker-J 7.0.4. 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/broker-j/7.0.4-rc1 The maven artifacts are also staged for now at: https://repository.apa

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

There were 7 binding +1 votes, with no other votes received. The vote has passed. The voting thread can be found here: https://lists.apache.org/thread.html/308027cf887de69b610c7664d24568e7ba7161049933048f38465622@%3Cusers.qpid.apache.org%3E I will add the archives to the dist release repo and rel

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

using maven staged client artefacts On 15 May 2018 at 12:36, 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://d

Re: [Broker-J] management REST API

-- Rob > > On Tue, 15 May 2018 at 23:15, Oleksandr Rudyy wrote: > >> My apologies, >> >> I completely misread and misinterpreted the method description. >> Somehow I missed *all the bindings*" in my reading :( >> >> The bindingKey is optional here

Re: [Broker-J] management REST API

ire an explicit empty > argument for the empty string case) or we should take bindingKey not being > set as meaning delete all bindings for this destination. > > -- Rob > > On Tue, 15 May 2018 at 17:15, Oleksandr Rudyy wrote: > >> Hi Olivier, >> >> The curr

Re: [Broker-J] management REST API

Hi Olivier, The current description of unbind operation on master and 7.0.x states : Deletes all the bindings matching the given destination and bindingKey As per description the queue binding is deleted only when both destination and binding key are equal to provided destination and bindingKey ac

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

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 are also staged at: https://repository.apache.org/

Re: [VOTE] Release Apache Qpid JMS 0.32.0

+1 I performed the following tests * verified signatures and checksums * built from sources * run Qpid Broker-J integration tests against master using profiles java-mms.1-0 and java-bdb.1-0 mvn clean verify -DskipITs=false -Djava-bdb.1-0 mvn clean verify -DskipITs=false On 30 April 2018 at 14

Re: Broker-J and JMS selector

Hi Oliver, It is a long standing defect. Please check QPID-7642 [1]. Kind Regards, Alex [1] https://issues.apache.org/jira/browse/QPID-7642 On 27 April 2018 at 15:38, VERMEULEN Olivier wrote: > Hello, > > We played a bit with the JMS selector lately and we noticed that when you > specify an i

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

+1 * Verified signatures and checksums * Built and ran tests from source bundle * Ran Qpid Broker-J integration tests with staged maven artefacts On 18 April 2018 at 21:01, Robbie Gemmell wrote: > Hi folks, > > I have put together a second spin for a Qpid Proton-J 0.27.0 release, please > test

[RESULT][VOTE] Release Qpid for Java 6.1.6

There were 3 binding +1 votes, and no other votes received. The vote has passed. The voting thread can be found here: https://lists.apache.org/thread.html/52bb20cc6b9e82795a42130bebd923ddca3ed06f8f9d8820a64fd5af@%3Cusers.qpid.apache.org%3E I will add the archives to the dist release repo and rele

[RESULT] [VOTE] Release Apache Qpid Broker-J 7.0.3

There were 4 binding +1 votes, 1 non-binding +1 community vote, and no other votes received. The vote has passed. The voting thread can be found here: https://lists.apache.org/thread.html/332e5a6910904062fca1035764ff90ca16efd2368cf88f98fa3a56a2@%3Cusers.qpid.apache.org%3E I will add the archives

Re: [VOTE] Release Qpid for Java 6.1.6

" example using JMS AMQP 0-x client On 30 March 2018 at 16:45, Oleksandr Rudyy wrote: > Hi all, > > A bug-fix release candidate for the version 6.1.6 of the Qpid for > Java Components has been created. > > The list of defect fixes can be found in Jira: > https://issue

Re: [VOTE] Release Apache Qpid Broker-J 7.0.3

" example using JMS AMQP 0-x client On 30 March 2018 at 15:40, Oleksandr Rudyy wrote: > Hi all, > > I built a release candidate for a Qpid Broker-J 7.0.3. > Please give it a test out and vote accordingly. > > The source and binary archives can be grabbed from: > https://dis

Re: Building proton from master fails on Red Hat Enterprise Linux Server release 7.3 Maipo with "fatal error: bits/c++config.h: No such file or directory"

at 19:49, Andrew Stitcher wrote: > On Mon, 2018-04-02 at 17:15 +0100, Oleksandr Rudyy wrote: >> Hi Andrew, >> >> In Red Hat Enterprise Linux Server release 7.3 I found file >> /usr/include/c++/4.8.2/i686-redhat-linux/bits/c++config.h which was >> installed as part

Re: Building proton from master fails on Red Hat Enterprise Linux Server release 7.3 Maipo with "fatal error: bits/c++config.h: No such file or directory"

Alex On 2 April 2018 at 16:38, Andrew Stitcher wrote: > On Fri, 2018-03-30 at 10:29 +0100, Oleksandr Rudyy wrote: >> Hi, >> >> As per subject the master proton build fails with the error like >> below: >> >> [ 44%] Building CXX object >> proton-c/bindi

[VOTE] Release Qpid for Java 6.1.6

Hi all, A bug-fix release candidate for the version 6.1.6 of the Qpid for Java Components has been created. The list of defect fixes can be found in Jira: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310520&version=12342163 Please test and vote accordingly. The source and

[VOTE] Release Apache Qpid Broker-J 7.0.3

Hi all, I built a release candidate for a Qpid Broker-J 7.0.3. 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/broker-j/7.0.3-rc1 The maven artifacts are also staged for now at: https://repository.apa

Building proton from master fails on Red Hat Enterprise Linux Server release 7.3 Maipo with "fatal error: bits/c++config.h: No such file or directory"

Hi, As per subject the master proton build fails with the error like below: [ 44%] Building CXX object proton-c/bindings/cpp/CMakeFiles/qpid-proton-cpp.dir/src/binary.cpp.o In file included from /home/alex/qpid-proton/proton-c/bindings/cpp/include/proton/internal/../types_fwd.hpp:31:0,

Re: JMSMessageID differences in JMS 0.30.0 and JMS AMQP 0-x 6.3.0 clients

Hi Bryan, Using 0-91 AMQP client should work as expected. I am not aware about any issue with such approach. The issue you had run with 0-10 amqp client is caused by 0-10 protocol restriction which limits message id types to UUID only. The conversion layer of Broker-J converts the String message

Re: [VOTE] Release Apache Qpid JMS 0.31.0

+1 * Validated signatures and checksums * Built from source and ran the tests * Ran Broker-J master system tests against staged artefacts using profiles java-mms.1-0 and java-bdb.1-0 * Built sample application publishing messages into Broker-J 7.0.3-SNAPSHOT using staged artefacts On 22 March 20

Re: qpid-cpp cmake fails to find proton when PKG_CONFIG_PATH is set to non-standard /lib[64]/pkgconfig

rs in recent days, its not >>> immediately clear to me whether it is one or the other, or both. >>> >>> On 19 March 2018 at 17:15, Oleksandr Rudyy wrote: >>> > Hi, >>> > >>> > Jenkins job Qpid-Broker-J-Python-Test started to fail

Re: What is AMQP 1-0 spec complaint Broker behaviour for deletion of queue with consumers attached?

as rollback only). Kind Regards, Alex [1] https://issues.oasis-open.org/browse/AMQP-140 On 21 March 2018 at 13:46, Alan Conway wrote: > On Tue, Mar 20, 2018 at 9:07 AM, Oleksandr Rudyy wrote: > >> I think that publishing/consuming transactions should not be >> committable af

Re: Broker-J Queue Message persistent override

Hi Brian, A queue attribute 'messageDurability' set to NEVER will stop queue message entries from storing in the message store. Thus, on broker restart the queue entries would be removed. However, queue 'messageDurability' does not affect storing of message content. If you send a persistent messa

<    1   2   3   4   5   >