You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2013/01/15 23:08:12 UTC
[jira] [Resolved] (AMQ-4254) BrokerXmlConfigStartTest fails
intermittently
[ https://issues.apache.org/jira/browse/AMQ-4254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish resolved AMQ-4254.
-------------------------------
Resolution: Fixed
Fixed now on both my test platforms, was failing on both previously.
> BrokerXmlConfigStartTest fails intermittently
> ---------------------------------------------
>
> Key: AMQ-4254
> URL: https://issues.apache.org/jira/browse/AMQ-4254
> Project: ActiveMQ
> Issue Type: Bug
> Components: Test Cases
> Reporter: Kevin Earls
> Assignee: Timothy Bish
> Priority: Minor
> Fix For: 5.8.0
>
> Attachments: AMQ4254a.patch, AMQ4254.patch
>
>
> BrokerXmlConfigStartTest.testStartBrokerUsingSampleConfig fails intermittently on Hudson/Jenkins with the error
> "Error creating bean with name 'Server' defined in file [/home/hudson/hudson-slave/workspace/ActiveMQ-Java7/assembly/target/conf/jetty-demo.xml]: Invocation of init method failed; nested exception is java.net.BindException: Address already in use"
> I will attach a patch with this test rewritten as a JUnit4 Parameterized test. This creates runs each config as a separate test case and seems to resolve the broker start/stop issue.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira