Re: Virtualhost Initial Configuration

In order to help, you'll need to be a bit more explicit in terms of what you are trying to achieve in the virtual host configuration and exactly in what way it is "not working", -- Rob On Wed, 27 Mar 2024 at 17:36, Faisal Shaukat wrote: > Dear Sir/Madam, > > I am trying to use Apache Qpid in

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

+1 built and ran on my (Intel) Mac using JDK 11 ran mms and bdb system tests verified signatures and checksum files used console to perform a few basic operations -- Rob On Tue, 15 Nov 2022 at 08:19, Tomas Vavricka wrote: > +1 > > * verified signatures and checksum files > * extracted source

Re: QPID Broker-J Java 11

To be clear, are we talking about changing the required minimum version of Java required to run Qpid Broker-J? I think it's probably about time, but that would probably deserve updating the major version number (I think we've done that every time we've upped the required Java version previously).

Re: Broker-J: several authentication providers on one port

Rather than changing the model with all the extra work required to perform upgrades, etc... Would it make sense/be possible to simply define a new "composite authentication provider" which just contained an ordered list of other authentication providers which it would delegate to? This would seem

Re: Does Qpid Java broker close connection upon channel exception as well as closing the channel?

So, according to the 0-9-1 definition ( https://www.amqp.org/specification/0-9-1/amqp-org-download), 404 is supposed to be a channel error - so RabbitMQ is likely more correct than the Java Broker. IIRC there were a whole boatload of issues with clients (particularly the old JMS client) trying to

Re: Outreachy Intern

On Wed, 26 May 2021 at 11:29, Robbie Gemmell wrote: > Welcome, Rakhi! > > +1 - Welcome Rakhi! Great to have you onboard. -- Rob > On Tue, 25 May 2021 at 18:28, Rakhi Kumari wrote: > > > > Hi everyone! > > > > I am Rakhi Kumari from India. I’ll be contributing to Apache Qpid Proton > as > >

Re: Message Persistence in Qpid Broker C++ (1.39)

On Wed, 19 May 2021 at 17:04, Gordon Sim wrote: > On Wed, May 19, 2021 at 3:34 PM Namitha, Nancy wrote: > > Is Broker - J optimized for the below mentioned scenario. > > I believe the java broker will indeed perform better for synchronous > publish. Best thing is to run a quick test though. >

Re: [RABBITMQ/QPID-JMS/VHOST] failed to connect to a virtual host

MQP 0-9-1 ? Or do I need to > downgrade QPID's version ? > > (By the way, your help is much appreciated ;-) ) > -----Message d'origine- > De : Rob Godfrey > Envoyé : vendredi 12 février 2021 15:29 > À : users@qpid.apache.org > Cc : VARSHNEY Prerna > Objet : Re: [RABBITMQ/QPID-JM

Re: [RABBITMQ/QPID-JMS/VHOST] failed to connect to a virtual host

ts > Listing vhosts ... > name > /test > / > > herbert@centos-001$ sudo rabbitmqctl list_queues -p /test > Timeout: 60.0 seconds ... > Listing queues for vhost /test ... > namemessages > vval0 > conf.r 0 > conf.q 0 > > -Message d'o

Re: [RABBITMQ/QPID-JMS/VHOST] failed to connect to a virtual host

> I had the feeling that this would pair up nicely. When I connect my > program to the default virtual host (/), all running fine. > > > -Message d'origine- > De : Rob Godfrey > Envoyé : jeudi 11 février 2021 13:14 > À : users@qpid.apache.org > Cc : VARSHNEY Prerna

Re: broker j REST API getMessageContent help

Did you see any sort of Java stack trace in the logs corresponding to this issue? If so, can you paste the stack trace here? Thanks, Rob On Wed, 10 Feb 2021 at 09:45, bltw15 wrote: > I'm trying to retrieve message content from the queue, but can't seem to > get > it right. What is an example

Re: [RABBITMQ/QPID-JMS/VHOST] failed to connect to a virtual host

Are you enabling AMQP 1.0 support on RabbitMQ via their plugin (RabbitMQ does not support AMQP 1.0 by default - see https://www.rabbitmq.com/protocols.html). The Qpid JMS client uses AMQP 1.0 only. -- Rob On Thu, 11 Feb 2021 at 13:06, KOELMAN Herbert < herbert.koel...@soprasteria.com> wrote: >

Re: [VOTE] Release Qpid Broker-J 7.1.9

+1 - built from source and ran tests - kicked the tyres through the management console On Thu, 17 Sep 2020 at 12:11, Gordon Sim wrote: > > On 15/09/2020 12:55 am, Oleksandr Rudyy wrote: > > Hi folks, > > > > I built release artefacts for Qpid Broker-J version 7.1.9 RC1. > > Please, give them a

Re: [VOTE] Release Qpid Broker-J 8.0.1

+1 - built from source and ran tests - kicked the tyres through the management console On Thu, 17 Sep 2020 at 11:45, Gordon Sim wrote: > > On 15/09/2020 1:37 am, Oleksandr Rudyy wrote: > > Hi guys, > > > > I built release artefacts for Qpid Broker-J version 8.0.1 RC1. > > Please, give them a

Re: qpid-jms-client

On Tue, 11 Aug 2020 at 13:13, AnujaAlli wrote: > > Hi Team, > > Currently we are using *qpid-amqp-1-0-client-jms(0.27) * version, we want to > upgrade that to newer version. > We found that there is no new version introduced after 0.32 which contains > deadlock issue

Re: Broker-J: Message larger than 2GB

I think it's quite likely that there is a limitation somewhere where int is used (or possibly just an array created) which means that 2Gb is the effective message size limit. Do you actually have a requirement for such an enormously sized message - or are you just testing? -- Rob On Thu, 9 Jul

Re: [VOTE] Release Apache Qpid JMS 0.50.0

+1 Built from source and ran tests Ran Qpid Broker-J systests using built JMS client -- Rob On Wed, 11 Mar 2020 at 19:22, Timothy Bish wrote: > On 3/11/20 12:35 PM, Robbie Gemmell wrote: > > Hi folks, > > > > I have put together a spin for a 0.50.0 Qpid JMS client release, > > please give

Re: [Broker-J] Claim-check pattern and MessageDeleteListener

is left in the table. -- Rob On Wed, 11 Mar 2020 at 10:33, VERMEULEN Olivier wrote: > from many queues on the same broker > ____________ > From: Rob Godfrey > Sent: Wednesday, March 11, 2020 10:01:43 AM > To: users@qpid.apache.org > Subje

Re: [VOTE] Release Qpid Broker-J 8.0.0

On Tue, 10 Mar 2020 at 18:09, Gordon Sim wrote: > On 10/03/2020 4:45 pm, Gordon Sim wrote: > > On 04/03/2020 11:44 am, Alex Rudyy wrote: > >> Hi all, > >> > >> I built release artefacts for Qpid Broker-J version 8.0.0 RC1. > >> Please, give them a test out and vote accordingly. > >> > >> The

Re: [Broker-J] Claim-check pattern and MessageDeleteListener

ssage is or will be deleted from the store (this includes the recovery > process). > After that whether the hook is at the queue or virtual host level doesn't > really matter... > > Olivier > > From: Rob Godfrey mailto:rob.j.godf...@gmail

Re: [Broker-J] Claim-check pattern and MessageDeleteListener

ructure > for 1.0 messages). > > > > Did I miss something? > > > > No - I think to do this safely we'd have to expose some new API here. > > -- Rob > > > > > > Thanks, > > Olivier > > > > -Original Message- > >

Re: [Broker-J] Claim-check pattern and MessageDeleteListener

ink to do this safely we'd have to expose some new API here. -- Rob > > Thanks, > Olivier > > -Original Message- > From: Rob Godfrey > Sent: vendredi 6 mars 2020 17:54 > To: users@qpid.apache.org > Subject: Re: [Broker-J] Claim-check pattern and MessageDeleteListene

Re: C++ Broker

On Sat, 7 Mar 2020 at 04:16, Virgilio Fornazin wrote: > RHEL is pushing Dispatcher + Broker-J (Artemis based) as the new A-MQ > solution. > Just to be clear Artemis is part of the ActiveMQ project and not related to Qpid Broker-J -- Rob > With container and another new things happening,

Re: [Broker-J] Claim-check pattern and MessageDeleteListener

Hi Olivier I'm not entirely sure what your exact idea here is - are you looking to have Broker-J trigger the deletion on the blob at the point at which it believes it no longer needs the message? Or maybe to update the blob store to make clear that the broker no longer needs to retain a copy of

Re: [VOTE] Release Qpid Broker-J 7.1.8

+1 built from source ran 0-9-1 and 1.0 tests started the broker and kicked the tyres of the management console -- Rob On Mon, 10 Feb 2020 at 12:12, Oleksandr Rudyy wrote: > +1 > > My tests included the following: > * verified signatures and checksums > * built broker from source bundle and

Re: An imperative AMQP client API

eue, or a new message you created in order to > send it. So acknowledge is a method on a Delivery, not a Message. Same for > trackers - they don't even exist until a message is sent, and they expire > when the message is acknowledged, data in the message can exist (or be > destroyed) ind

Re: [Broker-J] Add support for SQL Server to JDBC store

Hi Olivier, as long as there are no requirements for code with incompatible licenses to be distributed by the Broker (which there shouldn't be) I don't see any issues at all (basically this is the same as supporting one of the other proprietary database vendors). Given their common roots, I

Re: Certificate validation behavior changed in QPID Broker-J 7.1.5?

I've created QPID-8404 for this and attached a very simple patch which I hope should solve your issue -- Rob On Fri, 24 Jan 2020 at 10:43, Rob Godfrey wrote: > It looks like this might be related to changes made in the underlying > Jetty library - https://github.com/eclipse/jetty.p

Re: Certificate validation behavior changed in QPID Broker-J 7.1.5?

It looks like this might be related to changes made in the underlying Jetty library - https://github.com/eclipse/jetty.project/issues/3554 It seems like a change needs to be made to Qpid Broker-J to explicitly disable this breaking change that Jetty introduced :-( -- Rob On Thu, 23 Jan 2020 at

Re: An imperative AMQP client API

On Tue, 21 Jan 2020 at 18:31, Robbie Gemmell wrote: > On Tue, 21 Jan 2020 at 17:06, Rob Godfrey wrote: > > > > On Tue, 21 Jan 2020 at 16:38, Robbie Gemmell > > wrote: > > > > > On Tue, 21 Jan 2020 at 14:28, Rob Godfrey > wrote: > > > > &

Re: An imperative AMQP client API

On Tue, 21 Jan 2020 at 16:38, Robbie Gemmell wrote: > On Tue, 21 Jan 2020 at 14:28, Rob Godfrey wrote: > > > > On Tue, 21 Jan 2020 at 14:24, Robbie Gemmell > > wrote: > > > > > On Tue, 21 Jan 2020 at 11:21, Rob Godfrey > wrote: > > > > >

Re: An imperative AMQP client API

On Tue, 21 Jan 2020 at 14:24, Robbie Gemmell wrote: > On Tue, 21 Jan 2020 at 11:21, Rob Godfrey wrote: > > > > So... a few initial thoughts / queries from a brief look through. I'll > try > > to do a more detailed review later > > > > 1. I don't se

Re: An imperative AMQP client API

So... a few initial thoughts / queries from a brief look through. I'll try to do a more detailed review later 1. I don't see any mechanism for connection retry / alternate hosts in the connect operation / connection-options parameter ; further I presume there is no mechanism for attempted

Re: [VOTE] Release Qpid Broker-J 7.1.7

+1 Built from source and ran 0-9-1 and 1-0 tests started up the broker and kicked the tyres of the web ui -- Rob On Sun, 12 Jan 2020 at 23:14, Keith W wrote: > +1. > > My testing was: > > 1) Verified the sha512 checksums on all distribution artefacts > 2) Verified signatures on all the

Re: [Qpid-Jms-Client] How does the broker get to know whether durable-shared-subscription should be associated with the containerId or not?

I think all the details are in this JIRA: https://issues.apache.org/jira/browse/QPIDJMS-220 -- Rob On Thu, 9 Jan 2020 at 23:57, Neeraj Makam wrote: > Hi > > Based on the spec of JMS 2.0, the clientId (which is set on the > connection) is optional for shared durable subscription. And this was

Re: Persistent messages in Durable Q not available after restart

Hi Kristofor, As Alex says, to me this looks like a problem with your environment configuration / test set up - I cannot reproduce the issue you are seeing. I downloaded Qpid 6.1.4, set up a virtual host as you described (JSON node, BDB host) and a durable LVQ, with persist ALWAYS. I sent a

Re: [VOTE] Release Qpid Broker-J 7.1.6

+1 built from source, ran 0-9-1 and 1-0 tests, started up the broker and kicked the tires. Tested the new REST API parts on various JVMs (8, 11 ; hotspot, J9) on my OS X machine. -- Rob On Mon, 2 Dec 2019 at 11:28, Alex Rudyy wrote: > Hi all, > > I built release artefacts for Qpid Broker-J

Re: Message timeouts before sending ack

Hi Martin, I'm pretty sure this is an Azure Service Bus "feature" rather than anything on the client side. I'm no expert on Service Bus, but I believe it grants a "lock" on the message for the consumer to process it, and then revokes the lock if processing has not completed within a timeout

Re: Migrate 0.20 XML configs to 6.1.4 JSON configs

On Thu, 21 Nov 2019 at 19:03, Kristofor Horst wrote: > Hello, > > Is there a generally accepted best practice/tool that can easily migrate an > xml configuration compatible with qpid 0.20 to the json format required of > 6.1.4? > Wow - that's an old version :) - looking back 0.20 was released

Re: [Broker-J] REST-API: how to determine consumer for acquired messages

So I've pushed a change that will return the consumerId of the acquiring consumer - so for an acquired message you'd additionally something like: "deliveredToConsumerId" : "406c1d71-1189-41bf-a945-6d21f5fd0753" Does that meet your requirements? Thanks, Rob On Wed, 6 Nov 2019 at 01:54, Timo

Re: [Broker-J] REST-API: getMessageInfo does not list message groupIds

Committed as QPID-8380 <https://issues.apache.org/jira/browse/QPID-8380>. Alex - another candidate for the next 7.1.x release I think -- Rob On Tue, 19 Nov 2019 at 10:11, Rob Godfrey wrote: > Hi > > On Tue, 19 Nov 2019 at 00:27, Timo Naroska > wrote: > >> Hi, >&

Re: [Broker-J] REST-API: getMessageInfo does not list message groupIds

Hi On Tue, 19 Nov 2019 at 00:27, Timo Naroska wrote: > Hi, > > we’re using Qpid’s message grouping feature and are sending messages > through Qpid java client with the JMSXGroupID property. This is working > great. > > Good to hear! > We noticed that when using the getMessageInfo REST API

Re: Qpid as a RabbitMQ broker for Java app integration tests - exchange declare arguments

On Mon, 18 Nov 2019 at 13:42, Lukasz Guzik wrote: > Hi Rob, > > Yes, this is a perfect solution for me, thank you! :) > Could you please let me know when it will be released? > > Alex - do we have a plan for the next release yet? -- Rob > niedz., 17 lis 2019 o 23:30 R

