On 01/04/2010 09:36 PM, Andrew Stitcher wrote:
For your new year resolution:
http://qpid.apache.org/dist/qpid-0.6rc3/
In theory the only part of the code that could have regressed since the
previous release candidates is the java code as that is all the code
that has changed since then.
However as I don't plan to make any changes until the release except
blockers and release notes now, please give everything a good going
over.
In a couple of days (if no one has found any blockers) I'll post a vote
for release with only release note changes.
I hit a few usability issues which perhaps could be alleviated by
changes to release notes or readmes (all the release notes I saw were
out of date - i.e. referred to M4 release - but I'm assuming from the
above that changes to these are panned anyway):
The ruby README is missing a couple of points (need to run make and need
to add ext/sasl to RUBYLIB as well); I presume this means it does not
run on windows? (Very minor: hello-world is not executable by default).
Successfully built and ran all tests for c++ on fedora 11. Ran python &
ruby tests against c++ broker. Ran qpid-bench (java) against c++ broker.
Did a make install with a prefix which also worked fine though the
examples Makefile need to be edited by hand to work against the prefixed
install.
I couldn't start java broker out of the box (had to disable SSL for JMX
in conf file). Might be nice to have that off by default as with the
standard ssl access?
When running python tests (0-10) against the java broker they hung on
qpid.tests.messaging.MessageEchoTests.testProperties. The 0-8 tests ran
with 3 failures (tests_0-8.queue.QueueTests.test_declare_exclusive,
tests_0-8.queue.QueueTests.test_delete_simple and
tests_0-8.queue.QueueTests.test_purge - possibly related to 0-9-1
changes?). The 0-9 tests ran with 6 out of 10 failures.
When running the ruby tests against the java broker I was prompted for a
password and the tests then hung (guest did not work). This is very
likely just requiring correct authentication details to be specified but
it wasn't immediately obvious how to specify that.
I tried running the hello world ruby example against the java broker,
modified to pass in the username and password, but that timed out on
connection.start.
I had similar issues trying to run the c++ client-test against the java
broker (client sends connection.start but doesn't get a response).
The java client only download doesn't contain any tests, scripts or
example to run or any instructions (except some basic ones for the
server). The full java download doesn't have any examples either, but I
ran the qpid-bench test against both brokers.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:[email protected]
