db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jean T. Anderson" <...@bristowhill.com>
Subject Re: Accessing embedded Derby in forked Maven2 build
Date Mon, 13 Mar 2006 23:07:54 GMT
Randy Watler wrote:
> Andrew:
> 
> Andrew McIntyre wrote:
> 
>>
>> It sounds like you're setting up a test database using Ant's <sql>
>> commands and this leaves the Derby engine running in the same VM as
>> Ant. So, my original solution wouldn't work, as ij wouldn't be able to
>> connect. It sounds like you may need to move the creation of the test
>> database into another VM. You could do this by putting all of the SQL
>> you have in your Ant <sql> statements into a file and running it in a
>> forked JVM using ij.
>>
>>   
> 
> Right. This is why when I run your solution I get cannot connect
> messages... even if it is not forked. So how is the best way to shutdown
> the engine? I assume that because an engine is running, ij cannot
> connect. But why is that if I do not fork ij?
> 
> Randy
> 
> 

This developerWorks article provides StopDatabaseTask and StopDerbyTask
Ant tasks:

http://www.ibm.com/developerworks/db2/library/techarticle/dm-0412snell/index.html

If this helps resolve your problem, please let us know.

 -jean

Mime
View raw message