> -----Original Message----- > From: Bryan Pendleton [mailto:bpendle...@amberpoint.com] > Sent: Wednesday, December 16, 2009 3:42 PM > To: Derby Discussion > Subject: Re: Just starting with Derby: Getting "Another instance of > Derby may have already booted the database" with embedded db > > > 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.
For now, I've got it working by putting the table creation code in my unit test code. I might change it to pass a path to the schema ddl instead.
