Andrew/Jean,
I have resolved this by forking the build process to place the sql
operations against the DB in a separate JVM process. This way, the build
will sequentially startup individual JVMs for all derby access and
thereby avoid the locks.
To make life easier for Ant and other similarly challenged environments,
it might be nice to have a statement, (e.g. stored procedure), of some
sort that can shutdown the databases and engines. Of course, I
understand that may not even be possible... :-(.
Anyway, off and running with a clunky patch of Ant code for now...
thanks for the help!
Randy
Randy Watler wrote:
Jean T. Anderson wrote:
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
I've been trying hard to avoid the custom tasks and the build fun that
involves. Thanks for the reference though... might just come in handy
if i can not manage to fork ant from ant...
Randy
