Hi, Yes I forgot to run the python tests. I still need to get a proper installation of python on my windows machine so I can run those python tests more frequently.
Ideally I would like to link them with the maven build but as I use cygwin things can be a bit tricky as mvn picks up cygwin python not windows python and it all goes a bit pear shaped. As to the problems you saw with the python scripts. This is down to the fact that the python is not compliant. The java broker stopped allowing AMQPLAIN as an authentication method but the python is obviously hardwired to only use that hence the Java broker closed the connection when it tried to use an 'invalid' authentication mechanism. I have reinstated the AMQPLAIN mechanism. It shouldn't have been disabled in the first place. As for the missing files in the distribution I don't run the distributions very often and would have thought that they would copy all files in etc. Silly me to think that the distributions are hard coded. I shall update them to be more flexible after I have committed the fixes to restore the python tests. Regards Martin On 16/03/07, Alan Conway <[EMAIL PROTECTED]> wrote:
Problems on the java trunk, Martin, I think you commits r518989, r518988 are the cluprits: Trying to run a Java broker I get: org.apache.commons.configuration.ConfigurationException: java.io.FileNotFoundException: Cannot find password file /home/aconway/svn/qpid/java/distribution/target/qpid-1.0-incubating-M2-SNAPSHOT-java-bin/qpid-1.0-incubating-M2-SNAPSHOT/etc/passwdVhost Error configuring message broker: org.apache.commons.configuration.ConfigurationException: java.io.FileNotFoundException: Cannot find password file /home/aconway/svn/qpid/java/distribution/target/qpid-1.0-incubating-M2-SNAPSHOT-java-bin/qpid-1.0-incubating-M2-SNAPSHOT/etc/md5passwd I fixed the problem by copying the files from qpid/broker/etc to the (ridiculous) location where where maven is installing things but I don't know how to fix maven to do this during the build. Also I'm merging python to trunk and with the java broker I'm getting all python tests failing with: Closed: Method(name=close, id=60) (506, 'Unable to create SASL Server [error code 506: resource error]', 10, 11) content = None It could well be my screw-up but I was a bit suspicious to see another security related failure - Martin, did you run the python tests on those commits? Cheers, Alan.
-- Martin Ritchie
