Hi Rajith,
To process to run the tests is:
1. Start a broker
2. Start at least 2 interop TestClient's (details below)
3. Run the Coordinator to initiate testing using a specified InteropTestCase
I only know of current TestClients for the Java and 0-8 .net clients,
the C++ TestClient was
2009/12/18 Robbie Gemmell robbie.gemm...@gmail.com: The -D
properties are there because the Coordinator
is a descendant of QpidTestCase (but it seems doenst need to be,
QPID-2164) and so needs those to get round current QTC behaviour.
Err, I meant that the interop test cases are descendants of
On 12/17/2009 08:13 AM, Rafael Schloming wrote:
Andrew Stitcher wrote:
On Wed, 2009-12-16 at 09:56 -0500, Alan Conway wrote:
I'm looking at some code that does sender flow control as follows:
- set a queue size limit
- sender catches 'resource-limit-exceeded' exception, sleeps for a
bit,
[
https://issues.apache.org/jira/browse/QPID-2295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Conway reassigned QPID-2295:
-
Assignee: Alan Conway
Clustered broker crashes with inconsistency error
Persistent cluster problems after reboot -f
Key: QPID-2296
URL: https://issues.apache.org/jira/browse/QPID-2296
Project: Qpid
Issue Type: Bug
Components: C++ Broker
Affects
Robbie,
Thanks for the detailed instructions
Rajith
On Fri, Dec 18, 2009 at 5:22 AM, Robbie Gemmell
robbie.gemm...@gmail.com wrote:
2009/12/18 Robbie Gemmell robbie.gemm...@gmail.com: The -D
properties are there because the Coordinator
is a descendant of QpidTestCase (but it seems doenst
Thank you very much to everyone who has helped to reduce the
blocking/critical bugs for 0.6 to just 1. We're almost ready to cut a
release.
The one remaining blocker bug is QPID-2273 -
http://issues.apache.org/jira/browse/QPID-2273 currently assigned to
Aidan.
This does indeed seem to be a
[
https://issues.apache.org/jira/browse/QPID-2273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aidan Skinner resolved QPID-2273.
-
Resolution: Fixed
Works with 0.5 as well. Win.
Java client can't negotiate to 0-9
Rafael Schloming wrote:
As there have been no comments or questions on the discussion thread,
I'm going to move this to a vote:
Qualities we look for:
- A candidate must demonstrate an understanding of how our project
is structured and how we work.
- A candidate must communicate
I'm now in the process of cutting the Release candidate for the 0.6
release. This implies a few things:
1. The trunk is now frozen for all checkins except blockers. Obviously
you'll need to include the Jira reference to the blocker in your checkin
comment
2. So any other changes will be reverted
[
https://issues.apache.org/jira/browse/QPID-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu updated QPID-2290:
---
Attachment: QPID-2290.patch
The commit made at rev 892123 on Qpid trunk has a few concerns
I've now uploaded the first release candidate for 0.6.
You'll be able to find it at:
http://qpid.apache.org/dist/qpid-0.6rc1
[when the automated sync process has finished]
Due to lack of time on my part I have not done any test building yet
(except the java/dotnet builds that are part of the
[
https://issues.apache.org/jira/browse/QPID-2297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rajith Attapattu updated QPID-2297:
---
Attachment: QPID-2297.patch
Added a simple fix to allow . as a valid char for a userID.
This
13 matches
Mail list logo