Re: Qpid as a RabbitMQ broker for Java app integration tests - exchange declare arguments

Hi Łukasz, I have made an enhancement to the Broker as QPID-8377 <https://issues.apache.org/jira/browse/QPID-8377> along the lines I suggested in my previous mail. I hope this will meet your requirements. Thanks, Rob On Mon, 11 Nov 2019 at 09:33, Rob Godfrey wrote: > Hi Łukasz, &g

Re: Broker-J statistics and CPU consumption

ic, as it's likely that the Dispatch developers will skip this thread due to its title :-) -- Rob > > Olivier > > -Original Message- > From: Rob Godfrey > Sent: dimanche 17 novembre 2019 13:36 > To: users@qpid.apache.org > Subject: Re: Broker-J statistics and CPU consu

Re: Broker-J statistics and CPU consumption

ecimal places) which will be retrieved if the underlying Java platform supports them. Hope this helps, Rob On Fri, 15 Nov 2019 at 23:05, Rob Godfrey wrote: > > > On Fri, 15 Nov 2019 at 21:21, Oleksandr Rudyy wrote: > >> Hi Olivier, >> >> CPU consumption statistic i

Re: Broker-J statistics and CPU consumption

On Fri, 15 Nov 2019 at 21:21, Oleksandr Rudyy wrote: > Hi Olivier, > > CPU consumption statistic is not available. > Potentially, cpu average load from > java.lang.management.OperatingSystemMXBean#getSystemLoadAverage can be > returned as part of broker statistics. > If you need

