[RESULT] [VOTE] Release Qpid for Java 6.1.0 (RC2)

There were 5 binding +1 votes, and no other votes received. The vote has passed. Voting thread: http://qpid.2158936.n2.nabble.com/VOTE-Release-Qpid-for-Java-6-1-0-RC2-td7653853.html I will push release artifacts into dist release repo and release the maven staging repo. The website will be update

Re: [VOTE] Release Qpid for Java 6.1.0 (RC2)

Adding my +1 vote I performed the following tests: * Started broker * Using Web Management Console created the following: ** new Virtual Host ** new Queue ** new Queue Binding ** Set preferred timezone and observed that time for log records on memory log viewer was updated in accordance with the t

[VOTE] Release Qpid for Java 6.1.0 (RC2)

Hi folks, Qpid for Java 6.1.0 RC2 is available for testing. The changes against the following JIRAs have been made since RC1: QPID-7352 : [Java Broker] Principal serialisation QPID-7409 : Support preview of maps/list message content QPID-7460 : [Java Broker] Improve performance of the Json Confi

[ANNOUNCE] Apache Qpid for Java 6.0.5 released

The Apache Qpid community is pleased to announce the immediate availability of Apache Qpid for Java 6.0.5. This release incorporates a number of defect fixes and enhancement. The release is available now from our website: http://qpid.apache.org/download.html Binaries are also available via M

[CANCELED][VOTE] Release Qpid for Java 6.1.0

The voting [1] is canceled due to a number of issues found in new features introduced in 6.1.0 RC1 build of Qpid for Java. We are going to spin RC2 build where found issues will be fixed. Kind Regards, Alex [1] http://qpid.2158936.n2.nabble.com/VOTE-Release-Qpid-Java-6-1-0-td7652361.html -

[RESULT] [VOTE] Release Qpid for Java 6.0.5

There were 4 binding +1 votes, and no other votes received. The vote has passed. Voting thread: http://qpid.2158936.n2.nabble.com/Fwd-VOTE-Release-Qpid-Java-6-0-5-td7652349.html I will publish release artifacts into release repositories and I will update web site in 24h after repo mirrors update.

Re: [VOTE] Release Qpid Java 6.0.5

+1 I tested publishing messages with AMQP 1.0 JMS client, receiving them with AMQP 0.10 JMS client and vice versa. I performed smoke test of web management console by creating and binding a queue. On 28 October 2016 at 16:44, Robbie Gemmell wrote: > On 24 October 2016 at 11:52, Oleksa

Re: [VOTE] Release Qpid Java 6.1.0

t;> * https://issues.apache.org/jira/browse/QPID-7469 >> * https://issues.apache.org/jira/browse/QPID-7470 >> * https://issues.apache.org/jira/browse/QPID-7471 >> * https://issues.apache.org/jira/browse/QPID-7474 >> * https://issues.apache.org/jira/browse/QPID-7352 >>

[VOTE] Release Qpid Java 6.1.0

Hi all, A release candidate build for the next 6.1.0 release of the Qpid Java Components is available for testing. The release introduces a number of new features to Qpid Broker for Java and contains hundreds of bug fixes and improvements. Please, check JIRA for the full list of changes and their

Fwd: [VOTE] Release Qpid Java 6.0.5

Hi all, A release candidate for the next 6.0.5 release of the Qpid Java Components has been created. A number of important defect fixes and improvements have been made in this release. The list of changes can be found in Jira: https://issues.apache.org/jira/issues/?jql=project%20%3D%20QPID%20AND%

Re: [Qpid Java Broker 6.0.x] Random failure in queue creation/deletion using REST calls

Adel, I simply changed the log level to ALL for logging rule Qpid (org.apache.qpid.*) in logfile logger. That enables all possible Qpid logging. Alternately, you can just add new logging rule to enable debug logging for logger "org.apache.qpid.server.management.plugin.filter.LoggingFilter". Potent

