On 4 March 2015 at 22:02, Gordon Sim <[email protected]> wrote: > On 02/20/2015 11:39 AM, Justin Ross wrote: > >> Hi, everyone. We have branched for release, and 0.32 beta is now >> available. >> >> Release branch: https://svn.apache.org/repos/asf/qpid/branches/0.32/ >> Release artifacts: https://dist.apache.org/repos/ >> dist/dev/qpid/0.32-beta/ >> Release tool log output: >> http://people.apache.org/~jross/qpid-0.32-beta.log >> >> This is pre-release software, for testing only. >> >> Now that we've branched, 0.32 changes require developer review and release >> manager approval. See the release page for details. It means as well >> that >> trunk has opened for forward development. >> >> Please test the beta in your environment and report your results on the >> list. Thank you very much to those who tested the alpha. >> > > Built and installed qpid-cpp (against latest proton master), java broker, > python client, qmf lib and tools. > > Tests and tools ran fine against c++ broker. > > Had some issues with the java broker. It now starts with no virtual host > defined(?). Meaning that any attempt to connect got an error. (This is > after enabling anonymous, as even plain appeared to be disabled by > default?). After creating a virtual host, was able to run some tests > against it using qpid-cpp clients over both 0-10 and 1.0. >
That's odd... The out of the box config should have a virtualhost. Were you running a completely fresh install, or were you running with an existing config/work directory? In terms of authentication, by default PLAIN is no longer enabled over non-TLS connections. > > There *seems* to be something odd happening when trying to consume > messages from a queue. Over 0-10 I only get the messages if I issue a > message-flush. Over 1.0 I sometimes can't get any messages out at all. Not > sure if this is only when queue was created over 0-10. Even for a queue > created through management, I was not getting messages at times after > having sent them and had them accepted (switching back to 0-10 and > flushing, I could see them all as expected). If the receiver is active > before messages are sent (whether through exchanges or direct through > queues), receiving seems to work ok. > > Got a deadlock trying to stop the (java) broker, see attached. On > restarting, my virtual host was there but somehow things were corrupted and > could not connect again until I deleted and recreated it. So, the deadlock actually happened before the close, it occurred when a flow arrived at the broker at the same time as a message was being sent from the broker to a consumer... I'll fix that now on trunk (I don't think that looks like a new issue, but we should fix it anyway). The effect of the deadlock would be that that queue would no longer be distributing messages. -- Rob > > > The next planned build is our first RC on March 4th. >> > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
