RE: svn commit: r884635 - in /qpid/trunk/qpid/java/systests/src/main/java/org/apache/qpid: server/security/firewall/FirewallConfigTest.java test/utils/QpidTestCase.java

[Robbie Gemmell <ro...@gmail.com>]

Ah, see I hadnt actually considered that it was the write that hadnt
finished, I just jumped to the conclusion it was the subprocess that hadnt
hehe...which in retrospect even if it was, I should have checked and waited
for instead of just the random pause - ill revisit that change.

Robbie

-----Original Message-----
From: Aidan Skinner [mailto:aidan.skinner@gmail.com] 
Sent: 26 November 2009 17:36
To: dev@qpid.apache.org
Cc: commits@qpid.apache.org
Subject: Re: svn commit: r884635 - in
/qpid/trunk/qpid/java/systests/src/main/java/org/apache/qpid:
server/security/firewall/FirewallConfigTest.java
test/utils/QpidTestCase.java

On Thu, Nov 26, 2009 at 4:47 PM,  <ro...@apache.org> wrote:

> QPID-2184: correct use of reload instead of restart in
testDenyOnRestartInVhost(), add a delay to the SIGHUP based reload to help
ensure the new config is in place before testing continues, helping prevent
sporadic failure

Urgh, random 1 second delay is pretty horrid.  If you're seeing
failures because the write hasn't completed flush() is probably the
right answer.

- Aidan
-- 
Apache Qpid - AMQP, JMS, other messaging love http://qpid.apache.org
"A witty saying proves nothing" - Voltaire

---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org



---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org