Re: [Qpid Java Broker 6.0.x] Random failure in queue creation/deletion using REST calls

Hi Adel, I looked into an issue you had reported. I ran your sample application attached to the JIRA QPID-7420 and found that every time when application fails it sends 2 similar requests: first one is handled by the broker successfully and the other one fails because the work is already performed

Re: [VOTE] Release Qpid Java 6.0.4 (RC1)

+1 I successfully performed the following tests with 6.0.4 broker and client bundles in my Fedora 23 based environment * started broker from binary bundle * created queue using web management console * sent/received messages into/from queue using client bundle Hello/Drain/Spout examples * publishe

Re: [Java Broker- 6.0.0] Unable to close zombie connections from Web Management console

Hi Adel, It looks like you have run into an issue reported at [1]. The fix will be included into 6.0.4. We are in process of fixing other issues scheduled for 6.0.4. If everything will go as planned, Qpid 6.0.4 could be released next week or week after. Kind Regards, Alex [1] https://issues.apac

[ANNOUNCE] Apache Qpid Java 6.0.3 released

The Apache Qpid community is pleased to announce the immediate availability of Apache Qpid Java 6.0.3. This release addresses CVE-2016-3094, CVE-2016-4432 vulnerabilities and incorporates a number of defect fixes and enhancements. The release is available now from our website: http://qpid.apa

[RESULT] [VOTE] Release Qpid Java 6.0.3 (RC3)

There were 7 binding +1 votes, and no other votes received. The vote has passed. Voting thread: http://qpid.2158936.n2.nabble.com/VOTE-Release-Qpid-Java-6-0-3-RC3-td7644268.html I am going to publish release artifacts into dist release repo and maven repo. The website will be updated later after

Re: [VOTE] Release Qpid Java 6.0.3 (RC3)

protocol and receiving them with legacy client using AMQP 0-10 protocol. Kind Regards, Alex On 19 May 2016 at 12:04, Oleksandr Rudyy wrote: > Hi all, > > I have built RC3 for 6.0.3 Qpid Java Components. > > The following changes have been made since RC2: > QPID-6096 : j

[VOTE] Release Qpid Java 6.0.3 (RC3)

Hi all, I have built RC3 for 6.0.3 Qpid Java Components. The following changes have been made since RC2: QPID-6096 : java broker doesn't indicate that port is already in use QPID-7255 : Support del

Re: [VOTE] Release Qpid Java 6.0.3 (RC2)

though :-) > > -- Rob > > On 18 May 2016 at 13:57, Oleksandr Rudyy wrote: > >> Hi, >> I believe that it would be better to release 6.0.3 with fixes in >> QPID-6096, QPID-7268, QPID-72689. >> >> Additionally, I would like to suggest an inclusion of QPID

Re: [VOTE] Release Qpid Java 6.0.3 (RC2)

Hi, I believe that it would be better to release 6.0.3 with fixes in QPID-6096, QPID-7268, QPID-72689. Additionally, I would like to suggest an inclusion of QPID-7255 ( Support delivery delay). It seems that finishing and releasing of 6.1 will take some time and having a released version with this

[VOTE] Release Qpid Java 6.0.3 (RC2)

Hi folks, I built Qpid Java 6.0.3 RC2. The following changes have been made since RC1: QPID-7260 : apache-release fails under JDK 1.8 QPID-7265 : migrate the AMQP 0-10 JMS client docs out of the ol

Re: [VOTE] Release Qpid Java 6.0.3 (RC1)

Hi Gordon, Java broker has a context variable broker.failStartupWithErroredChild (set to false by default) to control whether broker should fail or continue running on any issue on startup. If you start broker using $BROKER_HOME/bin/qpid-server -prop broker.failStartupWithErroredChild=true it shou

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

+1 On 20 April 2016 at 01:03, 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 it

[ANNOUNCE] Apache Qpid Java 6.0.2 released