Re: Broker-J statistics and CPU consumption

Hi Olivier, no - there is nothing on CPU consumption. I don't believe there is any standard way to get the CPU consumption from a Java process. The closest I can find is that if the platform implementation of OperatingSystemMXBean implements com.sun.management.OperatingSystemMXBean then it will

Re: Qpid as a RabbitMQ broker for Java app integration tests - exchange declare arguments

Hi Łukasz, firstly let me apologise for not getting back to you sooner. Secondly, unfortunately I agree that there is no current way to explicitly tell the broker to ignore unknown exchange declare arguments, and that adding this ability is a good idea. The simplest approach is probably to add

Re: Are generated Ids secure + permanent?

Hi Kristofor, On Thu, 10 Oct 2019 at 20:17, Kristofor Horst wrote: > Hello, > > When a queue is generated via the UI/web API and written to the config.json > file, is the ID created for it securely generated and permanent? > > The IDs are generated from java.util.UUID.randomUUID() -

Re: [Broker-J] Question about SUB-1003: Suspended for 10,001 ms

On Fri, 11 Oct 2019 at 23:20, Tom Jordahl wrote: > Hello, > > I am hoping someone can give me a little more background on why I am > receiving the following messages in my broker logs: > 2019-10-11 10:32:10,278 INFO [IO-/10.110.54.132:41086] (q.m.s.state) - > [IO Pool]

