On 5 March 2015 at 12:42, Gordon Sim <[email protected]> wrote: > On 03/05/2015 11:21 AM, Rob Godfrey wrote: > >> To verify, I downloaded the broker tgz from here >> https://builds.apache.org/view/M-R/view/Qpid/job/Qpid- >> Java-Artefact-Release-0.32/ >> expanded >> it into an empty directory, set QPID work to a non existent location, and >> ran bin/qpid-server. >> >> On startup the broker had a single (Json) virtual host node, containing an >> (active) Derby virtual host. >> >> This is the behaviour I would expect... >> > > Retested and I can confirm I see the same. Looking at my bash history, it > seems I got a typo in first setting QPID_WORK, presumably meaning it picked > up something stale from the default location(?). Apologies for the false > alarm, it was a user error. > > > Interesting... I guess it found something where the virtual host configuration had been blown away... otherwise it should have automatically upgraded your old config. Anyway, glad to know that the out of the box installation does have a vhost as expected.
-- Rob > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