The Apache Qpid community is pleased to announce the immediate availability of Apache Qpid Java Components 6.0.2 This release incorporates a number of defect fixes and enhancement. The release is available now from our website: http://qpid.apache.org/download.html Binaries are also available

Re: [RESULT] [VOTE] Release Qpid Java 6.0.2 (RC1)

My apologies, I provided an URL to voting thread for 6.0.1 RC3 in the result voting email for 6.0.2 RC1. The correct voting thread URL is: http://qpid.2158936.n2.nabble.com/VOTE-Release-Qpid-Java-6-0-2-RC1-td7641806.html Kind Regards, Alex On 18 April 2016 at 13:48, Oleksandr Rudyy wrote

[RESULT] [VOTE] Release Qpid Java 6.0.2 (RC1)

There were 5 binding +1 votes, and no other votes received. The vote has passed. Voting thread: http://qpid.2158936.n2.nabble.com/VOTE-Release-Qpid-Java-6-0-1-RC3-td7638867.html I am going to publish release artifacts into dist release repo and maven repo. In 24h after that I will update web sit

Re: [VOTE] Release Qpid Java 6.0.2 (RC1)

tions to > include the rename step. In the medium term, when the Java Broker is > split from the (legacy) JMS clients in to separate, we can get this > right. > > [1] > https://cwiki.apache.org/confluence/display/qpid/Releasing+Qpid+Java+Components > > On 15 April 2016 at 11:

Re: [VOTE] Release Qpid Java 6.0.2 (RC1)

I made the following checks: 1) Verified pgp signatures against public keys in http://www.apache.org/dist/qpid/KEYS. Keith's signature is not there and should be appended manually. 2) Source bundle is named qpid-java-build-6.0.2.tar.gz but the site generating script(s) expect(s) it to be named qpid

Re: Max Frame Size for Java Broker

Hi, Could you please provide your client and corresponding broker logs from your test where broker does not respect the frame size set in client TuneOk? Please, provide broker logs with debug log level. You can change broker log level to debug by opening Web Management Console and setting log lev

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

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

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

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 toggle to enable/disable it but does not specify how toggle is implemented. In suggested changes for legacy JMS client

Re: Welcome Ganesh Murthy as an Apache Qpid committer

Welcome, Ganesh! Alex On 1 March 2016 at 17:30, 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 > > -

[ANNOUNCE] Apache Qpid Java Broker and JMS Client for AMQP 0-8..0-10 version 6.0.1 is released

The Apache Qpid community is pleased to announce the immediate availability of version 6.0.1 for Apache Qpid Java Broker and JMS Client for AMQP 0-8...0-10. This release incorporates a number of defect fixes and enhancements. The release is available now from our website: http://qpid.apache.o

[RESULT] [VOTE] Release Qpid Java 6.0.1

There were 5 binding and 1 non-binding +1 votes, and no other votes received. The vote has passed. Voting thread: http://qpid.2158936.n2.nabble.com/VOTE-Release-Qpid-Java-6-0-1-RC3-td7638867.html I am going to publish release artifacts into dist release repo and maven repo. After that I will upda

Re: [VOTE] Release Qpid Java 6.0.1 (RC3)

