Re: [VOTE] Release Apache Qpid proton-dotnet 1.0.0-M10 (RC1)

+1 * Verified the signature and checksum files * Verified LICENCE and NOTICE files in archives * Verified source license headers by './build.sh rat' * Built from source and ran the test suite using the './build.sh test' command (dotnet 8.0.103, Ubuntu 22.04.2) Tomas On 2024/04/08 23:04:24

Re: [VOTE] Release Apache Qpid protonj2 1.0.0-M20

+1 * Verified the signature and checksum files * Verified LICENCE and NOTICE files in archives * Verified source license headers by 'mvn apache-rat:check' * Built from source and ran tests (mvn clean install) on OpenJDK Java 11 (11.0.21), OpenJDK Java 17 (17.0.9) and OpenJDK Java 21 (21.0.2) on

[ANNOUNCE] Apache Qpid Broker-J 9.2.0 released

The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache Qpid Broker-J 9.2.0. This is the latest release of pure java implementation of messaging broker supporting the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464,

[RESULT][VOTE] Release Qpid Broker-J 9.2.0 (RC4)

There were 4 binding +1 votes and no other votes received. The vote has passed. I will add the files to the dist release repo and release the maven staging repo shortly, updating the website and announcing after the release has had time to sync to the CDN and maven central. Regards, Tomas

Re: [VOTE] Release Qpid Broker-J 9.2.0 (RC4)

and received messages using Qpid JMS Client Tomas On 2024/02/08 10:49:38 Tomas Vavricka wrote: > Hi all, > > I built release artifacts for Qpid Broker-J version 9.2.0 RC4. > Please, give them a test out and vote accordingly. > > The source and binary archives can be found at: > ht

[VOTE] Release Qpid Broker-J 9.2.0 (RC4)

Hi all, I built release artifacts for Qpid Broker-J version 9.2.0 RC4. Please, give them a test out and vote accordingly. The source and binary archives can be found at: https://dist.apache.org/repos/dist/dev/qpid/broker-j/9.2.0-rc4/ The maven artifacts are also staged at:

[CANCELLED][VOTE] Release Qpid Broker-J 9.2.0 (RC3)

The vote is cancelled due to the issue with VirtualHost creation. I will cut a new release candidate for voting when issues will be fixed. - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands,

Re: [VOTE] Release Qpid Broker-J 9.2.0 (RC3)

se -DskipITs=false) using profiles java-mms.1-0 / > > java-bdb.1-0 / java-dby.1-0 as well as java-mms.0-10 / java-bdb.0-10 / > > java-dby.0-10 > > - Started broker and created / deleted a queue via web management console > > (JDK 17) > > > > On Wed, 7 Feb 2024

Re: [VOTE] Release Qpid Broker-J 9.2.0 (RC3)

binary on JDK 11, created queues/exchanges/ports/... via REST API * sent and received messages using Qpid JMS Client Tomas On 2024/02/06 12:52:21 Tomas Vavricka wrote: > Hi all, > > I built release artifacts for Qpid Broker-J version 9.2.0 RC3. > Please, give them a test out and vote

[VOTE] Release Qpid Broker-J 9.2.0 (RC3)

Hi all, I built release artifacts for Qpid Broker-J version 9.2.0 RC3. Please, give them a test out and vote accordingly. The source and binary archives can be found at: https://dist.apache.org/repos/dist/dev/qpid/broker-j/9.2.0-rc3/ The maven artifacts are also staged at:

[CANCELLED][VOTE] Release Qpid Broker-J 9.2.0 (RC2)

The vote is cancelled due to the issues with configuration upgrade. I will cut a new release candidate for voting when issues will be fixed. - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands,

[VOTE] Release Qpid Broker-J 9.2.0 (RC2)

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

[CANCELLED][VOTE] Release Qpid Broker-J 9.2.0

The vote is cancelled due to the issues with configuration upgrade. I will cut a new release candidate for voting when issues will be fixed. - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands,

Re: [VOTE] Release Qpid Broker-J 9.2.0

