Thank you.Virgilio Fornazin
Does "QMF framework" means qpid-config and qpid-route and so on?
I never use anything about QMF and i cant even use qpid-route because it
report i lack module qmf.console.
But i have already install QPID-broker、C++MessageAPI、PythonMessagAPI.
I am also looking for t
Thank you.Virgilio Fornazin
Does "QMF framework" means qpid-config and qpid-route and so on?
I never use anything about QMF and i cant even use qpid-route because it
report i lack module qmf.console.
But i have already install QPID-broker、C++MessageAPI、PythonMessagAPI.
I am also looking for the so
On Fri, Aug 26, 2016 at 9:39 PM, Matt Broadstone wrote:
> On Fri, Aug 26, 2016 at 7:58 PM, Matt Broadstone
> wrote:
>
>> On Fri, Aug 26, 2016 at 5:44 PM, Matt Broadstone
>> wrote:
>>
>>> On Fri, Aug 26, 2016 at 3:33 PM, Gordon Sim wrote:
>>>
On 26/08/16 20:15, Matt Broadstone wrote:
On Fri, Aug 26, 2016 at 7:58 PM, Matt Broadstone wrote:
> On Fri, Aug 26, 2016 at 5:44 PM, Matt Broadstone
> wrote:
>
>> On Fri, Aug 26, 2016 at 3:33 PM, Gordon Sim wrote:
>>
>>> On 26/08/16 20:15, Matt Broadstone wrote:
>>>
Oops you're sorry I forgot a crucial part there, here's the updat
On Fri, Aug 26, 2016 at 5:44 PM, Matt Broadstone wrote:
> On Fri, Aug 26, 2016 at 3:33 PM, Gordon Sim wrote:
>
>> On 26/08/16 20:15, Matt Broadstone wrote:
>>
>>> Oops you're sorry I forgot a crucial part there, here's the updated code:
>>> const amqp = require('amqp10');
>>>
>>> let client = ne
As a result of the way our credentials are managed internally we’d like to
extend proton-j to enable different mechanisms of SSL configuration and would
be interested in opinions/feedback before we embark on the PR process.
The ask from our Application Security team is that we extend the driver
The artifacts proposed for release:
https://dist.apache.org/repos/dist/dev/qpid/cpp/1.35.0-rc/
Please indicate your vote below. If you favor releasing the 1.35.0 RC bits
as 1.35.0 GA, vote +1. If you have reason to think the RC is not ready for
release, vote -1.
Thanks,
Justin
---
C++ 1.35.
Hi, folks. A little late, here's the release candidate.
Source distribution:
https://dist.apache.org/repos/dist/dev/qpid/cpp/1.35.0-rc/
There's been only one substantive change since beta:
https://git-wip-us.apache.org/repos/asf?p=qpid-cpp.git;a=shortlog;h=refs/tags/1.35.0-rc
Note that the
Thank you Rob, i am also trying to configure JMX, i have added JMX ports in
config and server listening on them but when i try to connect using connect
string "service:jmx:rmi:///jndi/rmi://localhost:8999/jmxrmi" its asking me
credentials but i configured to use Anonymous for that port
Any idea?
On Fri, Aug 26, 2016 at 3:33 PM, Gordon Sim wrote:
> On 26/08/16 20:15, Matt Broadstone wrote:
>
>> Oops you're sorry I forgot a crucial part there, here's the updated code:
>> const amqp = require('amqp10');
>>
>> let client = new amqp.Client();
>> client.connect('amqp://')
>> .then(() => Prom
Hi Ram,
This page from the broker docs covers most aspects of memory configuration:
https://qpid.apache.org/releases/qpid-java-6.0.4/java-broker/book/Java-Broker-Runtime-Memory.html
Hope this helps,
Rob
On 26 August 2016 at 20:49, rammohan ganapavarapu
wrote:
> Yes, i changed it to use Anonym
Yes, i changed it to use Anonymous and its working now. Now i need some
documents or suggestions on how to configure Mem settings and flow to disk
settings in config.json
Thanks,
Ram
On Fri, Aug 26, 2016 at 12:16 PM, Rob Godfrey
wrote:
> Hi Ram,
>
> I assume that you have configured port 5672 t
On 26/08/16 20:15, Matt Broadstone wrote:
Oops you're sorry I forgot a crucial part there, here's the updated code:
const amqp = require('amqp10');
let client = new amqp.Client();
client.connect('amqp://')
.then(() => Promise.all([
client.createSender('test.queue'),
client.createReceiv
On 26/08/16 20:18, Matt Broadstone wrote:
it appears that `release` in the
python client is in fact sending a `modified` outcome!
Sorry! Attached is the fixed example with which I also see the expected
behaviour:
[0x5590136bb570]: -> SASL
[0x5590136bb570]: <- SASL
[0x5590136bb570]:0 <- @s
On Fri, Aug 26, 2016 at 3:15 PM, Matt Broadstone wrote:
> On Fri, Aug 26, 2016 at 3:04 PM, Gordon Sim wrote:
>
>> On 26/08/16 18:50, Matt Broadstone wrote:
>>
>>> Hi all,
>>>
>>> It was my understanding that if you replied to a received message with a
>>> `released` outcome, that the broker woul
Hi Ram,
I assume that you have configured port 5672 to use the Plain auth provider
(each port can only be associated with a single auth provider - you can add
other ports which use the a different auth provider). The issue here is
that by default the Java Broker will not allow PLAIN SASL over a n
On Fri, Aug 26, 2016 at 3:04 PM, Gordon Sim wrote:
> On 26/08/16 18:50, Matt Broadstone wrote:
>
>> Hi all,
>>
>> It was my understanding that if you replied to a received message with a
>> `released` outcome, that the broker would attempt re-delivery to either
>> the
>> link that received it or
On 26/08/16 18:50, Matt Broadstone wrote:
Hi all,
It was my understanding that if you replied to a received message with a
`released` outcome, that the broker would attempt re-delivery to either the
link that received it or some other attached link. Is that correct?
That is correct.
I'm
not
Rob,
I have followed as you said and created a clean slate v6 broker and from UI
created two auth provides palin and anonimous but when i make this api call
i am getting different sasl list
curl -s http://localhost:10001/service/sasl
{
"mechanisms" : [ "CRAM-MD5", "SCRAM-SHA-1", "SCRAM-SHA-256
Hi all,
It was my understanding that if you replied to a received message with a
`released` outcome, that the broker would attempt re-delivery to either the
link that received it or some other attached link. Is that correct? I'm
not seeing this behavior with this simplified use case (using node-a
you must use QMF framework to dinamically bind/unbind topics to exchanges /
queues
On Fri, Aug 26, 2016 at 9:49 AM, lucas wrote:
> I have bound a queue and topic with code:
> "family ; {create:always,node: {type: topic,durable:True,
> x-bindings:[{queue:lucas}]}}";
> Now I want to unbin
I have bound a queue and topic with code:
"family ; {create:always,node: {type: topic,durable:True,
x-bindings:[{queue:lucas}]}}";
Now I want to unbind this connection,but i dont konw how to do;
Please help!
I try to use "delete:always" but the whole queue or topic will be delete at
last.
On 26/08/16 12:06, Petr Kubat wrote:
Hello everyone,
with the license of Berkeley DB version 6 having changed to a more
restrictive AGPL license, which is legally incompatible with most of the
projects currently using BDB, Fedora's long term goal is to get rid of
BDB completely. As qpid-cpp is o
On 26/08/16 11:13, rat...@web.de wrote:
I am using the c++ messaging API which (I think) only supports 0-9?
No, the c++ messaging API supports both 0-10 and 1.0. It does not at
present support websockets however.
Anyhow,
it would require me to manually send the AMQP commands using websocket
Hello everyone,
with the license of Berkeley DB version 6 having changed to a more
restrictive AGPL license, which is legally incompatible with most of the
projects currently using BDB, Fedora's long term goal is to get rid of
BDB completely. As qpid-cpp is one of the projects still dependent
Thanks for the reply ;)
I have read into the AMQP over WebSockets specs. However it seems that it
only supports AMQP 1.0 right?
I am using the c++ messaging API which (I think) only supports 0-9? Anyhow,
it would require me to manually send the AMQP commands using websockets
right? I was searching
Hi Ram,
yes - unfortunately the generic code we use for configuration parsing
doesn't have a way of understanding things like MB/GB ... nor does it allow
arithmetic operations. In practice I'd hope this particular value is only
changed by people who have done extensive testing and are very comfor
On 25/08/16 21:40, John McLaughlin wrote:
I am not sure of the proper etiquette here, but I wanted to say thanks to
Gordon.
Most welcome, thanks for giving the QPid project a try!
Building the C++ qpidd with "-Damqp_force=true" did, in fact, solve my
problem.
Great!
--
On 26/08/16 09:20, rlemmers wrote:
I'm using Qpid Proton (proton-j-0.13.0) to send messages over AMQP to an
ActiveMQ 5.12.0 queue. On a development machine, where ActiveMQ and the Java
program run on the same machine, this is working fine. On a test
environment, where ActiveMQ is running on a sep
I'm using Qpid Proton (proton-j-0.13.0) to send messages over AMQP to an
ActiveMQ 5.12.0 queue. On a development machine, where ActiveMQ and the Java
program run on the same machine, this is working fine. On a test
environment, where ActiveMQ is running on a separate server, we see the
send() metho
30 matches
Mail list logo