Re: [VOTE] Release Qpid Broker-J 7.1.5

+1 Built from source Tested using AMQP 1.0 and 0-9-1 protocols, Memory and BDB stores. Manually tested the web console Simple send / receive tests -- Rob On Sun, 6 Oct 2019 at 12:59, Oleksandr Rudyy wrote: > +1 > > My tests are listed below > * verified signatures and checksums > *

Re: [Qpid Broker-J] Reload FileKeyStore

host name rather than just one default alias. > > I am speculating, as I am not sure what are the real use cases here. > > > > Kind Regards, > > Alex > > > > > > On Wed, 31 Jul 2019 at 17:36, Rob Godfrey > wrote: > > > > > On Wed, 3

Re: [Qpid Broker-J] Reload FileKeyStore

On Wed, 31 Jul 2019 at 17:37, Oleksandr Rudyy wrote: > Tomas, > Thanks for clarification. > > I am actually curious about your keystore setup. Why do you need multiple > valid certificates with matching SNI host name? Perhaps, I missing some > useful use cases. In that case, I can update

Re: [QPID Broker-J] Flow control does not stall the client

Hi Martin, On Thu, 18 Jul 2019 at 15:55, Martin Krása wrote: > Hello, > > I have installed Java broker version 7.1.5-SNAPSHOT (last commit > 4dd26ddd0263fac22d91a0a16c48789592a9ccb2). Using QPID JMS Client > 0.40.0 producer I sent valid messages to the exchange. All messages > end up in the

Re: [VOTE] Release Qpid Broker-J 7.0.8

On Fri, 5 Jul 2019 at 12:30, Robbie Gemmell wrote: > FWIW the test is passing for me on two different Fedora systems with > OpenJDK 1.8.0_212 and Oracle JDK 1.8.0_181, but the log does suggest > an issue which could very well be the one you point to. Especially > since the JIRA is marked fixed

Re: [VOTE] Release Qpid Broker-J 7.0.8

ure" is simply down to how long (failed) dns resolution takes on the machine running the test. -- Rob > Kind Regards, > Alex > > On Fri, 5 Jul 2019 at 11:16, Rob Godfrey wrote: > > > Hi Alex, > > > > thanks for finding that JIRA for me - I knew that I'd f

Re: [VOTE] Release Qpid Broker-J 7.0.8

Hi Alex, thanks for finding that JIRA for me - I knew that I'd fixed this at some point in the past. Just to confirm that that fixes the test for me. So I'm +1 on the release (perhaps we should apply that fix to the 7.0.x branch in case we do any more releases from there) Build from src, ran

Re: [VOTE] Release Qpid Broker-J 7.0.8

On Fri, 5 Jul 2019 at 10:54, Gordon Sim wrote: > On 05/07/2019 9:26 am, Oleksandr Rudyy wrote: > > Hi Gordon, > > > > Thanks for testing the release and reporting a test failure. > > > > The failed test sends open performative against non existing virtual host > > and expects to receive an

Re: [VOTE] Release Qpid Broker-J 7.1.4

On Wed, 3 Jul 2019 at 14:53, Alex Rudyy wrote: > Hi folks, > > I built release artefacts for Qpid Broker-J version 7.1.4 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/7.1.4-rc1/

Re: Negative Bytes Credit

Alex, looks like a broker defect to me. If the bytes (or message) credit is set to "infinite credit", then the useCreditForMessage method won't update the used bytes (or message) credit. However the restoreCredit method always tries to deduct from the bytes (or message) used value, which will

Re: Microservices Exchange Queue Strategy

Hi, On Wed, 12 Jun 2019 at 09:55, fea17e86 wrote: > Hi > > I want to use Qpid Broker-J and AMQP 1.0 to achieve and event and message > based communication between my microservices. I would like to hear your > thoughts on the following scenario: > > There are one or more microservices

Re: Broker-J topic example with rhea.js

On Fri, 7 Jun 2019 at 16:24, fea17e86 wrote: > Hi, > > I'm trying to get a publish subscribe example with Broker-J and rhea.js > to work. > > First I created a few queues bound to the default exchange "amq.topic": > >

Re: Qpid Broker-J - Add a certificate without recreating an SSL port

I believe you can use the ManagedPeerCertificateTrustStore if you want to dynamically add and remove certificates in this way. Having the broker reload a JKS store would require a change. -- Rob On Mon, 8 Apr 2019 at 13:26, Tomas Soltys wrote: > Hi, > > After I add a user certificate to a

Re: [VOTE] Release Qpid Broker-J 7.1.2

+1 built and ran tests (0-9-1 and 1.0) ad-hoc testing via the web console On Wed, 3 Apr 2019 at 16:15, Robbie Gemmell wrote: > On Sun, 31 Mar 2019 at 14:36, Oleksandr Rudyy wrote: > > > > Hi, > > > > I built release artefacts for Qpid Broker-J version 7.1.2 RC1. > > Please, give them a test

Re: [VOTE] Release Qpid Broker-J 7.1.1

+1 - built from source, ran tests (0-9-1, 0-10 mms; 1-0 bdb) verified signatures/checksums ad hoc testing On Tue, 26 Feb 2019 at 14:24, Gordon Sim wrote: > On 26/02/2019 12:40 pm, Oleksandr Rudyy wrote: > > I expect that building and running tests for earlier versions of broker-j > > bundle

Re: [VOTE] Release Qpid Broker-J 7.0.7

+1 - built from source, ran tests (0-9-1, 0-10 mms; 1-0 bdb) verified signatures/checksums ad hoc testing On Tue, 26 Feb 2019 at 14:14, Gordon Sim wrote: > On 25/02/2019 3:31 pm, Alex Rudyy wrote: > > Hi, > > > > I built release artefacts for Qpid Broker-J version 7.0.7 RC1. > > Please, give

Re: [VOTE] Release Qpid Broker-J 7.1.1

ct that building and running tests for earlier versions of broker-j > bundle would fail with the same error when OpenJDK 8u201 is used. > > I will look into fixing this issue tonight. > > Kind Regards, > Alex > > > On Tue, 26 Feb 2019 at 11:16, Rob Godfrey wrote: > > > S

Re: [VOTE] Release Qpid Broker-J 7.1.1

So, I think this is an OpenJDK vs. Oracle JDK problem. Running install 7.1.0 on OpenJDK (8u201) also fails on my Fedora machine. Switching to the Oracle JDK and it installs fine. -- Rob On Tue, 26 Feb 2019 at 11:46, Rob Godfrey wrote: > > > On Tue, 26 Feb 2019 at 11:04, Gordon S

Re: [VOTE] Release Qpid Broker-J 7.1.1

On Tue, 26 Feb 2019 at 11:04, Gordon Sim wrote: > On 25/02/2019 1:22 pm, Oleksandr Rudyy wrote: > > Hi folks, > > > > I built release artefacts for Qpid Broker-J version 7.1.1 RC1. > > Please, give them a test out and vote accordingly. > > > > The source and binary archives can be grabbed from:

Re: Rollback Failure

On Thu, 31 Jan 2019 at 19:02, sidarthsc wrote: > Thanks Rob! That makes sense. Similarly, we're seeing a lot of exceptions > of > the form "Session sync was interrupted by failover. [error code 541: > internal error]." Unfortunately, I'm not seeing in anything in the broker > logs and we're

Re: QPID feature to synchronize messages

you would need to add leading zeros to pad the String so it sorts the way you want). -- Rob On Wed, 30 Jan 2019 at 18:04, Bee k wrote: > Thank you. I will look into that. > > > > On Jan 30, 2019, at 4:20 AM, Rob Godfrey > wrote: > > > >> On Wed, 30 Jan 2019, 1