he expected behaviour of > the change also really isnt clear. > > On Wed, 31 Jan 2024 at 12:02, Tomas Vavricka wrote: > > > > Hi all, > > > > I built release artifacts for Qpid Broker-J version 9.2.0 RC1. > > Please, give them a test out and vote accordingly. >

[VOTE] Release Qpid Broker-J 9.2.0

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

Re: [VOTE] enroll Proton and Dispatch in Packit-as-a-Service CI offering from Fedora

+1 On 2024/01/12 16:11:01 Jiri Daněk wrote: > I'd like to enable Packit-as-a-Service ( > https://github.com/marketplace/packit-as-a-service) for Qpid Proton and > Qpid Dispatch GitHub repositories, so that every new PR gets tested on > Fedora infrastructure (latest released Fedora and Fedora

Re: [VOTE] Release Apache Qpid protonj2 1.0.0-M19 (RC1)

+1 * Verified the signature and checksum files * Verified LICENCE and NOTICE files in archives * Verified source license headers by 'mvn apache-rat:check' * Built from source and ran tests (mvn clean install) on OpenJDK Java 11 (11.0.21) and OpenJDK Java 17 (17.0.9) on Ubuntu 22.04.2 Regards,

Re: [VOTE] Release Apache Qpid protonj2 1.0.0-M18

+1 * Verified the signature and checksum files * Verified LICENCE and NOTICE files in archives * Verified source license headers by 'mvn apache-rat:check' * Built from source and ran tests (mvn clean install) on OpenJDK Java 11 (11.0.20.1) and OpenJDK Java 17 (17.0.8.1) on Ubuntu 22.04.2

Re: [VOTE] Release Apache Qpid JMS 2.5.0

+1 * Verified the signature and checksum files * Verified LICENCE and NOTICE files in archives * Verified source license headers by 'mvn apache-rat:check' * Built from source and ran tests (mvn clean install) on OpenJDK Java 11 (11.0.20.1) and OpenJDK Java 17 (17.0.8) on Ubuntu 22.04.2 Regards,

Re: [VOTE] Release Apache Qpid JMS 1.11.0

+1 On 2023/10/30 08:41:04 Tomas Vavricka wrote: > * Verified the signature and checksum files > * Verified LICENCE and NOTICE files in archives > * Verified source license headers by 'mvn apache-rat:check' > * Built from source and ran tests (mvn clean install) on OpenJDK Java 11

Re: [VOTE] Release Apache Qpid JMS 1.11.0

* Verified the signature and checksum files * Verified LICENCE and NOTICE files in archives * Verified source license headers by 'mvn apache-rat:check' * Built from source and ran tests (mvn clean install) on OpenJDK Java 11 (11.0.20.1) and OpenJDK Java 17 (17.0.8) on Ubuntu 22.04.2 Regards,

[ANNOUNCE] Apache Qpid Broker-J 9.1.0 released

The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache Qpid Broker-J 9.1.0. This is the latest release of pure java implementation of messaging broker supporting the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464,

[RESULT][VOTE] Release Qpid Broker-J 9.1.0 (RC2)

There were 3 binding +1 votes, 1 non-binding +1 vote, and no other votes received. The vote has passed. I will add the files to the dist release repo and release the maven staging repo shortly, updating the website and announcing after the release has had time to sync to the CDN and maven

Re: [VOTE] Release Qpid Broker-J 9.1.0 (RC2)

-0, java-dby.0-10, java-dby.0-9-1 and java-dby.0-9 on JDK 11 * started Qpid Broker-J from binary on JDK 11, created queues/exchanges/ports/... via REST API * sent and received messages using Qpid JMS Client Tomas On 2023/08/25 10:10:02 Tomas Vavricka wrote: > Hi all, > > I buil

[VOTE] Release Qpid Broker-J 9.1.0 (RC2)

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

[CANCELLED][VOTE] Release Qpid Broker-J 9.1.0

The vote is cancelled due to the issue with the BDB store upgrade from version 7 to 8. I will cut a new release candidate for voting when issue will be fixed. - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For

