You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Robbie Gemmell (JIRA)" <qp...@incubator.apache.org> on 2009/10/01 17:37:23 UTC
[jira] Updated: (QPID-2125) FailoverBaseCase launches second broker
with QPID_WORK set to /tmp/ and silently fails to clean up
[ https://issues.apache.org/jira/browse/QPID-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robbie Gemmell updated QPID-2125:
---------------------------------
Status: Ready To Review (was: In Progress)
> FailoverBaseCase launches second broker with QPID_WORK set to /tmp/<alt port> and silently fails to clean up
> ------------------------------------------------------------------------------------------------------------
>
> Key: QPID-2125
> URL: https://issues.apache.org/jira/browse/QPID-2125
> Project: Qpid
> Issue Type: Bug
> Components: Java Tests
> Affects Versions: 0.5
> Reporter: Robbie Gemmell
> Assignee: Robbie Gemmell
> Priority: Minor
> Fix For: 0.6
>
>
> FailoverBaseCase launches second broker with QPID_WORK set to /tmp/<alt port> and fails to clean up. Although attempt is made to clear up, the method used is ineffective. Coupled with the QueueBrowser* tests making use of queue names containing the current time in millis, this can lead to repeated runs of the test suite with a persistence store resulting in a large number of queues for the broker to recover on subsequent tests, and eventually leads to test failure due to lengthy startup times.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org