Re: QPID feature to synchronize messages

Actually Qpid Broker-J does support both holding messages for a given time before delivery, and sorted queues (i.e. ordering the delivery of messages from a particular queue based on a header value). -- Rob On Wed, 30 Jan 2019 at 10:20, Gordon Sim wrote: > On 29/01/19 16:46, Bee k wrote: > >

Re: Rollback Failure

On Fri, 18 Jan 2019 at 00:38, sidarthsc wrote: > Our server is running broker-j 7.0.6 and our sessions are transacted. We're > seeing a lot of exceptions of the form "Failed to rollback: > org.apache.qpid.AMQException: timed out waiting for sync: complete = 18, > point = 19 [error code 541:

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

Hi Brian, On Wed, 19 Dec 2018 at 23:18, Brian O'Shea wrote: > Looking at jconsole (connected to the running Qpid broker), it appears that > it exposes a Map under java.lang -> Runtime -> Attributes > -> > SystemProperties. Is this something that I can depend on always being > available? This

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

On Wed, 12 Dec 2018 at 16:13, Vavricka wrote: > 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

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

On Mon, 10 Dec 2018 at 17:10, Robbie Gemmell wrote: > Hi Folks, > > Per the below mail sent by the ASF Infrastructure team (to dev@), our Git > repositories will be migrated from the original/old git-wip-us service on > to > the newer gitbox.apache.org service by February 7th. > > This is

Re: Welcome Roddie Kieley as an Apache Qpid committer

Welcome Roddie - good to have you here! -- Rob On Tue, 27 Nov 2018 at 17:18, Oleksandr Rudyy wrote: > 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

Re: [Broker-J] JDBC config store

Actually, ignore that too... Been too long since I looked at this code. There doesn't actually seem to be any way to set an arbitrary property in the system config. :-( This seems like something we should raise an enhancement for Apologies, Rob On Mon, 26 Nov 2018 at 18:02, Rob Godfrey wrote

Re: [Broker-J] JDBC config store

> Sent: vendredi 23 novembre 2018 12:44 > To: users@qpid.apache.org > Subject: 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

Re: Changing system time causes J-Broker to drop connections

The connection timeouts are defined by the AMQP protocol and, since in general the two ends of the connection would be on different machines, implicitly refer to externally observable time (to the extent that such a concept is meaningful). You are changing the literal system time in your system,

Re: [Broker-J] JDBC config store

quot;type\":\"Noop\", \"attributes\":{}}" would work... Obviously the initial config will only be picked up if you are running the broker for the first time pointing at that database instance. -- Rob > > Olivier > > -Original Message- > From: Rob God

Re: [Broker-J] JDBC config store

On Thu, 22 Nov 2018 at 15:11, VERMEULEN Olivier wrote: > Hello, > > I'm using version 7.0.3 of the Broker-J. > I tried to configure it to use a JDBC (here Sybase) config store. > > qpid-server.bat -st JDBC -prop > "systemConfig.connectionUrl=jdbc:sybase:Tds:dell719srv:4100/DB" -prop >

Re: Changing system time causes J-Broker to drop connections

The Qpid Broker-J uses offsets from System.currentTimeMillis (defined by Java as "the difference, measured in milliseconds, between the current time and midnight, January 1, 1970 UTC") and so should not be affected by changed to DST or whatever. Suspending/resuming inside a VM would be a

Re: [Broker-J] JDBC message store performance

Rob, > > I modified your patch to set a minimum batch size of 10 but didn't see any > improvement in the overall throughput... > > Olivier > > -Original Message- > From: Rob Godfrey > Sent: mardi 2 octobre 2018 18:08 > To: users@qpid.apache.org > Subjec

Re: [Broker-J] Limit connections per user

Hi Tomas, On Mon, 15 Oct 2018 at 09:59, Vavricka wrote: > 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

Re: [Broker-J] JDBC message store performance

mum batch size of 10 or whatever and see if you get a further speedup. -- Rob > Olivier > > -Original Message- > From: Rob Godfrey > Sent: mardi 25 septembre 2018 13:20 > To: users@qpid.apache.org > Subject: Re: [Broker-J] JDBC message store performance > >

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