There were 5 binding and 1 non-binding +1 votes, and no other votes received. The vote has passed. Kind Regards, Alex On 22 February 2016 at 11:51, Oleksandr Rudyy wrote: > Hi everyone, > > I created a new 6.0.1 RC3 build containing a fix for a blocker: > > QPID-6817 - [Java Br

Re: [VOTE] Release Qpid Java 6.0.1 (RC3)

+1 On 22 February 2016 at 11:51, Oleksandr Rudyy wrote: > Hi everyone, > > I created a new 6.0.1 RC3 build containing a fix for a blocker: > > QPID-6817 - [Java Broker] On abrupt connection close from client side when > Broker is delivering messages to consumer, the delivering

Re: [VOTE] Release Qpid Java 6.0.1 (RC2)

filename doesnt match the content currently and > doing so won't need a rebuild. > > Robbie > > On 23 February 2016 at 12:46, Oleksandr Rudyy wrote: >> Hi >> >> I just would like to clarify that QPID-7091 is not a blocker for >> 6.0.1. We might fix it

Re: [VOTE] Release Qpid Java 6.0.1 (RC2)

Hi I just would like to clarify that QPID-7091 is not a blocker for 6.0.1. We might fix it in one of the following releases. Kind Regards, Alex On 23 February 2016 at 10:17, Oleksandr Rudyy wrote: > Hi Robbie, > > I apologize for not canceling RC2 vote immediately after we decide

Re: [VOTE] Release Qpid Java 6.0.1 (RC2)

Hi Robbie, I apologize for not canceling RC2 vote immediately after we decided to spin RC3. Thanks for reporting the issue with inconsistent src bundle name. It was not intentional change. I raised a JIRA QPID-7091 to fix that. Kind Regards, Alex On 22 February 2016 at 11:57, Robbie Gemmell wro

[VOTE] Release Qpid Java 6.0.1 (RC3)

Hi everyone, I created a new 6.0.1 RC3 build containing a fix for a blocker: QPID-6817 - [Java Broker] On abrupt connection close from client side when Broker is delivering messages to consumer, the delivering messages might not be released as part of close in some unlucky circumstances Please t

Re: [VOTE] Release Qpid Java 6.0.1 (RC2)

Hi, The vote is canceled due to found blocker QPID-6817. I built 6.0.1 RC3 with a fix for QPID-6817. Please, test it and vote again in 6.0.1 RC3 voting thread. I am sorry for inconveniences caused by cancellation. Kind Regards, Alex -

[VOTE] Release Qpid Java 6.0.1

Hi everyone, I have created 6.0.1 release candidate for Qpid Java Components. A number of bug fixes and enhancements have been made in 6.0.1 (52 in total). Please, check JIRA system for details: https://issues.apache.org/jira/issues/?jql=project%20%3D%20QPID%20AND%20fixVersion%20%3D%20qpid-java-6

[VOTE] Release Qpid Java 6.0.1

Hi everyone, I have just created 6.0.1 release candidate for Qpid Java Components. A number of bug fixes and enhancements have been made in 6.0.1 (52 in total). Please, check JIRA system for details [1]. The release artifacts are available from maven staging repository at [2] and development stag

Re: [Proposal] Roadmap for ending Java 7 support for the Java Broker and AMQP 0-x client

+1 to Robs suggestions On 11 February 2016 at 15:12, Rob Godfrey wrote: > All, > > about 2 years ago we discussed the roadmap for ending support for Java 6 > [1]. In April it will be one year since Oracle ceased public support for > Java 7. Towards the end of this year (hopefully) Java 9 will b

Re: Problem with establishing TLS1.1/TLS1.2 connection between cpp client and java broker with disabled TLS1.0 on broker side

client to use TLSv1.2/TLSv1.1 with openssl 1.0.1e-fips? Thanks, Alex On 29 December 2015 at 12:40, Oleksandr Rudyy wrote: > Hi, > > TLSv1 was disabled on Java Broker as part of QPID-6938. > > After that trunk cpp client fails to establish TLS connection with Java > Broker. >

Problem with establishing TLS1.1/TLS1.2 connection between cpp client and java broker with disabled TLS1.0 on broker side

Hi, TLSv1 was disabled on Java Broker as part of QPID-6938. After that trunk cpp client fails to establish TLS connection with Java Broker. $ openssl version OpenSSL 1.0.1e-fips 11 Feb 2013 On client side I see the following in the logs: ./hello_world localhost:35671 'hello-world ; { create: a

[ANNOUNCE] Apache Qpid Java Components 6.0.0 released

The Apache Qpid community is pleased to announce the immediate availability of Apache Qpid Java Components 6.0.0. Qpid Java 6.0 release brings with it the following headline changes: - Fully reimplemented AMQP IO layer utilising Java NIO Improved messaging performance - messages kept in direc

[RESULT] [VOTE] Release Qpid Java Components 6.0.0

There were 5 binding and 1 non-binding +1 votes, with no other votes received. The vote has passed. I am going to publish release artifacts into dist release repo and maven repo. After that I will update web site. Kind Regards, Alex --

Re: [VOTE] Release Qpid Java Components 6.0.0

This vote is now closed. I will publish results in separate email. Kind Regards, Alex - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mail: users-h...@qpid.apache.org

Re: [VOTE] Release Qpid Java Components 6.0.0

+1 On 3 December 2015 at 15:06, Oleksandr Rudyy wrote: > Hi folks, > > I would like to initiate new voting to release Qpid Java Components 6.0.0 > RC5 as the final 6.0.0. > > Maven release artifacts are available from maven staging repo at: > https://repository.apache.org

[VOTE] Release Qpid Java Components 6.0.0

Hi folks, I would like to initiate new voting to release Qpid Java Components 6.0.0 RC5 as the final 6.0.0. Maven release artifacts are available from maven staging repo at: https://repository.apache.org/content/repositories/orgapacheqpid-1056 Source and binary bundles are available from dev sta

Qpid java 6.0.0 RC5 is available

Hi all, I produced Qpid java 6.0.0 RC5 build. Maven artifacts are available from maven staging repo at: https://repository.apache.org/content/repositories/orgapacheqpid-1056 Source and binary bundles are available from dev staging area at: https://dist.apache.org/repos/dist/dev/qpid/java/6.0.0-rc

Re: [VOTE] Release Qpid Java Components 6.0.0

Hi all, I am canceling this voting as we decided to build RC5 to include fixes for QPID-6926 and QPID-6928. Thanks a lot for testing and reporting issues with the RC4. Kind Regards, Alex On 3 December 2015 at 11:06, Rob Godfrey wrote: > Does the broker put the full stack trace of the NullPoint

Re: [RFI] Request for inclusions in Qpid Java 6.0.0

Rob, Both issue fixes (QPID-6926 , QPID-6928) are approved for inclusion into 6.0 Kind Regards, Alex On 3 December 2015 at 11:55, Rob Godfrey wrote: > Alex, > > In his testing of RC4, Gordon found one issue which is a regression since > 0.32 and another issue where a NullPointerException is thr

Re: [VOTE] Release Qpid Java Components 6.0.0

2 December 2015 at 13:19, Robbie Gemmell wrote: > On 2 December 2015 at 12:58, Robbie Gemmell > wrote: > > On 2 December 2015 at 10:51, Oleksandr Rudyy wrote: > >> Hi all, > >> > >> I have produced 6.0.0 RC4 build and would like to initiate voting to >

[VOTE] Release Qpid Java Components 6.0.0

Hi all, I have produced 6.0.0 RC4 build and would like to initiate voting to release Qpid Java Components 6.0.0 RC4 as the final 6.0.0. The release artifacts are available from maven staging repo at: https://repository.apache.org/content/repositories/orgapacheqpid-1055 If you want to test it out

Qpid java 6.0.0 RC4 is available

Hi everyone, After detection of couple issues with RC3 build I merged the fixes into 6.0.x branch and produced Qpid java 6.0.0 RC4. It is available from maven staging repo at: https://repository.apache.org/content/repositories/orgapacheqpid-1055 RC 4 contains the following changes since RC3: ht

Re: Qpid java 6.0.0 RC3 is available

ult. > > Hopefully this will be last of the changes. > > > > > On 1 December 2015 at 14:04, Oleksandr Rudyy wrote: > >> Hi folks, >> Qpid java 6.0.0 RC3 is now available from maven staging repo: >> >> https://repository.apache.org/content/repositories/orgapacheqp

Qpid java 6.0.0 RC3 is available

Hi folks, Qpid java 6.0.0 RC3 is now available from maven staging repo: https://repository.apache.org/content/repositories/orgapacheqpid-1054 This build is signed and versioned for release. I am going to start voting process for 6.0.0 release soon after sending this email. RC 3 contains the foll

Re: Qpid java 6.0.0 RC2 is available

Fix defect causing error during edit of > authentication provider > > Fixes an issue preventing the edit of the authentication provider shipped > within default configuration. UI change only. > Code change by me, reviewed by you. > > > > > > > > On 26 November

Qpid java 6.0.0 RC2 is available

Hi, Qpid java 6.0.0 RC2 is available for testing from Nexus staging repository [1]. I performed smoke testing by starting the broker and running Hello/Spout/Drain examples. No issue is found. Hopefully, next week we can start voting. Kind Regards, Alex [1] https://repository.apache.org/conten

Qpid java 6.0.0 RC1 is available

Hi everyone, I created a branch [1] for 6.0.x Qpid java components releases, bumped trunk version to 6.1.0-SNAPSHOT and built 6.0.0 RC1 version of Qpid java Components from RC1 tag [2]. All release artifacts are available from Nexus staging repository [3]. Please, fill free to give a try to the 6

Re: Welcome Lorenz Quack as a Qpid committer

+1 Welcome, Lorenz. On 9 October 2015 at 20:26, Robbie Gemmell wrote: > The Qpid PMC have voted to grant commit rights to Lorenz Quack in > recognition of his contributions to the project. > > Welcome, Lorenz! > > Robbie > > - >

Re: Qpid java 6.0.0 alpha is available

Hi guys, We have to postpone the beta as we are currently investigating performance issues. As soon as we resolve them, we will cut the branch and do a beta build. Hopefully, that will be accomplished during the following week. If not, we will provide another notice about the delay. Kind Regards,

Re: WELCOME to users@qpid.apache.org

n 1 October 2015 at 23:42, Oleksandr Rudyy wrote: > > Hi Ram, > > > > Your Broker virtual host nodes configuration looks good. Could you > > please clarify what exactly error message you are getting on the > > client after you created virtual host and nodes? > >

Re: WELCOME to users@qpid.apache.org

Hi Ram, Your Broker virtual host nodes configuration looks good. Could you please clarify what exactly error message you are getting on the client after you created virtual host and nodes? I noticed that in your connection string you explicitly specified PLAIN sasl mechanism (url=amqp://guest:***

Qpid java 6.0.0 alpha is available

Hi folks, I prepared an alpha build of Qpid java components for version 6.0.0 (qpid-java-6.0.0) from trunk revision 1705736. The 6.0.0 alpha artifacts are available from Nexus staging repo at: https://repository.apache.org/content/repositories/orgapacheqpid-1045/ I performed some smoke testing of

Re: Proposing qpid-java release soon

Hello all, I am going to perform a release of new version of Qpid java components. Following our previous discussion about versioning of Qpid components, the new version for Qpid java components will be 6.0. Here are approximate dates for the release: 14 August: Alpha 21 August: Beta 28 August:

Re: [VOTE] Release Qpid 0.32

My votes (all +1) are inline below. I performed smoke tests of java broker and java clients by starting broker and executing the examples from 0.10 and 1.0 clients. They worked fine to me. Kind Regards, Alex On 13 March 2015 at 15:45, Justin Ross wrote: > Hi, folks. As with 0.30, we are voting

Re: 0.32 release update - RC is available

Justin, I tested 0.32 RC java broker and java JMS clients by starting the broker and running Hello/Spout/Drain examples from 0.8/0.9.x/0.10 JMS client and Hello example from 1.0 JMS client. They worked fine for me. No issue is found. Additionally I tested web management console operations like crea

Re: handling old Subversion contents after migrations to Git

+1 for option 3 On 9 March 2015 at 16:24, Robbie Gemmell wrote: > Hi all, > > As you probably know, we migrated the Proton and new JMS client code > to Git repositories last year. As part of the process the old > locations within the Subversion repo were frozen read-only and left in > place. > >

Re: Java Broker 0.28 HA Configuration

Hi Mark, Please change message store class org.apache.qpid.server.store.berkeleydb.BDBHAMessageStore and restart your broker. in your configuration you specified store of type org.apache.qpid.server.store.berkeleydb.BDBMessageStore which is not HA store. Kind Regards, Alex On 11 September 2014

Request for inclusion into 0.30

Hi Justin, I would like to request an inclusion of Java Broker BDB HA security fix ( committed into trunk under revision https://svn.apache.org/r1620882 and documented in QPID-6048) into 0.30 . We discovered a bug with an intruder protection for BDB HA solution implemented as part of QPID-5867/QP

Re: How to turn off pre-fetched when browse LVQ

Hi, The maximum prefetch value is set to 500 by default in Qpid JMS client for AMQP 0.10 and 0.8/0.9.x protocols. You cannot turn it off by you can set it to 1 or any other value. The max prefetch value can be set either as a connection URL option or as JVM setting. Please, read [1] or [2] for de

Re: Coaxing an error message out of qpid-cpp - unable to connect

Hi Graham, The JMS client exception stack trace indicates that you are using AMQP 1.0 JMS client with 0.18 Broker which does not speak AMQP 1.0. The support for AMQP 1.0 was introduced in 0.20 version of Qpid cpp broker. 0.18 Broker supports only AMQP 0.10. You can use Qpid JMS Client which speak

Re: [VOTE] Release Qpid 0.24

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

Re: Qpid JMS client side failover with broker federation

Hi Rajib, Your original connection URL with cyclecount specified as a failover option is correct and my suggestion about changing the URL to specify cyclecount as a top level option was wrong. I do apologize for a misleading answer. Kind Regards, Alex On 8 July 2013 10:54, Oleksandr Rudyy

Re: Qpid JMS client side failover with broker federation

Hi Rajib, In your producer and consumer URLs you should specify the failover and cyclecount arguments as 2 separate arguments like in the example below: amqp://guest:guest@clientid/? failover='roundrobin'&cyclecount='2'&brokerlist='tcp://localhost:5672?retries='2'&connectdelay='1000';tcp://localh

Re: Website update 2

t 6:57 PM, Oleksandr Rudyy wrote: > > Hi Justin, > > > > The new version looks really nice. Well done. > > However, I got a couple of minor comments. > > > > General remarks: > > > > I do not know if it is me (may be I am getting older and more > con

Re: Website update 2

Hi Justin, The new version looks really nice. Well done. However, I got a couple of minor comments. General remarks: I do not know if it is me (may be I am getting older and more conservative :) ) but I would decrease slightly the size of the fonts. They look bigger than I get used to. Front pa

Re: How to create a fanout exchange with the Java broker

Hi Jeremy, You need to add into a virtual host configuration an exchange configuration like in the example below: test ... fanout test.fanout ... my-queue

Re: Comparing two JMS Destinations created using address strings.

Hi Rajith, I should clarify that on adding a comment about comparing subjects of destinations I meant topic destinations. Indeed, it does not make sense to compare subjects in destinations for xml exchanges, header exchanges and queues. However, it seems not right for me to not compare subject fo

Re: how to set static binding (routingkeys) config for Java broker?

Hi Tom, qpid-config does not work with java broker. You can configure your queues/exchanges/bindings on java broker in virtualhost.xml or create them with JMX client like jconsole, qpid management console or rest management client like qpid web management console. You need to configure a persist

Re: Client-side Failover Logic

Hi Lance, Could you please provide more details about what you are doing? What brokers do you use? java or c++ What is your connection URL? Have you tried to reproduce the issue with the latest version of client? You can get 0.22 snapshot client build from: https://repository.apache.org/content/r

Re: SSL Client Authentication in Java broker

Hi Jakub, You suggesting is quite interesting and it would be beneficial for Qpid project if you could raise a JIRA and attach a patch. You might already noticed that we have changed the broker configuration model and removed xml configuration. At the moment, the only supported configuration for

Re: Federation with Java Broker?

Hi Jeremy, Java broker does not currently support federation. It is something we will look to implement in future after adding of amqp 1.0 support based on Qpid proton-j amqp 1.0 library and progressing work on 'global addressing' in conjunction with the OASIS AMQP technical committee. Kind Regar

Re: Count number of messages

Hi Mat, Could you please clarify what do you mean under "messages handled by all the queues at any given time"? Is it the total number of messages received by the queues, or the total number of messages hold by the queues or messages receive/delivery rates? If any of the above, the easiest way

Re: C++ clients unable to communicate with Java broker

Hi, Can you change java broker log level to debug and provide the broker logs for c++ client connect? You need to change in ${QPID_HOME}/etc/log4j.xml the following logger configuration By default, the log level is set to "warn". Also, could you try to run spout/drain examples by spe

Re: How to configure JMS QPID client application to log on windows event viewer

Hi Hamid, I beleive you can use Log4j NTEventLogAppender to apped logs into windows event log system. See http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/nt/NTEventLogAppender.html The NT Event Viewer relies on message resource DLLs to properly view an event message. The NTEventLogA

Re: Evaluation of requirements

Hi Holger, The selector expression you have provided in your post is correct and should work with Qpid JMS client. I suspect that in your java code you specified wrong quotes. Could you please check in you code that standard ACII single quotes are used in a selector expression? Kind Regards, Al

Re: stopping a queue from being exclusive

Hi Christopher, What is the version of your broker? In case if broker version >= 0.16, I found so far 2 scenarios leading to these issue: 1) queue was created as exclusive, consumer subscribed, and exclusivity flag was reset through JMX while consumer was still present 2) queue was created as

Re: Erlang client for Qpid C++ Broker

Hi Sergey, You cannot use 0.9.1 amqp client with broker supporting only 0.10 amqp protocol. Java Qpid Broker supports both 0.10 and 0.9.1 protocols. You can publish messages with Erling client into Qpid Java Broker (or RabitMQ broker) and use Qpid java client to consume messages from that broker

Re: qpid Java client keeps sending messages even if underlying session/connection does not exist

e, > On the flip side, If you select sync_publish it will affect performance > quite a bit. > > Rajith > > On Mon, May 14, 2012 at 10:28 AM, Oleksandr Rudyy wrote: > >> Hi Shyamal, >> >> By default, MessageProducer#send operation is asynchronous, i.e. a >>

Re: qpid Java client keeps sending messages even if underlying session/connection does not exist

Hi Shyamal, By default, MessageProducer#send operation is asynchronous, i.e. a message is put on a wire and producer does not wait for the broker confirmation. You can make this operation synchronous by setting JVM system property -Dsync_publish=all or -Dsync_publish=persistent or through connect

Re: Jave Client with C++ Broker - Messages in Queue-size?

Hi, You can get number of messages on a queue by invoking AMQSession#getQueueDepth(AMQDestination) like following Session myJMSSession = ... Desionation myJMSDestination = .. long queueDepth = ((AMQSession)myJMSSession).getQueueDepth(((AMQDestination)myJMSDestination)); Pls, be aware that this m

Re: QPID java client and automatic queue creation

Hi Sergey, You can stop java client from creating queues and exchanges automatically by using JVM settings -Dqpid.declare_exchange=false and -Dqpid.declare_queues=false. On trying to publish or receive messages into/from non-existing exchanges/queues exceptions should be thrown. Kind Regards, A

<    1   2   3   4   5