first runs some sql through the "sql" task, then runs JUnit to run my test class?
If you take out the "sql" task invocation, does your script run correctly? If so, then I'd think this might be a bug in the SQL task, that it isn't closing down the connection properly at the completion of its work. But if you still get the problem with the "sql" task removed, then it may be that you somehow have some other process which still has the database open. thanks, bryan
