+1
- Original Message -
> From: "Ted Ross"
> To: users@qpid.apache.org
> Sent: Tuesday, August 2, 2016 9:17:20 AM
> Subject: [VOTE] Release Qpid Dispatch Router 0.6.1
>
> This is the vote thread for Qpid Dispatch Router 0.6.1 (RC1). Please
> test and vote:
>
>
On 03/08/16 18:23, Robbie Gemmell wrote:
On 3 August 2016 at 18:08, Gordon Sim wrote:
I think this is different from proton's behaviour (and from qpidd's) where
the similar flags are false by default. (This is a distinct concern from the
default sasl mechanisms enabled).
On 3 August 2016 at 18:08, Gordon Sim wrote:
> On 03/08/16 17:54, Robbie Gemmell wrote:
>>
>> On 3 August 2016 at 17:37, Jakub Scholz wrote:
>>>
>>> Hi,
>>>
>>> When I have listener configured like this:
>>>
>>> listener {
>>> role: normal
>>> host:
On 03/08/16 17:54, Robbie Gemmell wrote:
On 3 August 2016 at 17:37, Jakub Scholz wrote:
Hi,
When I have listener configured like this:
listener {
role: normal
host: 0.0.0.0
port: amqp
saslMechanisms: PLAIN DIGEST-MD5 CRAM-MD5
linkCapacity: 1000
}
Is it
On 3 August 2016 at 17:37, Jakub Scholz wrote:
> Hi,
>
> When I have listener configured like this:
>
> listener {
> role: normal
> host: 0.0.0.0
> port: amqp
> saslMechanisms: PLAIN DIGEST-MD5 CRAM-MD5
> linkCapacity: 1000
> }
>
> Is it really expected that
+1
I built it from source code and run some of my tests including connections
to Qpid C++ broker and various clients.
On Tue, Aug 2, 2016 at 3:17 PM, Ted Ross wrote:
> This is the vote thread for Qpid Dispatch Router 0.6.1 (RC1). Please test
> and vote:
>
>
And how do you measure your throughput?
> From: adelbout...@live.com
> To: users@qpid.apache.org
> Subject: RE: [Performance] Benchmarking Qpid dispatch router 0.6.0 with Qpid
> Java Broker 6.0.0
> Date: Wed, 3 Aug 2016 18:38:12 +0200
>
> Hello Ulf,
>
> I am sending messages with a byte array
Hello Ulf,
I am sending messages with a byte array of 100 bytes and I am using Berkley DB
as a message store (which should be slower than having memory only message
store, no?)
With 1 consumer, 1 producer and no broker, I am at 33k msgs/sec if they are all
on the same machine and I have set
Hi,
When I have listener configured like this:
listener {
role: normal
host: 0.0.0.0
port: amqp
saslMechanisms: PLAIN DIGEST-MD5 CRAM-MD5
linkCapacity: 1000
}
Is it really expected that it allows anonymous access? It seems that unless
I add to the listener configuration also
These fixes missed the beta cut-off by a few hours!
PROTON-1272: This is a trivial fix that allows build tests to run
correctly on more systems (RHEL 6 in particular)
PROTON-1243: This is a serious bug in a basic functionality of proton-c
reactor and its bindings (and maybe in the proton-j
+1
* Downloaded distribution
* Verified checksums
* Verified that patch to DISPATCH-367 and relevant units tests are present.
* Ran all unit tests successfully
Thanks.
- Original Message -
> From: "Ken Giusti"
> To: users@qpid.apache.org
> Sent: Wednesday, August
On 3 August 2016 at 15:52, Gordon Sim wrote:
> On 03/08/16 15:13, Robbie Gemmell wrote:
>>
>> ActiveMQ 5.9.0 is rather old and its AMQP 1.0 support was fairly
>> recent at the time, its changed a lot since then. You'll want to try a
>> newer version. 5.13.4 is the current, with
On 03/08/16 12:40, Sasikumar Ramasamy wrote:
Hi Folks,
I am a new bee for messaging service. My need is to parse reactive messages
through network using core java. I tried to implement Active-MQ and kafka,
but i got messed up. I can't find semantic Tutorials/Demo regarding this.
And now i
+1
- passes oslo functional tests, simulator, and test clients
- Original Message -
> From: "Ted Ross"
> To: users@qpid.apache.org
> Sent: Tuesday, August 2, 2016 9:17:20 AM
> Subject: [VOTE] Release Qpid Dispatch Router 0.6.1
>
> This is the vote thread for Qpid
On 03/08/16 15:13, Robbie Gemmell wrote:
ActiveMQ 5.9.0 is rather old and its AMQP 1.0 support was fairly
recent at the time, its changed a lot since then. You'll want to try a
newer version. 5.13.4 is the current, with 5.14.0 currently under vote
for release.
Yes, if I recall correctly 5.9
Hi,
Excuse me if this was already mentioned somewhere, but what is the size
of the messages you are sending ?
FWIW, I'm able to get around 30-40k msgs/sec sustained with 1 producer,
1 consumer, 1 dispatch (4 worker threads) and 1 broker (activemq-5). The
sender sends unsettled messages as
ActiveMQ 5.9.0 is rather old and its AMQP 1.0 support was fairly
recent at the time, its changed a lot since then. You'll want to try a
newer version. 5.13.4 is the current, with 5.14.0 currently under vote
for release.
On 3 August 2016 at 14:37, eric73 wrote:
> Hello
Hi Paolo,
I try "route-container" instead of "on-demand" and it is the same problem of
timeout.
Thanks for the reply.
Regards
Eric
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Qpid-dispatch-router-issue-tp7648428p7648648.html
Sent from the Apache Qpid users mailing list
Hello Sim,
I use Apache ActiveMQ broker 5.9.0 with AMQP1.0 on Windows 7 Entreprise.
The clients run on Linux mint 17.3.
--
View this message in context:
http://qpid.2158936.n2.nabble.com/Qpid-dispatch-router-issue-tp7648428p7648644.html
Sent from the Apache Qpid users mailing list archive
On 03/08/16 13:45, eric73 wrote:
Thank Ted.
I set "standalone" mode for the router configuration.
But now the dispatch router seems have problem when it try to connect to the
broker.
Indefinitely, there is a timeout error after connection: "local-idle-timeout
expired".
What broker are you
Hi,
the role for the connector should be "route-container" not "on-demand".
Regards,
Paolo.
Paolo PatiernoSenior Software Engineer (IoT) @ Red Hat
Microsoft MVP on Windows Embedded & IoTMicrosoft Azure Advisor
Twitter : @ppatierno
Linkedin : paolopatierno
Blog : DevExperience
> Date: Wed, 3
Thank Ted.
I set "standalone" mode for the router configuration.
But now the dispatch router seems have problem when it try to connect to the
broker.
Indefinitely, there is a timeout error after connection: "local-idle-timeout
expired".
Here is the dispatch router log:
...
...
Regards
--
View
Hello again,
As requested, I added a 2nd connector and the appropriate autoLinks on the same
host/port but with a different name. It seems to have resolved the issue.
1 Broker, 1 Dispatcher, 3 producers, 0 consumers, 1 connectors --> 5000 msg/s.
1 Broker, 1 Dispatcher, 3 producers, 0
Hi Folks,
I am a new bee for messaging service. My need is to parse reactive messages
through network using core java. I tried to implement Active-MQ and kafka,
but i got messed up. I can't find semantic Tutorials/Demo regarding this.
And now i just figured out Qpid AMQP, which could be a
On 03/08/16 00:26, Justin Ross wrote:
This problem remains for me. Unless this is shown to be my error, it
blocks the C++ release.
The problem appears related to code that was recently changed.
https://gist.github.com/ssorj/44fcffd57075ad230ec8d221bca8e92a
25 matches
Mail list logo