Re: [VOTE] Release Qpid Broker-J 9.1.0

auses of failures. It > could be just test failures. The most worrying test failures are > SimpleConversionTest covering the functionality to convert messages > between different protocols. > > Kind Regards, > Alex > > On Mon, 14 Aug 2023 at 11:04, Tomas Vavricka wrote: > > &

Re: [VOTE] Release Qpid Broker-J 9.1.0

Tomas Vavricka wrote: > Hi all, > > I built release artifacts for Qpid Broker-J version 9.1.0 RC1. > Please, give them a test out and vote accordingly. > > The source and binary archives can be found at: > https://dist.apache.org/repos/dist/dev/qpid/broker-j/9.1.0-rc1/ >

[VOTE] Release Qpid Broker-J 9.1.0

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

[CANCELLED][VOTE] Release Qpid Broker-J 9.0.1

The vote is cancelled due to the issues with logging and licensing. I will cut a new release candidate for voting when issues will be fixed. - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands,

Re: [VOTE] Release Qpid Broker-J 9.0.1

/DEPENDENCIES_REFERENCE > [2] > https://github.com/apache/qpid-broker-j/blob/main/apache-qpid-broker-j/src/main/assembly/LICENSE > [3] > https://github.com/apache/qpid-broker-j/blob/f3703502e16e75c1df8c1f84e9de1afde6781e5f/apache-qpid-broker-j/src/main/assembly/dependenc

[VOTE] Release Qpid Broker-J 9.0.1

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

Re: [VOTE] Release Apache Qpid protonj2 1.0.0-M16

* Verified the signature and checksum files * Verified LICENCE and NOTICE files in archives * Verified source license headers by 'mvn apache-rat:check' * Built from source and ran tests (mvn clean install) on OpenJDK Java 11 (11.0.18) and OpenJDK Java 17 (17.0.6) on Ubuntu 22.04.2 Regards, Tomas

Re: [VOTE] Release Apache Qpid JMS 1.9.0

+1 * Verified the signature and checksum files * Verified LICENCE and NOTICE files in archives * Verified source license headers by 'mvn apache-rat:check' * Built from source and ran tests (mvn clean install) on OpenJDK Java 11 (11.0.18) and OpenJDK Java 17 (17.0.6) on Ubuntu 22.04.2 Regards,

Re: [VOTE] Release Apache Qpid JMS 2.3.0

+1 * Verified the signature and checksum files * Verified LICENCE and NOTICE files in archives * Verified source license headers by 'mvn apache-rat:check' * Built from source and ran tests (mvn clean install) on OpenJDK Java 11 (11.0.18) and OpenJDK Java 17 (17.0.6) on Ubuntu 22.04.2 Regards,

Re: [VOTE] Release Apache Qpid protonj2 1.0.0-M15

+1 * Verified the signature and checksum files * Verified LICENCE and NOTICE files in archives * Verified source license headers by 'mvn apache-rat:check' * Built from source and ran tests (mvn clean install) on OpenJDK Java 11 (11.0.18) and OpenJDK Java 17 (17.0.6) on Ubuntu 22.04.2 Regards,

Re: [VOTE] Release Apache Qpid ProtonJ2 1.0.0-M13 (RC1)

+1 * Verified the signature and checksum files * Verified LICENCE and NOTICE files in archives * Verified source license headers by 'mvn apache-rat:check' * Built from source and ran tests (mvn clean install) on Java 11 and Java 17 On 2023/03/27 19:03:53 Timothy Bish wrote: > Hi folks, > > I

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

+1 * Verified the signature and checksum files * Verified LICENCE and NOTICE files in archives * Verified source license headers by 'mvn apache-rat:check' * Built from source (mvn clean install) on Java 11 and Java 17 Tomas On 2023/03/02 18:00:04 Robbie Gemmell wrote: > Hi folks, > > I have

Re: [RESULT][VOTE] Release Qpid Broker-J 9.0.0 (RC2)

