Is it possibly a nagle problem? We always set "tcp_nodelay: true" in our
configs... We also re-use sessions throughout the application lifetime.
On Wed, Dec 9, 2020 at 8:36 AM Toralf Lund wrote:
> I'm still debugging the communication issues I've been struggling with
> for months - where there a
ds of bytes) and queues typically have less than 1MB of data
at any given time.
Thanks,
Chester
On Thu, Feb 28, 2019 at 8:08 AM Gordon Sim wrote:
> On 27/02/2019 11:29 pm, Venkat Jaligama wrote:
> > Hello Users,
> >
> >
> > We are having issue with memory of one of our pr
2018-10-22 07:39:02 [Broker] warning Exchange ex-group-1 cannot deliver to
queue prod-queue-01: resource-limit-exceeded: Maximum depth exceeded on
prod-queue-01: current=[count: 12567, size: 1073741816], max=[count:
100, size: 1073741824]
(/builddir/build/BUILD/qpid-cpp-1.35.0/src/qpid/brok
Looks like this may already been in, but if it isn't, we would love to have
it included:
https://issues.apache.org/jira/browse/QPID-8221
[qpid-cpp] Client open connections to broker and waits forever
Thanks,
Chester
On Tue, Oct 16, 2018 at 4:11 PM Justin Ross wrote:
> Hi, all. I
passing, but the build is marked
successful. Is this by intent?
Thanks,
Chester
https://www.clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html/Clusters_from_Scratch/index.html
will get you started with pacemaker. The DRBD walkthrough is easy enough to
follow to start understanding the clustering system.
For qpidd, you'll need the following resources:
1. qpidd service clone (1
Try using user/password instead of user:password in your connection string:
container.Dial(“tcp”, “amqps://USER/PASSWORD@ENDPOINT:5671/ENTITY”)
This follows the pattern I know to work with the cli tools:
qpid-stat amqps://USERNAME/PASSWORD@localhost:5672 -q
> On Oct 17, 2017, at 7:48 PM, Br
Thanks, Gordon! That made the difference.
Is there a doc somewhere that I've overlooked that describes the available
keys?
On Mon, May 8, 2017 at 3:44 AM, Gordon Sim wrote:
> On 05/05/17 21:52, Chester wrote:
>
>> Hi all,
>>
>> I am trying to create a queue with
qpid-cpp-client-devel-1.35.0-3.el7.x86_64
Has anyone else seen this?
Thanks,
Chester
s case.
Thanks,
Chester
On Mon, Apr 24, 2017 at 1:07 PM, Gordon Sim wrote:
> On 19/04/17 21:07, Chester wrote:
>
>> Hello,
>>
>> I'm trying to determine if there is any way to set which network interface
>> is used by the cpp-client. I have a new use case of a
truct the client
which interface/ip it should use? We're using qpid-cpp-client 1.36 on EL7.
Thanks,
Chester
Hey Robbie,
I was wondering when the next release for cpp might be. Specifically, I'm
interested in a build which includes
https://issues.apache.org/jira/browse/QPID-7693 (SSL client socket leaks a
file descriptor).
Thanks,
Chester
On Tue, Dec 13, 2016 at 1:24 PM, Robbie Gemmell
At least for the cpp broker, ssl-require-client-authentication=yes will do
the trick. The broker book (
http://qpid.apache.org/releases/qpid-cpp-0.34/cpp-broker/book/chap-Messaging_User_Guide-Security.html#sect-Messaging_User_Guide-Security-Encryption_using_SSL)
is a good resource for SSL options.
Based on https://issues.apache.org/jira/browse/QPID-6160, it does not
appear to be configurable.
Also no mentions in the broker book that I could find:
http://qpid.apache.org/releases/qpid-0.32/cpp-broker/book/chap-Messaging_User_Guide-Security.html#tabl-Messaging_User_Guide-Enabling_SSL_in_Client
14 matches
Mail list logo