You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2007/09/27 11:09:50 UTC
[jira] Commented: (QPID-596) Intermittent ConnectionStartTest
Failure
[ https://issues.apache.org/jira/browse/QPID-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12530661 ]
Martin Ritchie commented on QPID-596:
-------------------------------------
Not entirely sure why the VM didn't exist .. however the test itself is broken.
as I got this error on a 8 way box:
Test set: org.apache.qpid.test.unit.client.connection.ConnectionStartTest
-------------------------------------------------------------------------------
Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 1.057 sec <<< FAILURE!
testSimpleReceiveConnection(org.apache.qpid.test.unit.client.connection.ConnectionStartTest) Time elapsed: 0.
019 sec <<< FAILURE!
junit.framework.AssertionFailedError: There should be messages waiting for the consumer
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at org.apache.qpid.test.unit.client.connection.ConnectionStartTest.testSimpleReceiveConnection(ConnecttionStartTest.java:103)
But the current assert line only fails if it does get a message! so something isn't quite right.
> Intermittent ConnectionStartTest Failure
> ----------------------------------------
>
> Key: QPID-596
> URL: https://issues.apache.org/jira/browse/QPID-596
> Project: Qpid
> Issue Type: Bug
> Components: Java Tests
> Affects Versions: M2.1
> Environment: Win XP using cygwin, test failed in maven build
> Reporter: Martin Ritchie
>
> A timeout is not very helpful at all. Sorry. This poor error will be done to QPID-594
> Tests run: 2, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 31.078 sec <<< FAILURE!
> testSimpleReceiveConnection(org.apache.qpid.test.unit.client.connection.ConnectionStartTest) Time elapsed: 30.031 sec <<< FAILURE!
> junit.framework.AssertionFailedError: Connection to vm://:1 should succeed. Reason: javax.jms.JMSException: Error closing session: org.apache.qpid.AMQTimeoutException: Server did not respond in a timely fashion [error code 408: Request Timeout]
> at junit.framework.Assert.fail(Assert.java:47)
> at org.apache.qpid.test.unit.client.connection.ConnectionStartTest.setUp(ConnectionStartTest.java:80)
> at junit.framework.TestCase.runBare(TestCase.java:125)
> at junit.framework.TestResult$1.protect(TestResult.java:106)
> at junit.framework.TestResult.runProtected(TestResult.java:124)
> at junit.framework.TestResult.run(TestResult.java:109)
> at junit.framework.TestCase.run(TestCase.java:118)
> at junit.framework.TestSuite.runTest(TestSuite.java:208)
> at junit.framework.TestSuite.run(TestSuite.java:203)
> at sun.reflect.GeneratedMethodAccessor10.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.apache.maven.surefire.junit.JUnitTestSet.execute(JUnitTestSet.java:210)
> at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet(AbstractDirectoryTestSuite.java:135)
> at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute(AbstractDirectoryTestSuite.java:122)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:129)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(SurefireBooter.java:225)
> at org.apache.maven.surefire.booter.SurefireBooter.run(SurefireBooter.java:139)
> at org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:376)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.