Oystein, Yes, exactly that is the point which I wanted. It shuts down the entire Derby system(Derby Engine+Database) thrice, but it fails to do so from the 4th test case and further on. Obviously resulting in the exceptions.
Kamesh. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Saturday, December 06, 2008 10:34 PM To: Derby Discussion Cc: [EMAIL PROTECTED] Subject: Re: Urgent : Problem in booting up the database using Derby Emmanuel Cecchet wrote: > Kamesh, > >> I'm suffering a weird kind of a problem while running my JUnit Test >> Cases against a database which uses derby as an engine. >> Once after each test case gets completed I'm shutting down the >> database and derby using the following piece of code >> >> DriverManager.getConnection("jdbc:derby:;shutdown=true"); > Are you not supposed to provide the database name in the URL? It looks > like it is missing here. > No, if you do not specify a database, all booted databases and the database engine will be shut down. -- Øystein
