Hi, folks. I'm planning to produce a minor Proton update at the end of
this week. Please raise candidate issues. They should be important,
minimum-delta fixes.
Thanks,
Justin
+1
* built from source distribution artefact and ran all tests (mvn verify)
* ran Joram JMS tests against the Java Broker (trunk and 6.0.3) using
the staged Maven artefacts
* verified the signatures, MD5s and SHAs of the source and binary
distribution artefacts
On 27 June 2016 at 19:18, Timothy B
+1
* checked the license and notice files in the archives
* built from source and ran all tests.
* ran the example against an ActiveMQ broker
* ran the ActiveMQ broker tests using the artifacts from the staging repo
* gave the updated docs a once over.
On 06/27/2016 12:33 PM, Robbie Gemmell wrot
Hi folks,
I have put together a spin for a 0.10.0 Qpid JMS client release, please
test it and vote accordingly.
The source and binary archives can be grabbed from here:
https://dist.apache.org/repos/dist/dev/qpid/jms/0.10.0-rc1/
Those files and the other maven artifacts are also staged for now a
Adel, there is a plan to add some more detailed documentation on setting up
SASL/SSL in the router but it will not delve into details of SSL/TLS since that
is already public knowledge. Thanks.
- Original Message -
> From: "Adel Boutros"
> To: users@qpid.apache.org
> Sent: Monday, June 2
You are right. Nevertheless, working with security is never easy as there are
so many options to configure and a lot of points to be careful at.
What do you think about having a tutorial section in the dispatcher book
explaining how to setup SSL/SASL from what we have done here? I think it would
Adel, Glad you got it working.
I have augmented the script gencerts_openssl.sh
(https://github.com/apache/qpid-dispatch/blob/master/tests/ssl_certs/gencerts_openssl.sh)
to now include the creation of an intermediate CA and using it to create the
server and client certificates.
An important po
Great, thats what I was expecting to see happen.
As described in https://issues.apache.org/jira/browse/DISPATCH-367, if
you were sending synchronously, then by the time the subsequent
messages reach the router all the consumers have the same ability to
receieve it and the router just sent it to th
I removed the thread sleep from the producer and it now seems to be working
as expected as in messages are load balanced across the consumers.
Why would that have a impact on the way the router dispatches messages to
the consumer ?
On Mon, Jun 27, 2016 at 8:37 PM, Robbie Gemmell
wrote:
> They
They should be getting sent asynchronously, since the client actually
sends non-persistent messages async by default, plus the force option
is there.
There is a Thread.sleep in there for the producer, tried it without
the sleep? How long is it sleeping?
The 0.9.0 version of the client was mention
10 matches
Mail list logo
