RE: multicast without consumers

Hello, First, thank you guys for the quick reply/analysis. We should be able to unblock our client by upgrading their dispatch-router version to 1.9.0. Now this is only a short term solution. Indeed if DISPATCH-1423 makes it the master we won't be able to upgrade to newer versions of the dispat

RE: multicast without consumers

Hello, Regarding the multicast , what will be the behavior in 1.10.0 if all *present* subscribers do not return the same acknowledgment? Thanks, Olivier -Original Message- From: Ken Giusti Sent: jeudi 7 novembre 2019 17:11 To: users Subject: Re: multicast without consumers On Thu, No

Broker-J statistics and CPU consumption

Hello, We're using the Broker-J 7.1.3. Looking at the statistics provided by /api/latest/broker/getStatistics, I don't see anything related to the CPU consumption. Did I miss something or this information is not provided? Thanks, Olivier *** This e-mail contains infor

RE: Broker-J statistics and CPU consumption

is more properly reported using some sort of external monitoring tool. > > -- Rob > > >> >> Kind Regards, >> Alex >> >> On Fri, 15 Nov 2019 at 16:31, VERMEULEN Olivier < >> olivier.vermeu...@murex.com> >> wrote: >> >> > H

Dispatch-Router statistics and CPU consumption

Hello, We're using the Dispatch-Router 1.9.0. Is there a way, using the AMQP management of the Dispatch-Router, to retrieve statistics like the CPU consumption? Thanks, Olivier *** This e-mail contains information for the intended recipient only. It may contain propr

RE: Dispatch-Router statistics and CPU consumption

ess to the AMQP management. Regards, Olivier -Original Message- From: Ganesh Murthy Sent: lundi 18 novembre 2019 14:20 To: users@qpid.apache.org Subject: Re: Dispatch-Router statistics and CPU consumption On Mon, Nov 18, 2019 at 3:51 AM VERMEULEN Olivier < olivier.vermeu...@mur

High number of transfers between Broker-J and Dispatch-Router

Hello, First let me explain the setup. We have 1 Broker-J (version 7.1.3) with 1 queue. We have 1 Dispatch-Router (version 1.9.0) with 1 waypoint address and 1 out auto-link. The queue contains 10 messages. When I create a JMS consumer (with jms.prefetchPolicy.all=1), consume 1 message and clos

RE: High number of transfers between Broker-J and Dispatch-Router

Hello, Thanks for the analysis. And sorry I actually forgot to mention what we were expecting here. We know about the dispatch-router 250 pre-fetch and we're very much counting on that for performance. What we were not expecting are the 2 round-trips of the 9 remaining messages between the broke

RE: [VOTE] Release Qpid Broker-J 7.1.6

+1 Launched our validation pipeline which includes: - basic sends and receives - basic routing and filtering - JDBC message and config stores - message recovery - HTTP management and statistics - TTL, max queue size and max message size - SSL and SASL - performance benchmark Olivier -Origina

RE: [VOTE] Release Qpid Broker-J 7.1.7

+1 Launched the Murex validation pipeline which includes: - basic sends and receives - basic routing and filtering - JDBC message and config stores - message recovery - HTTP management and statistics - TTL, max queue size and max message size - SSL and SASL - performance throughput and latency Ol

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

Hello, We would like to contribute the support of SQL Server by the Broker-J JDBC store. But before doing the dev I just wanted to make sure that there is no restrictions on your side? Thanks, Olivier *** This e-mail contains information for the intended recipient on

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

he same as supporting one of the other proprietary database vendors). Given their common roots, I assume the SQL server configuration will be mostly similar to the Sybase configuration (I think I may even have tested this many many years ago). -- Rob On Wed, 29 Jan 2020 at 09:47, VERMEULEN Oliv

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

today or over the weekend. Kind Regards, Alex On Thu, 6 Feb 2020 at 20:51, VERMEULEN Olivier wrote: > Hello, > > I see that my pull-request has been approved, great. > When will be the next release of the Broker-J ? > We have a client asking for this SQL Server support and they ar

RE: [VOTE] Release Qpid Broker-J 7.1.8

+1 Launched the Murex validation pipeline which includes: - basic sends and receives - basic routing and filtering - JDBC message and config stores - message recovery - HTTP management and statistics - TTL, max queue size and max message size - SSL and SASL - performance throughput and latency Ol

[Dispatch Router] unit test failure on master

Hello, We are monitoring the dispath-router master branch on our own CI. It has been consistently failing for the path 2 weeks with the error below. Those 2 tests were introduced by DISPATCH-1553. Is it also failing on your side or is it a configuration issue on ours? Thanks, Olivier test 49

RE: [Dispatch Router] unit test failure on master

TestCase): > stdin=PIPE, stdout=PIPE, stderr=STDOUT, expect=Process.EXIT_FAIL, > universal_newlines=True) > out = p.communicate(timeout=5)[0] > +print("ctrl-char out:", out) > try: > p.teardown() > e

[Broker-J] Claim-check pattern and MessageDeleteListener

Hello, We're trying to implement the claim-check pattern on top of our broker + dispatch-router topology. So we have a blob store and the idea is for each message above 10KB to store the payload in it and to only keep an ID in the message. The tricky part is the delete of the payload in the blob

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

y view of the message). Without such an interception extension mechanism, you are correct I think that you would need to create a new vhost type (potentially using a new store type of your own implementation) -- Rob On Fri, 6 Mar 2020 at 16:37, VERMEULEN Olivier wrote: > Hello, > > We'

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

/apache/qpid/server/store/jdbc/AbstractJDBCMessageStore.java#L1670 Olivier -Original Message- From: Rob Godfrey Sent: lundi 9 mars 2020 09:58 To: users@qpid.apache.org Subject: Re: [Broker-J] Claim-check pattern and MessageDeleteListener On Mon, 9 Mar 2020 at 09:36, VERMEULEN Olivier wrote

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

" trigger which is passed the message it is about to be permanently removed from the queue). -- Rob On Tue, 10 Mar 2020 at 17:59, VERMEULEN Olivier wrote: > The cast works fine in my case but the problem is that everything is NULL, > including the meta-data. > Indeed the mess

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

o add a getter in StorableMessageMetaData). I can provide a pull-request if you want. WDYT? Olivier From: VERMEULEN Olivier Sent: mardi 10 mars 2020 20:08 To: users@qpid.apache.org Subject: Re: [Broker-J] Claim-check pattern and MessageDeleteListener The idea is to avoid any performance impa

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

from many queues on the same broker From: Rob Godfrey Sent: Wednesday, March 11, 2020 10:01:43 AM To: users@qpid.apache.org Subject: Re: [Broker-J] Claim-check pattern and MessageDeleteListener On Wed, 11 Mar 2020 at 09:46, VERMEULEN Olivier wrote: > Why do

RE: [VOTE] Release Qpid Broker-J 8.0.2

+1 Launched our validation pipeline which includes: - basic sends and receives - basic routing and filtering - JDBC message and config stores - message recovery - HTTP management and statistics - TTL, max queue size and max message size - SSL and SASL One remark regarding the list of JIRAs though

Qpid Broker-J next release

Hello ! Quick question, when is the next Broker-J release planned ? I'm asking because I'm very interested in the jetty upgrade to 11.0.18 that fixes CVE-2023-44487 Thanks ! Olivier *** This e-mail contains information for the intended recipient only. It may contain

<    1   2