gt; https://dlcdn.apache.org/qpid/broker-j/) and maven central (see e.g > https://repo1.maven.org/maven2/org/apache/qpid/qpid-broker/) shortly, > at which point the website can be updated and the release announced > (and I'll then remove 8.0.6 from the dist release repo). > > On Tue, 22 Nov 2022

[ANNOUNCE] Apache Qpid Broker-J 9.0.0 released

The Apache Qpid (http://qpid.apache.org) community is pleased to announce the immediate availability of Apache Qpid Broker-J 9.0.0. This is the latest release of pure java implementation of messaging broker supporting the Advanced Message Queuing Protocol 1.0 (AMQP 1.0, ISO/IEC 19464,

[RESULT][VOTE] Release Qpid Broker-J 9.0.0 (RC2)

There were 3 binding +1 votes, 1 non-binding +1 vote, 1 indicative +1 vote and no other votes received. The vote has passed. I am not a PMC member, I would like to ask if a PMC member could publish the release? Voting thread: https://lists.apache.org/thread/sdn5mmf3glgjtdywbo9hlk7wo41o2pxy

Re: [VOTE] Release Qpid Broker-J 9.0.0 (RC2)

/... via REST API * sent and received messages using Qpid JMS Client Tomas On 2022/11/14 11:51:14 Tomas Vavricka wrote: > Hi all, > > I built release artefacts for Qpid Broker-J version 9.0.0 RC2. > Please, give them a test out and vote accordingly. > > The source and b

[VOTE] Release Qpid Broker-J 9.0.0 (RC2)

Hi all, I built release artefacts for Qpid Broker-J version 9.0.0 RC2. Please, give them a test out and vote accordingly. The source and binary archives can be found at: https://dist.apache.org/repos/dist/dev/qpid/broker-j/9.0.0-rc2/ The maven artifacts are also staged at:

Re: [VOTE] Release Qpid Broker-J 9.0.0

CI jobs is in > order, since the test issues should have been caught earlier. That in > addition to perhaps preparing for removal of the Travis based jobs > when Infra cease paying for Travis at the end of December. > > On Fri, 11 Nov 2022 at 15:54, Tomas Vavricka wrote:

Re: [VOTE] Release Qpid Broker-J 9.0.0

Hi Robbie, thank you very much for testing and comments. The points mentioned should be fixed in main branch. I will try to prepare RC2 next week (if no more issues). Regards, Tomas On 2022/11/11 13:25:27 Robbie Gemmell wrote: > One further issue noticed now the earlier test issue was

[CANCELLED][VOTE] Release Qpid Broker-J 9.0.0

The vote is cancelled due to the issues with truncating file paths in source bundle when extracted by 7-zip or Midnight Commander (tar -xvf works fine). I will cut a new release candidate for voting when issue will be fixed.

Re: [VOTE] Release Qpid Broker-J 8.0.0

+1 * built from source * executed system and integration tests * installed broker with BDB store * * added broker objects (queues/exchanges/ports/...) via REST API * * password and external authentication * * send and receive * * message recovery after broker restart * * ACL rights Tomas --

Re: [Qpid Broker-J] NullPointerException when using temporary queues

Hi Alex, I created JIRA QPID-8323 Regards, Tomas -- Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html - To unsubscribe, e-mail:

[Qpid Broker-J] NullPointerException when using temporary queues

Hi, during performance test there are created temporary exclusive autodelete queues, then messages are sent to created temporary queues and then temporary queues are deleted. All operation are done in parallel in multiple threads. Sometimes broker throws NullPointerException and then dies

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

Hi, thank you for quick replies. When I checked system tests I remembered there is property "Peers only" set to true in truststore in our broker setup. I set "Peers only" to false, restarted broker and I was able to connect with certificate signed by custom CA. Best Regards, Tomas -- Sent

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

Hi, I tried to authenticate via certificate which is signed by my own certificate authority and only certificate authority public key is present in broker. Steps I have done: * create certificate authority * add public CA key to broker truststore (certutil DB in C++ broker) * sign client

[Broker-J] Limit connections per user

Hi, is it possible to limit maximum number of AMQP connections per user basis? I can set maximum number of connections for AMQP port, but then one user can create maximum number of connections and this user will block other users connections. Best regards, Tomas -- Sent from:

Re: [Broker-J] Detect idle connections

JIRA created - https://issues.apache.org/jira/browse/QPID-8240 Tomas -- Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional

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

+1 * checkout tag 7.0.4 from git repository * build using mvn clean package (including tests) * started broker on Debian 9 * checked if only user which created temporary queue, can consume message when rule 'ACL ALLOW-LOG OWNER CONSUME QUEUE' is applied * created queue and exchange with name

Re: [Java Broker] Temporary queues ACLs for multiple users

Hi Keith, excellent idea, this will completely solve our use case. Regards, Tomas -- Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org

Re: [Java Broker] Temporary queues ACLs for multiple users

s only AMQP 0-x conventions you have to permission the default > exchange. > > ACL ALLOW-LOG foo PUBLISH EXCHANGE name="" routingKey="queueName" > > Hope this helps. > > Keith > > On 5 April 2018 at 14:46, Vavricka > vavricka.tomas@ > wrote: >&

[Java Broker] Temporary queues ACLs for multiple users

Hi, I am trying to get working temporary queues on Java Broker. Each user should have access only to queue which he created. ACL rights: ACL ALLOW-LOG user1 ACCESS VIRTUALHOST ACL ALLOW-LOG user1 CREATE QUEUE temporary="true" owner="user1" ACL ALLOW-LOG user1 CONSUME QUEUE temporary="true"

Re: [Java Broker] Select certificate from broker keystore

he bug >> as >> part of QPID-7567[1] last year, however I think that is only on master >> (and >> scheduled for 7.1) and hasn't been backported to 7.0.x. >> >> -- Rob >> >> [1] https://issues.apache.org/jira/browse/QPID-7567 >> >> O

[Java Broker] Select certificate from broker keystore

Hi, *I generate multiple self-signed certificates by:* keytool -genkeypair -alias pc18379_1 -dname CN=pc18379 -validity 1096 -keysize 2048 -keyalg RSA -sigalg SHA512withRSA -keypass '123456' -storepass 123456 -deststoretype PKCS12 -keystore pc18379_1.jks keytool -genkeypair -alias pc18379_2

Re: Java Broker performance

you would see greater performance. Let me ask a higher level > question - what messaging guarantee does this application require? > > [1] https://qpid.apache.org/releases/qpid-jms-0.27.0/docs/index.html > > On 10 November 2017 at 15:50, Rob Godfrey > rob.j.godfrey@

Re: Java Broker performance

Hi, hardware: * Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz * 16 GB RAM * HDD ST500DM002-1BD142 timings: Currently Java Broker 6.1.1 seems to behave as version 7.0.0 RC. 10 - 30 messages per second. Interesting is when I increase message size to 10kB. Messages per second are same but throughput is

Re: Java Broker performance

Yes, we running it on same hardware and versions. Couldn't be there issue with our configuration? Can you spot there some misconfiguration in config files below? Will be helpful if you send us your broker configuration? config.json { "id" : "cfa9a57a-6f98-4f17-b81d-22fb5a032473", "name" :

Re: Java Broker performance

C++ client code below #include #include #include #include #include #include #include #include #include #include #include class Broadcaster : public proton::messaging_handler { private: std::string _account; std::string _password; std::string _host;

Re: Java Broker performance

Hi, when consumer is not attached sending of messages is slow too. We were running performance tests for Java Broker 6.1.1 before 6 months and there were no issues (throughput for 1K messages was around 10MB/s). rgodfrey wrote > Hi Tomas, > > are you saying that there is a significant

Java Broker performance

Hi, we are testing release candidate of Java Broker 7.0.0. I checkout tag 7.0.0, build broker with tests without any problem. We have sender and receiver based on proton 0.18.1. Both sender and receiver are started at same time. Sender is sending 1000 persistent messages to exchange and

Re: [Java Broker] Usage of any certificate from keystore

rgodfrey wrote > On 27 October 2017 at 10:43, Vavricka > vavricka.tomas@ > wrote: > > In the period 28.10.2017 10:00 - 30.10.2017 10:00; both certificates are > valid... the broker can't really know which is "preferred" by the client, > I > would think tha

Re: [Java Broker] Usage of any certificate from keystore

I can imagine these situations where it can be helpful. 1. * There is active/passive cluster (provides a fully redundant instance of each node, which is only brought online when its associated primary node fails) environment where Java broker is running on node1 * Shared drive is used for

Re: [Qpid JMS client] Characters ',' and '=' in password

Yes type of authentication provider is SCRAM-SHA-256. And I can confirm that when PLAIN sasl mechanism is used, password with ',' and '=' characters can be used. Thanks for quick replies. Vavricka -- Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html

[Qpid JMS client] Characters ',' and '=' in password

(password, StandardCharsets.UTF_8.name()). Are these characters unsupported? Vavricka -- Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org

Re: [Qpid JMS Client] Password with '+' character

Hi, when I used URLEncoder.encode(pass, "UTF-8") as used in mentioned test, client successfully connected. Thanks for reply. Tomas -- Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html - To

[Qpid JMS Client] Password with '+' character

character in jms.password property? Vavricka -- Sent from: http://qpid.2158936.n2.nabble.com/Apache-Qpid-users-f2158936.html - To unsubscribe, e-mail: users-unsubscr...@qpid.apache.org For additional commands, e-mai

[Qpid JMS client] Asynchronous send JMS 2.0

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 - "amqp://host:20405?jms.username=admin=admin=true=true=true" When I use JMS 1.1 API, it works ok.

Re: [Java Broker] Invalid routing key

Hi, JIRA issue created https://issues.apache.org/jira/browse/QPID-7857 <https://issues.apache.org/jira/browse/QPID-7857> . Vavricka -- View this message in context: http://qpid.2158936.n2.nabble.com/Java-Broker-Invalid-routing-key-tp7664724p7664731.html Sent from the Apache Qpid

[Java Broker] Invalid routing key

was routing key specified as TradeReport. Vavricka -- View this message in context: http://qpid.2158936.n2.nabble.com/Java-Broker-Invalid-routing-key-tp7664724.html Sent from the Apache Qpid users mailing list archive at Nabble.com. ---

Re: [Qpid Java Broker] Get SessionPrincipal

Thanks, it works like a charm. Vavricka -- View this message in context: http://qpid.2158936.n2.nabble.com/Qpid-Java-Broker-Get-SessionPrincipal-tp7663741p7663794.html Sent from the Apache Qpid users mailing list archive at Nabble.com

[Qpid Java Broker] Get SessionPrincipal

().next(); AMQPSession session = sessionPrincipal.getSession(); Am I doing anything wrong? Vavricka -- View this message in context: http://qpid.2158936.n2.nabble.com/Qpid-Java-Broker-Get-SessionPrincipal-tp7663741.html Sent from the Apache Qpid users mailing list archive

Re: [Java Broker] Access control rights, routingKey and wildcard

uot; as wildcard is ok for me. I was just confused that ACL wildcard works differently from topic exchange. Vavricka -- View this message in context: http://qpid.2158936.n2.nabble.com/Java-Broker-Access-control-rights-routingKey-and-wildcard-tp7662212p7662213.html Sent from the Ap

[Java Broker] Access control rights, routingKey and wildcard

me when I set message routing key to "ABCD.*". Is there a way to restrict access by routing key with wildcard? Am I doing everything correctly? I used https://qpid.apache.org/releases/qpid-java-6.1.2/java-broker/book/Java-Broker-Security-ACLs.html as source of information. Vavr

Re: [Qpid Java Broker] Remove alternate exchange

It worked like a charm. Thanks. Vavricka -- View this message in context: http://qpid.2158936.n2.nabble.com/Qpid-Java-Broker-Remove-alternate-exchange-tp7660147p7660212.html Sent from the Apache Qpid users mailing list archive at Nabble.com

[Qpid Java Broker] Remove alternate exchange

passes, but no change is done, alternate exchange still persists. Is this the correct way how to remove exchange with alternate exchange? Vavricka -- View this message in context: http://qpid.2158936.n2.nabble.com/Qpid-Java-Broker-Remove-alternate-exchange-tp7660147.html Sent from th

[Java Broker] SASL connection to REST API

ature.universal("admin", "admin"); with no success (401 status). Am I doing something wrong? Vavricka -- View this message in context: http://qpid.2158936.n2.nabble.com/Java-Broker-SASL-connection-to-

Re: [Qpid Java Broker] Generate SHA-256 password

Many thanks. I successfully managed to generate SCRAM-SHA256 password by using code from AbstractScramAuthenticationManager.java. Vavricka -- View this message in context: http://qpid.2158936.n2.nabble.com/Qpid-Java-Broker-Generate-SHA-256-password-tp7658669p7658778.html Sent from the Apache

[Qpid Java Broker] Generate SHA-256 password

Hi, I would like to ask If there is possibility to generate SHA-256 hash for password by external program and then paste it to config.json file? Vavricka -- View this message in context: http://qpid.2158936.n2.nabble.com/Qpid-Java-Broker-Generate-SHA-256-password-tp7658669.html Sent from

Java Broker QMF2 Management

. at org.apache.qpid.server.model.ConfiguredObjectTypeRegistry.addStateTransitions(ConfiguredObjectTypeRegistry.java:982) ~[qpid-broker-core-6.0.2.jar:6.0.2] Is still possible to add QMF2 management plugin ? Vavricka -- View this message in context: http://qpid.2158936.n2.nabble.com/Java-Broker-QMF2-Management

Re: Java Broker exclusive binding

nothing like that > currently. I meant exactly that, sorry for mine vague explanation. Thanks a lot for clarifying. Vavricka -- View this message in context: http://qpid.2158936.n2.nabble.com/Java-Broker-exclusive-binding-tp7651458p7651464.html Sent from the Apache Qpid users mailing list archiv

Java Broker exclusive binding

. In REST API definitions I found attribute named 'type' which looks promising, but unfortunately I couldn't find any documentation about it. Vavricka -- View this message in context: http://qpid.2158936.n2.nabble.com/Java-Broker-exclusive-binding-tp7651458.html Sent from the Apache Qpid

Re: Filtering issues

QP style > naming of properties for AMQP 1.0. You can use the JMS names however. Is planned support for AMQP naming style properties for AMQP 1.0? Thanks a lot for your help. Regards, Vavricka -- View this message in context: http://qpid.2158936.n2.nabble.com/Filtering-issues-tp7642996p7643131.html

Re: Filtering issues

I am using Qpid Java Broker 6.0.2. -- View this message in context: http://qpid.2158936.n2.nabble.com/Filtering-issues-tp7642996p7642998.html Sent from the Apache Qpid users mailing list archive at Nabble.com. - To

Filtering issues

ot; + yesterday.getTime());'. Message was created with today's timestamp so message should be received, but no message was received, when selector is specified. Is this known issues? Am I doing everything right? Best regards, Vavricka -- View

Re: ACL Java Broker 6.0.2 AMQP 1.0

Hi, thanks for quick reply. Including this in version 6.1 is OK for me. Best Regards, Vavricka -- View this message in context: http://qpid.2158936.n2.nabble.com/ACL-Java-Broker-6-0-2-AMQP-1-0-tp7642793p7642947.html Sent from the Apache Qpid users mailing list archive at Nabble.com

Re: ACL Java Broker 6.0.2 AMQP 1.0

If there any problems viewing ACL rule or log,it maybe connected to nabble formatting. You can view original message at http://qpid.2158936.n2.nabble.com/ACL-Java-Broker-6-0-2-AMQP-1-0-td7642793.html -- View this message in context:

ACL Java Broker 6.0.2 AMQP 1.0

special configuration for AMQP 1.0 to get ACL working as in AMQP 0-10? Vavricka -- View this message in context: http://qpid.2158936.n2.nabble.com/ACL-Java-Broker-6-0-2-AMQP-1-0-tp7642793.html Sent from the Apache Qpid users mailing list archive at Nabble.com