Then it looks like the issue you are seeing is that that Alex identified (i.e. it is a BDB issue and thus outside of our control in Qpid), obviously if you are not using the BDB store then you can simply exclude it from your build / dependencies. -- Rob On Tue, 25 Sep 2018 at 20:26, Brian O'Shea

Re: [Broker-J] JDBC message store performance

And now with a fix to allow the system tests to pass consistently https://issues.apache.org/jira/secure/attachment/12941197/QPID-8242.patch -- Rob On Tue, 25 Sep 2018 at 12:24, Rob Godfrey wrote: > D'oh - no idea what happened there. > > Re-attached with an actual diff this tim

Re: [Broker-J] JDBC message store performance

D'oh - no idea what happened there. Re-attached with an actual diff this time (I hope :) ) https://issues.apache.org/jira/secure/attachment/12941192/QPID-8242.patch -- Rob On Wed, 19 Sep 2018 at 01:23, Rob Godfrey wrote: > As an alternative approach, how about the (totally untested) pa

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

On Tue, 25 Sep 2018 at 01:23, Brian O'Shea wrote: > Hello Qpid developers, > > I am trying to build the Qpid broker version 7.0.6 Java version, and it is > failing the BDB Link Store Plug-in tests. I am building on an Intel 64-bit > system running Ubuntu Linux 16.04 with OpenJDK 1.8.0_162_x64.

Re: [Broker-J] JDBC message store performance

I'm on vacation at the moment, but if I get a chance I'll at least try to test with Derby. -- Rob On Wed, 19 Sep 2018 at 09:14, VERMEULEN Olivier wrote: > Thanks a lot Rob, I'll try to test that next week. > > Olivier > > -Original Message----- > From: Rob Godfrey &

Re: [Broker-J] JDBC message store performance

/QPID-8242.patch On Mon, 17 Sep 2018 at 15:22, Rob Godfrey wrote: > The reference counting is done in AbstractServerMessageImpl.java. In > general instances of ServerMessage should not be passed around, rather a > MessageReference (obtained by calling newReference(..) on the message

Re: [Broker-J] JDBC message store performance

ese 2 commits. > > But before going any further I'd like your input on the below, to see > > if what I'm trying to do could work or if I'm missing something (which > > I'm surely are) > > > > https://github.com/apache/qpid-broker-j/compare/master...overmeulen:fe > >

Re: [Broker-J] JDBC message store performance

commits > > Regards, > Olivier > > -Original Message- > From: Rob Godfrey > Sent: vendredi 14 septembre 2018 16:06 > To: users@qpid.apache.org > Cc: AYOUBI Ali > Subject: Re: [Broker-J] JDBC message store performance > > On Fri, 14 Sep 2018 at 15:30, VERME

Re: [Broker-J] JDBC message store performance

On Fri, 14 Sep 2018 at 15:30, VERMEULEN Olivier wrote: > Hello, > > We ran a performance test with a bunch of brokers and an Oracle database > to store the messages. > We noticed that the database was a bit overloaded with commits. > Looking at the logs we saw that sending a message was

Re: [Broker-J] Detect idle connections

Hi Tomas, I don't believe there is a way to do that currently, but it seems like a useful feature - please raise a JIRA and we can see about adding that -- Rob On Fri, 14 Sep 2018 at 09:20, Vavricka wrote: > Hi, > > we would like to detect idle connections in Java Broker. I found out there >

Re: [VOTE] Release Qpid for Java 6.1.7

+1 Compiled from source Ran bdb and mms 0-9-1 and 0-10 test profiles Started up the broker and poked around the management console a bit -- Rob On Thu, 30 Aug 2018 at 09:57, Keith W wrote: > On Tue, 28 Aug 2018 at 13:27, Oleksandr Rudyy wrote: > > > > Hi all, > > > > I built a release

Re: [Broker-J] HTTP management

On Wed, 29 Aug 2018 at 17:21, VERMEULEN Olivier wrote: > Hello, > > While working with the Broker-J HTTP management I found some strange > behaviors, especially while binding a queue to an exchange. > > * If the exchange does not exist the creation of the binding returns > 404 where I would

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

+1 on ending support for Java 7 in Proton-J Do we actually document anywhere which versions of Java we "support"/have tested on for the various Java components? On a cursory look through the website and READMEs I didn't see anything, except for the AMQP 0-x JMS client claiming to support "Java 7

  1   2   3   4   5   6   7   8   9   >