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).
I figured 'the server is up' when the startup message appeared (I had
redirected the log to System.out. In the current test it should point
to null). I assumed this was the last thing the server did, but I
didn't verify that.
I tried to use anotherDatabaseSetups, but having 5 databases created
will also slow the test down.
I tried to debug this for some time, but could not get the error when
stepping in the debugger. I finally decided my stepping through in the
debugger was slow enough that the problem did not occur. It's possible
I misjudged this.
I also thought of making the sleep shorter, which may reintroduce the
intermittent failure - as the original testSecMec.java was wont to do.
I have a rather slow machine, the sleep can probably be reduced some.
Opinions?
Without input, I'll log a separate bug indicating it appears the
server is up but the database may still be inaccessible, and that this
can be confusing, and I'll reduce the sleep.
Myrna
