On 3/29/07, Daniel John Debrunner <[EMAIL PROTECTED]> wrote:
Myrna van Lunteren wrote:
> On 3/28/07, Daniel John Debrunner (JIRA) <[EMAIL PROTECTED]> wrote:
>>
>> [
>>
https://issues.apache.org/jira/browse/DERBY-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>> ]
>>
>> Daniel John Debrunner reopened DERBY-1496:
>> ------------------------------------------
>>
>>
>> NSSecurityMechanismTest has this TODO in it:
>>
>> // TODO: sleep ridiculously long, otherwise getting 08001
>> errors
>> // even when the server is up.
>> Thread.sleep(120000);
>>
>>
>> That sleep in executed a number of times, slowing the test runs down.
>> If the server is up and running and giving errors, would that be a bug?
>>
> Possibly...
> It may be the extra time needed is because the database is reused for
> each security mechanism. I imagine that takes longer, so the server
> may be up, but the database not (yet).
A different approach may be to use the client server decorator which
already handles this. Then each security mechanism would be a different
fixture run.
Dan.
Hm, the test already uses clientServerDecorator. Did I make a mistake
there somewhere?
Myrna
