Eike Stepper wrote:
hi steve,
first i was unsure what you advice is. but then i have set the timeout value to 0 and everything executed like a hurricane. i still have no clue what happend behind the scenes when the timeout was 1000, but i hope that i can rely on the current state...
Small mistake in what I said below - I should have said 1000, not 100.
Anyway - I was assuming you already has a 0 timeout which would account for the 1000 deployment times that were occurring. Here is the code from the CommissionRequest:
private void waitForCompletion( long timeout )
throws InterruptedException
{
if( timeout > 0 )
{
wait( timeout );
}
else
{
while( !m_completed )
{
wait( 1000 );
}
}
}The only reason for this is that a deployment timeout of 0 would result in an indefinite wait - so instead we just snooze for 1000 and check that the deployment has not generated any errors and if its still executed then back to snooze again.
Steve.
--
|---------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org | |---------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
