On 01/03/2014 01:52 PM, Crinklaw-Vogt, Matthew wrote:
Since qpid 0.14 and 0.24 both support the same version of the AMQP spec, should
I expect a qpid 0.24 java client to work with the qpid 0.14 C++ broker?
Though we probably haven't tested that specific combination as part of
the release, I
Please find the Qpid Dispatch Router RC5 here at the following link.
This contains the fix for QPID-5448
(https://issues.apache.org/jira/browse/QPID-5448).
http://people.apache.org/~tross/qpid-dispatch-0.1rc5/
This release is dependent on the Proton 0.6 release
(http://people.apache.org/~rhs
Since qpid 0.14 and 0.24 both support the same version of the AMQP spec, should
I expect a qpid 0.24 java client to work with the qpid 0.14 C++ broker?
I assume that if I were to venture out an use features like 'x-bindings' that
aren't covered in the AMQP spec then I shouldn't expect those to w
I will put up a new RC to address the problem Darryl found. The vote
will be re-started next week if all goes well with RC5.
-Ted
On 01/03/2014 09:50 AM, Darryl L. Pierce wrote:
On Thu, Jan 02, 2014 at 03:28:53PM -0500, Ted Ross wrote:
I am starting a vote on the initial release of the Qpid
+1
Tested by installing on a bare-bones Centos 5.10 VM (i686). Unit tests passed,
with one minor nit:
https://issues.apache.org/jira/browse/QPID-5449
Installed python tools, python client. Built drain & spout C++ examples, all
looks good.
The man page has this one interesting glitch:
On 01/02/2014 07:55 PM, Justin Ross wrote:
RC2 is now available from revision 1551622 of the release branch:
http://people.apache.org/~jross/qpid-0.26-rc2/
http://people.apache.org/~jross/qpid-0.26-rc2-testing.txt
Please give it a test and report what you find. I discovered one new
block
On 01/03/2014 04:13 PM, Gordon Sim wrote:
On 01/02/2014 07:55 PM, Justin Ross wrote:
RC2 is now available from revision 1551622 of the release branch:
http://people.apache.org/~jross/qpid-0.26-rc2/
http://people.apache.org/~jross/qpid-0.26-rc2-testing.txt
Please give it a test and report
Thank you! I totally missed the part with the inter-router connection.
Now everything is working as expected.
-Sascha
On 01/03/2014 03:39 PM, Ted Ross wrote:
On 01/03/2014 06:28 AM, Sascha Kattelmann wrote:
Hi,
I'm currently working on gathering logs from devices in a network via
AMQP. The
On 01/03/2014 07:25 AM, Pavel Moravec wrote:
Hi all,
I have finished implementing AMQP 1.0 dissector to Wireshark, to simplify our
troubleshooting of issues with communication over the protocol. See [1] for the
bug requesting inclusion in Wireshark.
As I don't know when my work will appear in
On Thu, Jan 02, 2014 at 03:28:53PM -0500, Ted Ross wrote:
> I am starting a vote on the initial release of the Qpid Dispatch
> message router. This vote is to use RC4 as the official 0.1
> release.
>
> Source location:
>
> http://people.apache.org/~tross/qpid-dispatch-0.1rc4/
>
> Documentat
On 01/03/2014 06:28 AM, Sascha Kattelmann wrote:
Hi,
I'm currently working on gathering logs from devices in a network via
AMQP. The dispatch router seems to be a good choice for this. I tried
the examples provided with
svn.apache.org/repos/asf/qpid/dispatch/trunk/doc/book/release-0.1.md
an
Hi all,
I have finished implementing AMQP 1.0 dissector to Wireshark, to simplify our
troubleshooting of issues with communication over the protocol. See [1] for the
bug requesting inclusion in Wireshark.
As I don't know when my work will appear in a Wireshark public release, feel
free to build
Hi,
I'm currently working on gathering logs from devices in a network via
AMQP. The dispatch router seems to be a good choice for this. I tried
the examples provided with
svn.apache.org/repos/asf/qpid/dispatch/trunk/doc/book/release-0.1.md
and everything works fine (I'm using the rc3 of Prot
13 matches
Mail list logo
