On Wed, May 16, 2012 at 9:58 AM, Charith Wickramarachchi <[email protected]>wrote:
> Hi Hasitha , > > In the reports if we look at the coverage reports. In Both MB an andes > there are lot of untested requirements. And when i look in to the > details.The reason is it can't connect to the broker. > > javax.jms.JMSException: Error creating connection: Connection refused > at > org.apache.qpid.client.AMQConnectionFactory.createXAConnection(AMQConnectionFactory.java:464) > at > org.apache.qpid.client.AMQConnectionFactory.createXAConnection(AMQConnectionFactory.java:499) > at > org.apache.qpid.client.AMQConnectionFactory.createXAQueueConnection(AMQConnectionFactory.java:564) > at > org.exolab.jmscts.core.ConnectionFactoryHelper.createConnection(ConnectionFactoryHelper.java:100) > at > org.exolab.jmscts.core.ConnectionTestRunner$Tester.setUp(ConnectionTestRunner.java:139) > at org.exolab.jmscts.core.TestInvoker.protect(TestInvoker.java:146) > at junit.framework.TestResult.runProtected(TestResult.java:124) > at > org.exolab.jmscts.core.ConnectionTestRunner.runTest(ConnectionTestRunner.java:104) > at org.exolab.jmscts.core.TestRunner.basicRun(TestRunner.java:144) > > > Hi Hasitha, I also got this exception yesterday when testing with ws-event compatibility. The issue for this was due to the port binding issue. I could get rid of this by altering the bind ip address which can be found in qpid-config.xml file to 0.0.0.0. Thanks Shammi > So i think still this report is not complete. This must be a configuration > /setup issue. > > thanks, > Charith > > > On Tue, May 15, 2012 at 9:53 AM, Hasitha Hiranya <[email protected]>wrote: > >> Hi, >> >> I used JMSCTS [1] to test current MB (Actually Andes). I am attaching the >> test results herewith. A few things to be noted. >> >> >> - Some test failure happens as we do not allowed to delete >> distributed queues yet. >> - I could not run all the tests even if I allowed to run it from 8.00 >> P.M to 7.00 A.M. I took a snapshot of reports while it was running. >> - Test environment is* one node, clustering >> enabled, OnceInOrderSupport disabled, Zookeeper and Cassandra servers are >> externally running.* >> - There are other issues like timeouts etc, which can be configured. >> I used >> >> * >> * >> * >> # Message receipt timeout >> * >> * >> # The default time to wait for messages, in milliseconds >> * >> * >> # >> * >> * >> org.exolab.jmscts.core.MessagingBehaviour.timeout=2000 >> ** * >> >> >> >> - I have also tested previous MB release to have a comparison and to >> verify that I have set the test environment correctly. I am attaching >> those >> test results as well. >> >> >> Note: test results html pages are linked to each other. Open >> coverage.html to see overall results. >> >> Further, I'd like to know if we have to integrate JMSCTS with Andes. And >> any idea how to overcome the problems we have with tests? Because as I can >> see a lot has failed to various reasons. I have attached a part of the log >> too (as it is too big to mail). >> >> >> [1]. http://jmscts.sourceforge.net/ >> >> >> Thank You. >> >> -- >> *Hasitha Abeykoon* >> Software Engineer; WSO2, Inc.; http://wso2.com >> *cell:* *+94 719363063* >> *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com>* * >> * >> * >> >> > > > -- > Charith Dhanushka Wickramarachchi > Software Engineer > WSO2 Inc > http://wso2.com/ > http://wso2.org/ > > blog > http://charithwiki.blogspot.com/ > > twitter > http://twitter.com/charithwiki > > Mobile : 0776706568 > > > -- Best Regards,* Shammi Jayasinghe* Senior Software Engineer; WSO2, Inc.; http://wso2.com, mobile: +94 71 4493085
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
