+1
Verified checksum
Tested with proton 0.35 debug build
Debug build
Passes self tests
On Tue, Aug 10, 2021 at 6:00 PM Ken Giusti wrote:
> Folks,
>
> Please cast your vote on this thread to release RC1 as the official
> Qpid Dispatch Router version 1.17.0.
>
> RC1 of Qpid Dispatch Router vers
There is a design issue with the fallback destination handling when the
presence of a fallback receiver is known *before* the associated primary
receiver. Please see issue
https://issues.apache.org/jira/browse/DISPATCH-1786 and the attachment
https://issues.apache.org/jira/secure/attachment/1302893
+1
* download, verify checksum
* build Debug from source - passes self test
* build qpid-dispatch 1.16.1-rc1 - passes self test
* build qpid-dispatch main@25478 - passes self test
On Fri, Jun 25, 2021 at 11:05 AM Robbie Gemmell
wrote:
> Hi folks,
>
> I have put together a first spin for a Qpid
+1
* scrutinized commits since 1.16.0
* check checksum check checks
* built debug build from source using proton 0.34.0 on Fedora 33
* passes local self tests
* ran several non-selftest tests
On Mon, Jun 28, 2021 at 2:33 PM Ken Giusti wrote:
> Folks,
>
>
> Please cast your vote on this thread
Hi Rakhi,
Welcome! Good to have you aboard.
--Chuck
- Original Message -
> From: "Rakhi Kumari"
> To: "users"
> Sent: Tuesday, May 25, 2021 1:27:57 PM
> Subject: Outreachy Intern
>
> Hi everyone!
>
> I am Rakhi Kumari from India. I’ll be contributing to Apache Qpid Proton as
> an Out
+1
* verified checksum
* built from source using proton 0.34.0
* ran self tests
* ran 12-router test network exercising AMQP and TCP
* additionally cherrypicked DISPATCH-2100 TCP half-closed self test: passes
- Original Message -
> From: "Ken Giusti"
> To: users@qpid.apache.org
> Sent:
+1
* built from source kit on fedora fc32.x86_64
* passes self test
* built qpid-dispatch main branch - passes self tests
- Original Message -
> From: "Robbie Gemmell"
> To: "users"
> Sent: Tuesday, April 6, 2021 9:31:21 AM
> Subject: [VOTE] Release Apache Qpid Proton 0.34.0
>
> Hi fo
Every bullet point in the original message names an issue that was a
serious problem until recently. No requests-per-second number are worth
anything if the product fails out from under it.
I am pleased to hear about meeting this milestone and look forward to
more improvements and better numbers i
Yes. But not in a traditional IP Router or Load Balancer sense.
A qpid-dispatch router is not routing IP addresses or rewriting L2 traffic
to forward low-level network packets between the two networks.
Instead qpid-disptach is completely terminating the traffic at L7, the
Application Layer,
on
The qpid-dispatch network security model is connection based. The connection
over which a user connects to the network determines that user's policy
restrictions. Once a user has connected and performed an allowed operation at
the ingress connection then the rest of the network passes the reques
+1 Thanks for planning this. --Chuck
- Original Message -
> From: "Robbie Gemmell"
> To: "users"
> Sent: Thursday, March 11, 2021 7:21:55 AM
> Subject: [DISCUSS/NOTICE] Renaming default git repo branches to "main"
>
> Hi folks,
>
> I would like to propose renaming our git repository de
This note is about the qpid-dispatch 1.16 content and features.
The schedule discussion is separate in a thread titled "[dispatch-router]
1.16.0 release schedule".
This note summarizes
TCP Adaptor
---
* DISPATCH-1968 fixed a memory corruption/crash issue.
See https://issues.apache.or
Http2 adaptor uses 16k (or so) -byte buffers between the adaptor and proton
raw connection. The TCP adaptor could probably use the http2 buffering scheme
and amortize the cost of doing a buffer copy between the 16k byte buffers and
the normal dispatch buffers by doing fewer scheduling turns and sti
The mail list scrubs attachments. Maybe create a jira and add the image
to that.
- Original Message -
> From: "Michael Goulish"
> To: users@qpid.apache.org
> Sent: Friday, February 12, 2021 2:43:40 AM
> Subject: Re: Dispatch Router: Changing buffer size in buffer.c blows up AMQP.
>
> *Ca
+1
* downloaded and checked sha512
* built debug build using proton master@537d7af8f
* passes all self tests
* runs iperf over TCP adaptor on localhost
- Original Message -
> From: "Ganesh Murthy"
> To: users@qpid.apache.org
> Sent: Monday, February 8, 2021 10:41:17 AM
> Subject: [VOTE]
+1
* verified checksum of src and bin bundles
* built from source
* ran automated tests
- Original Message -
> From: "Robbie Gemmell"
> To: "users"
> Sent: Monday, December 14, 2020 12:11:11 PM
> Subject: [VOTE] Release Apache Qpid JMS 0.56.0
>
> Hi folks,
>
> I have put together a sp
ide/index.html#configuring-authorization-qdr
>
> >
> > Do you have any ideas how to mitigate this or maybe this shouldn't
> > actually deserve any serious concerns?
> >
> > Thank you.
> >
> > -Original Message-
> > From: Chuck Rolke
Also, do not build the image with certificates embedded within it.
Find a way to inject the connection secrets into the container
as it is launched.
- Original Message -
> From: "Ted Ross"
> To: users@qpid.apache.org
> Sent: Friday, November 20, 2020 10:53:45 AM
> Subject: Re: Edge rout
+1
- downloaded; checked sha512
- built debug build; ran self tests
- built against dispatch dev-protocol-adaptors-2 branch; ran self tests
- Original Message -
> From: "Robbie Gemmell"
> To: users@qpid.apache.org
> Sent: Tuesday, November 17, 2020 7:32:53 AM
> Subject: [VOTE] Release Ap
+1
* built from source tag
* passes self test
* consumed build with qpid-dispatch
* dispatch passes self test
* ad-hoc multi system tests with 1000s of AMQP connections
* dispatch dev-prototol-adaptors-2 testing with raw connections
- Original Message -
> From: "Robbie Gemmell"
> To: use
When the receiver starts then the sender gets (by default) 250 credits.
As long as the receiver is there the credits keep getting replenished.
When the receiver exits then the router stops giving the sender new
credits. The sender still can send the 250 messages to use up the
current credits. If y
- Original Message -
> From: "Robbie Gemmell"
> To: "dev"
> Cc: users@qpid.apache.org
> Sent: Friday, September 11, 2020 9:41:16 AM
> Subject: Re: [VOTE] Release Qpid Dispatch Router 1.14.0 (RC1)
>
> On Wed, 9 Sep 2020 at 22:01, Ganesh Murthy wrote:
> >
> > Hello All,
> > Pl
elease Apache Qpid Proton 0.32.0
>
> On Thu, 20 Aug 2020 at 20:25, Andrew Stitcher wrote:
> >
> > On Thu, 2020-08-20 at 14:50 -0400, Chuck Rolke wrote:
> > > -1
> > >
> > > * checksum matches
> > > * built debug build
> > > * thread
- Original Message -
> From: "Andrew Stitcher"
> To: users@qpid.apache.org
> Sent: Thursday, August 20, 2020 3:25:46 PM
> Subject: Re: [VOTE] Release Apache Qpid Proton 0.32.0
>
> On Thu, 2020-08-20 at 14:50 -0400, Chuck Rolke wrote:
> > -1
> >
-1
* checksum matches
* built debug build
* threaderciser self test fails hard with timeout
Issues with the test:
- test does not honor ctest --timeout switch. Test always uses 120 seconds.
- test times out with Debug, RelWithDebInfo, and Release builds
Investigating a little:
- Sometimes tak
+1
* Checked sha512sum
* Built debug from source against master proton on fedora 31
* passes self test several times
* ran ad-hoc network tests over a few days (at commit 2348f53) OK
- Original Message -
> From: "Ganesh Murthy"
> To: users@qpid.apache.org, d...@qpid.apache.org
> Sent: We
qpid-proton changed architecturally a few years ago.
See https://issues.apache.org/jira/browse/PROTON-1344
The psend.c and precv.c examples were removed under commit id ca45418.
The current, stable, proactor-based replacements are in qpid-proton/c/examples.
- Original Message -
> From:
qpid-dispatch includes some tooling to help with AMQP operations in the router.
https://github.com/apache/qpid-dispatch/tree/master/tools/scraper
To get started use a single router with appropriate logging turned on.
Then run your tests to generate logs:
only a few hundred messages
short uniq
The C library definitely gives you better access to low level features. That
said, it comes at the cost of learning the proton-c way of doing things. See
https://github.com/apache/qpid-proton/blob/7abcfc7aba6cfd1c938324cf34a51555c845a589/c/examples/send.c#L58
for constructing a message that has a
+1
* verified checksum
* passes proton self test
* built qpid-dispatch - passes dispatch self test
- Original Message -
> From: "Robbie Gemmell"
> To: users@qpid.apache.org
> Sent: Thursday, May 7, 2020 12:06:35 PM
> Subject: [VOTE] Release Apache Qpid Proton 0.31.0 (RC3)
>
> Hi folks,
+1
* Verified signature/checksum
* Built debug
** Pass selftests
* Built relwithdebinfo
** Ran various performance tests against qpid-dispatch 1.12
** Ran ad-hoc networks with long term connect-reconnect processes
Note: building Debug build, Fedora 29, Python 3.7.4 issues several warnings:
/home
+1
* Ran system self tests (using current qpid-proton master)
* Ran ad-hoc 12-router tests
* Ran connect-disconnect exercisers
* Ran policy and oversize message tests
- Original Message -
> From: "Ganesh Murthy"
> To: d...@qpid.apache.org, users@qpid.apache.org
> Sent: Monday, April 27,
+1
* Verified checksum
* Ran tests on Fedora 29 python2 and python3 systems:
** pass self test
** ad hock 12-router formerly-problematic network: OK
** verified console and multiple consoles: OK
** 100s of thousands of connections during multicast tests: OK
- Original Message -
> From: "G
+1
* downloaded src and bin packages
* checksums ok
* build/install
* run helloworld example against qpid-dispatch router triggering various policy
denials
- Original Message -
> From: "Robbie Gemmell"
> To: users@qpid.apache.org
> Sent: Monday, February 24, 2020 6:35:11 AM
> Subject: [
Hi Oliver,
That test should work with python27. Please raise a jira for this.
As it stands the test does not leave a paper trail of why the test failed.
Useful information would be produced by patching the test and including the
output
generated by
'ctest -VV -R system_tests_bad_configuration'
- Original Message -
> From: "Francesco Raviglione"
> To: users@qpid.apache.org
> Sent: Saturday, February 8, 2020 5:36:39 AM
> Subject: Avoiding aggregation of "transfer" messages in Qpid Proton
>
> Hello,
> I'm sorry about the several questions I'm posting on the mailing list
> durin
-1 A segfault has been identified.
https://issues.apache.org/jira/browse/DISPATCH-1523
- Original Message -
> From: "Ganesh Murthy"
> To: users@qpid.apache.org, d...@qpid.apache.org
> Sent: Thursday, December 12, 2019 1:32:39 PM
> Subject: [VOTE] Release Qpid Dispatch Router 1.10.0 (RC1)
loses with a framing error.
Jira on the way.
- Original Message -
> From: "Chuck Rolke"
> To: users@qpid.apache.org
> Sent: Tuesday, December 10, 2019 6:07:51 PM
> Subject: Re: [VOTE] Release Apache Qpid Proton 0.30.0
>
> +1
>
> Built from sourc
I have not run qpid-cpp on windows in a few years (since boost 1-65) and I have
never run HA on Windows. But there are some standard operating procedures you
can use to see what's wrong. The first is logging. Try turning on logging to
full trace for the HA module, or for the entire broker for th
+1
Built from source tag.
* Fedora 29
* Passes BIST
* Linked with qpid-dispatch master and that passes BIST
* Ran several qpid-dispatch router scenarios and router tools
- Original Message -
> From: "Robbie Gemmell"
> To: users@qpid.apache.org
> Sent: Monday, December 9, 2019 10:59:42 A
- Original Message -
> From: "Gordon Sim"
> To: users@qpid.apache.org
> Sent: Thursday, November 7, 2019 10:00:47 AM
> Subject: Re: multicast without consumers
>
> On 07/11/2019 2:58 pm, Chuck Rolke wrote:
> > When vhost policy is in force th
> 1) All non-anonymous producer links will only be granted credit when the
> router is aware of at least one consumer. This applies to all of the
> address treatments uniformly (multicast, anycast, balanced, closest, ...)
>
> 2) Declare the fix to DISPATCH-779 invalid and change the JIRA's state
+1
* Passes checksum verify
* Build and pass self tests
* Run local test environment stress test OK.
Note: observed issue described in DISPATCH-1423.
That issue is also present in 1.8.0 and is not a regression
- Original Message -
> From: "Ganesh Murthy"
> To: users@qpid.apache.org, d.
-1
There's a race where lots of connect-receive_one_message-disconnect cycles
eventually core dump when the system tries to process a freed connection.
- Original Message -
> From: "Ganesh Murthy"
> To: d...@qpid.apache.org, users@qpid.apache.org
> Sent: Monday, September 9, 2019 5:35:59
1. A naked qdstat return "Router statistics" is a good idea.
A naked qdstat return an error is annoying.
2. The simple "--all-routers" returning "--all-routers --all-entities" is too
much.
Changing "--all-routers" with no other switches to be "--all-routers -g" is
better.
+1 to both suggestion
+1
* verified checksum
* built from source
* passes self test
* built into dispatch; dispatch passes self test
* ran test with simple dispatch network and proton cpp clients: OK
- Original Message -
> From: "Timothy Bish"
> To: users@qpid.apache.org
> Sent: Tuesday, August 13, 2019 3:33:
+1
* Checked checksums
* Build/test Fedora 29, python 3
* Fails system_tests_http (known problem, not a regression)
* Build/test Fedora 28, python 2
* Occasional test fail system_tests_fallback_dest
known problem in new test code and not in mission code; fix is already on
master; not a r
+1
* Verified signatures
* Built on (Fedora 28, python2) and (Fedora 29, python3)
* Passes self tests
* Built into qpid-dispatch master, passes self tests
Note: did not test tornado external event loop example
- Original Message -
> From: "Robbie Gemmell"
> To: users@qpid.apache.org
> S
hese IDs...
> For example in the "Log data" when a receiver attaches to a queue I get the
> real name in the source:
> attach [1,0] receiver link_24 (source: "myQueue", target: none, class:
> client)
> But when a producer attaches to a topic I only get the ID:
> a
Hi Olivier,
I've developed tooling to help find problems like the one you describe.
Could you give it a try?
To use it:
1. Turn on trace logging. For the most part just SERVER trace+ will do it
but DEFAULT trace+ gets the most detail. Save each router's log to a separate
file.
Add something like
+1
* Built from source
* Ran self tests
* Ran local multi-system qpid-dispatch router network with multiple consoles
coming and going
- Original Message -
> From: "Robbie Gemmell"
> To: users@qpid.apache.org
> Sent: Monday, April 15, 2019 1:42:15 PM
> Subject: [VOTE] Release Apache Qpi
+1
* Built from source with qpid-proton 0.27.1-rc1
* Ran self tests
* Ran local multi-system network with multiple consoles coming and going
- Original Message -
> From: "Ganesh Murthy"
> To: d...@qpid.apache.org, users@qpid.apache.org
> Sent: Friday, April 12, 2019 2:40:25 PM
> Subject
An easy thing to try would be to turn on protocol logging. In qpidd.conf
file or on the command line add
--log-enable trace+:Protocol
This would expose what led up to the session being rejected. The protocol
logs will show if the broker is spontaneously closing the session or if
the client(s)
+1
* built from source
** fedora 29 python 2.7.15
** fedora 28 python 3.6.6
* passes self tests
** fedora 29: all
** fedora 28: fails authz. See
https://issues.apache.org/jira/browse/DISPATCH-1304
Passes with workaround
- Original Message -
> From: "Ganesh Mu
-1 see https://issues.apache.org/jira/browse/DISPATCH-1301
Self tests fail randomly: system_tests_management, system_tests_one_router, and
system_tests_two_routers. In each case a management request message goes into
the router and the router never acts on it.
This is a new behavior after the f
Delete the section that has the "telemetry" "in". Otherwise the router will
connect and read messages from that address thus competing with your other
consumers.
The phase numbers help stage message flow through the router. Since there is
only one autoLink, don't specify a phase in the config. The
I just filed https://issues.apache.org/jira/browse/PROTON-2005
This is not a regression but it would be good to be included in the next
release.
- Original Message -
> From: "Robbie Gemmell"
> To: users@qpid.apache.org
> Sent: Wednesday, February 6, 2019 9:01:57 AM
> Subject: [VOTE] Rel
+1
* Built on Fedora 29, python 2
* Ran self tests
* Ran limited number of C examples stand-alone
* Built with qpid-dispatch and passed dispatch self tests except
system_tests_ssl [1]
[1] Dispatch relies on proton ssl version selection code which is suffering
from software rot.
Please get t
+1
* Fedora 29, Python 2.7.15, qpid-proton master, openssl v1.1.1
* Verified signatures
* Built from source, ran self tests (observed issue with ssl self test as noted)
* Ran cursory local network tests - all normal
- Original Message -
> From: "Ganesh Murthy"
> To: users@qpid.apache.or
+1 [Note]
* Built with proton master@ffe4915
* Self tests pass on Fedora 27
* Runs local network tests on F27 and F29
[Note]
* One self test fails with Fedora 29. This is an issue with
the ssl libraries on Fedora 29 as the kit works fine on
Fedora 27. I do not think this is a regression.
49
+1 to migrate asap.
-Chuck
- Original Message -
> From: "Robbie Gemmell"
> To: users@qpid.apache.org, d...@qpid.apache.org
> Sent: Monday, December 10, 2018 11:10:10 AM
> Subject: [NOTICE / DISCUSS] migrating Git repositories to gitbox.apache.org
>
> Hi Folks,
>
> Per the below mail se
The trace frames are the deepest details of the AMQP communication channels.
If you don't know AMQP that well you can start at
https://github.com/xinchen10/awesome-amqp or
https://dzone.com/refcardz/amqp-essentials
- Original Message -
> From: "akabhishek1"
> To: users@qpid.apache.org
This sounds like an architecturally wrong fit for a dispatch router and
like a better fit for a message broker. The router has no place to store
messages and it is not an endpoint capable of taking ownership of messages.
See docs/books/user-guide/theory_of_operation.adoc, section Message Routing/
Supporting issues like this on a mailing list is not workable.
Please log in the the qpid-dispatch jira instance
https://issues.apache.org/jira/projects/DISPATCH and create an issue describing
your product versions, setup, and problem or improvement description. Tracking
the issue is much easie
Hi basavaraj,
The issue here is that the broker wants to negotiate a SASL layer but the
Proton C++ example is skipping that during connection startup. AMQP allows
startup options SASL and TLS before jumping into an AMQP session. SASL provides
authentication variants and TLS provides authenticat
Those get set up when you run qpid-tool. Your qpid-tool instance and the broker
communicate through them.
If you stop your qpid-tool instance then the queues will disappear.
- Original Message -
> From: "rammohan ganapavarapu"
> To: "users"
> Sent: Saturday, October 27, 2018 3:32:18 PM
+1
* Fedora 27, proton master
* Checksums pass
* Compile, run self test
* Set up multi-router test network and run various tests
- Original Message -
> From: "Ganesh Murthy"
> To: users@qpid.apache.org
> Sent: Thursday, October 25, 2018 9:59:55 AM
> Subject: [VOTE] Release Qpid Dispatch
+1
* Fedora 27, proton master @aa85a
* Verified signatures
* Built from source
* Passed self tests [1], [2]
* Ran qpidd executable and hit it with proton examples
[1] on first run 'cli_tests' failed; reran 5 time with no issue
[2] 'paged_queue_tests' times out. Disabled valgrind and it passes.
-
+1
* Fedora 27, latest qpid-proton (aa85a)
* passes checksum
* compiles cleanly including console
* runs self test
- Original Message -
> From: "Ganesh Murthy"
> To: users@qpid.apache.org
> Sent: Tuesday, October 23, 2018 10:42:42 AM
> Subject: [VOTE] Release Qpid Dispatch Router 1.4.1
conditional +1
* Fedora 27, proton master
* checksums check
* build/test *without console* OK
Console requires packages that get downloaded from github,
github is inaccessible, and so the console build fails.
Will test again when github is back on line.
- Original Message -
> From: "Gan
+1
verif checksum
Built with proton master@aa85a on fc27 x64
Ran self test
Ran local smoke tests
- Original Message -
> From: "Ganesh Murthy"
> To: users@qpid.apache.org
> Sent: Friday, October 12, 2018 11:11:16 AM
> Subject: [VOTE] Release Qpid Dispatch Router 1.4.0 (RC1)
>
> Hello Al
+1 (with note)
* Fedora 27 - running version at release tag for several days
* Checksums check
* passes self test (note)
Note: Building from source, not installed, and running tests:
mkdir build
cdbuild
cmake -DCMAKE_BUILD_TYPE=Debug -DCMAKE_INSTALL_PREFIX=/opt/local ..
make -j 8
m
This was discussed in https://issues.apache.org/jira/browse/QPID-7926
I'm not sure how far the resolution made it into the upstream source.
- Original Message -
> From: "Paul A. Flores"
> To: users@qpid.apache.org
> Sent: Tuesday, September 11, 2018 5:50:55 PM
> Subject: Visual Studio Co
I'd put the signature in part of the 'bare message', such as application
properties, which passes from sender to receiver unmodified.
See
https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=1&ved=2ahUKEwiEzeqL0LjdAhVIGt8KHeuOAHEQFjAAegQIABAC&url=http%3A%2F%2Fdocs.oasis-open.org%2Famqp%
+1
* Fedora fc27.x86_64
* Passes checksums
* Builds and passes self test
* linked with qpid-dispatch master and that passes self tests
- Original Message -
> From: "Robbie Gemmell"
> To: users@qpid.apache.org
> Sent: Monday, September 3, 2018 11:08:36 AM
> Subject: [VOTE] Release Apache
+1
* verified checksum
* built from source using proton master@38a8a on Fedora 27
* self tests pass first try
* ran as target of some client tests
- Original Message -
> From: "Ganesh Murthy"
> To: users@qpid.apache.org
> Sent: Tuesday, August 7, 2018 3:07:16 PM
> Subject: [VOTE] Releas
+1
* Verified download
* Fedora 27
* Built against proton 0.24-rc1 tag
* Self tests pass
- Original Message -
> From: "Ganesh Murthy"
> To: users@qpid.apache.org
> Sent: Friday, June 29, 2018 3:21:48 PM
> Subject: [VOTE] Release Qpid Dispatch Router 1.2.0 (RC2)
>
> Hello All,
>
>
+1 (on Fedora Linux 4.16.7-200.fc27.x86_64 #1 SMP)
* verified kit checksum
* build/install
* passes self test
* included in qpid-dispatch (current master) build
* passes dispatch self test
* set up local router network and pass millions of messages
- Original Message -
> From: "Robbie Gem
+1
* Runs self tests (Note: proton master has issues[1] but proton 0.23 is fine)
* Runs correctly in other test arrangements
[1] One self test has a connection address that used to work (proton 0.23)
but now does not (proton master). This test is fixed in dispatch master.
- Original Message
Hi,
I cut and pasted your configuration and it came up OK. The console trace for
startup is appended.
In the policy section you will need the clause:
enableVhostPolicy: true
to get the policy turned on. But I don't see anything in your configuration
that should be a problem
Are you sure you
+1
* Built from source with Proton at d28fecf, three commits after 0.23.0.
* Ran self tests
- Original Message -
> From: "Ganesh Murthy"
> To: users@qpid.apache.org
> Sent: Friday, May 25, 2018 5:45:30 PM
> Subject: [VOTE] Release Qpid Dispatch Router 1.1.0 (RC4)
>
> Hello All,
>
>
Releasing the messages sounds like the better choice.
It also would be nice if the router could revoke the sender's credit so
that he could not send any more. This would create the same state as
when the sender attaches and there's no receiver available. Kind of like
a receiver-initiated drain.
O
1, 2018 7:53:15 PM
> Subject: Re: [VOTE] Release Qpid Dispatch Router 1.1.0 (RC2)
>
> I checked and the tip of the branch 1.1.x and the tag 1.1.0-rc2 are botth
> at commit
>
> 4fb04f463c6b0f9e1b8b0d9b1b9f2dfa87df12b7
>
>
>
> On Tue, May 1, 2018 at 6:19 PM, Chuck Ro
M
> To: users@qpid.apache.org
> Subject: Re: DOTNET Binding Availablity
>
> Thanks!
>
>
>
> From: Chuck Rolke
> Sent: Tuesday, May 1, 2018 3:40 PM
> To: users@qpid.apache.org
> Subject: Re: DOTNET Binding Availablity
>
> No. T
+1 [see note 1]
* Checked sha512
* Built with recent Proton (3e49ede)
* Self tests pass 100%
* Ran a couple of local test router network scenarios
[1] Apparently the distribution was created at the tip of the 1.1.x branch
(4fb04f) and not at the 1.1.0-rc2 tag (c6fac9).
Moving the tag will help f
No. The qpid-cpp binding for dotnet has fallen into disuse and has
not been maintained for a couple of years.
For .NET I have been using https://github.com/Azure/amqpnetlite
which is a lightweight, native library. It does not have the same API
as qpid-cpp messaging but it is closely coupled with A
I would prefer to keep the feature enforced as it is now. I was one who
was surprised to have a sender whose message is settled by the router
only to find out that it was not delivered anywhere.
The document
https://qpid.apache.org/releases/qpid-dispatch-1.0.0/book/book.html#routing-patterns
nee
endencies in
https://github.com/ChugR/qpid-proton-tools/tree/master/bat
Files build_proton.bat and build-qpid-cpp.bat took care of steps 2 and 3 shown
above.
>
> On Thu, Apr 5, 2018 at 4:12 AM, Chuck Rolke wrote:
>
> > I tried a build of the qpid-cpp latest master upstream tod
I tried a build of the qpid-cpp latest master upstream today using:
Windows Server 2012 R2
Visual Studio 2013 x64
boost 1_58_0
cmake version 3.9.4
Python 2.7.10
ruby 1.8.6 (2007-09-24 patchlevel 111) [i386-mswin32]
Note that I did not include qpid-proton in this build. Also I am not on
Windows 10
+1
* Checked checksums
* Built with master proton master at 3c80d6f4
* Self tests FAILED:
21/26 Test #21: paged_queue_tests ***Timeout 1500.02 sec
* Rebuilt with valgrind disabled
* Self tests pass 100%
My local machine is generally high performance and I'm surprised to have
th
Good work. These changes will be a great candidate to test with
qpid-interop to make sure that it still works with the other
implementations. And if not then why not.
- Original Message -
> From: "Andrew Stitcher"
> To: "Qpid Users"
> Sent: Friday, March 2, 2018 11:06:18 AM
> Subject: I
+1
* Verified sha512
* Build/install on fedora 27
* Pass self tests
* Build/install with current qpid-dispatch master
* Pass self tests
- Original Message -
> From: "Robbie Gemmell"
> To: users@qpid.apache.org
> Sent: Wednesday, February 28, 2018 2:33:29 PM
> Subject: [VOTE] Release Apac
+1
* Verified signatures
* Passed self tests using today's master proton b6b3dd6
- Original Message -
> From: "Ted Ross"
> To: users@qpid.apache.org
> Sent: Tuesday, February 20, 2018 3:27:38 PM
> Subject: [VOTE] Release Qpid Dispatch Router 1.0.1 (RC1)
>
> Please vote on this thread to
- Original Message -
> From: "Gordon Sim"
> To: users@qpid.apache.org
> Sent: Tuesday, February 20, 2018 3:36:37 PM
> Subject: Re: C++ Broker Performance with large messages
>
> On 20/02/18 16:51, andi welchlin wrote:
> > Hello all,
> >
> > I tested throughput of the Qpid C++ Broker (c
For the qpidd C++ broker the answer is no. Policy limits are available to
control the number of connections to the broker and by the number of queues
users may create.
- Original Message -
> From: "Michael Ivanov"
> To: users@qpid.apache.org
> Sent: Thursday, February 8, 2018 12:52:58 P
+1
* verified sha512
* verified release tag is at a good spot in git
* built, ran self tests OK
* built qpid-dispatch, ran self tests OK
* ran dispatch local test network OK
- Original Message -
> From: "Robbie Gemmell"
> To: users@qpid.apache.org
> Sent: Thursday, January 25, 2018 9:51:
Referring to
http://qpid.apache.org/releases/qpid-cpp-1.37.0/cpp-broker/book/chap-Messaging_User_Guide-Security.html#sect-Messaging_User_Guide-Authorization-Specifying_ACL_Queue_Limits
Queue limits are disabled unless there is an ACL file with a 'quota queues'
entry.
As an aid to understanding
Hello Daniel,
Your attachment got scrubbed. You could create a Jira and attach the
information to that.
https://issues.apache.org/jira/projects/QPID/issues/QPID-8075?filter=allissues
It would help if you could start with a clean build area before you run cmake.
Then include the cmake output
Hi Hiba,
In order for SSL to start up there needs to be a handshake (client and server
sending information back and forth) in order for them to agree on the SSL
version number and the encryption secrets. See [1] for details.
AMQP connections without SSL are "in the clear" meaning that there is
+1
on Fedora 27
* Verified checksum
* ran selftests [1]
* linked with qpid-dispatch master
* ran qpid-dispath selftests
[1] On first go self qpid-proton test failed. The fail on qpid-proton master,
too.
Had to upgrade valgrind to 3.13.0-12 then they pass in 0.19.0-rc2 and master.
- Origina
1 - 100 of 334 matches
Mail list logo
