
|
If you were logged in you would be able to see more operations.
|
|
|
|
Environment:
|
Postgresql 8.1
Fedora Core 5/Gentoo/Mac OS X 10.4
Postgresql 8.1
Fedora Core 5/Gentoo/Mac OS X 10.4
|
|
|
In my custom set up, the database server is shutdown after the dao tests have run using a script that called the postgres command "pg_ctl stop".
Initially I was using maven to call the antrun plugin to run dbunit to load the sample data. This worked fine.
After I had changed to using the maven dbunit plugin, the database stop script hung.
My conclusion is that dbunit, run from the maven plug in, is not closing its database connection.
My solutions was to use:
pg_ctl stop -m f
This will shutdown the database without waiting for all clients to disconnect, forcing a role back for any currently open transactions.
|
|
Description
|
In my custom set up, the database server is shutdown after the dao tests have run using a script that called the postgres command "pg_ctl stop".
Initially I was using maven to call the antrun plugin to run dbunit to load the sample data. This worked fine.
After I had changed to using the maven dbunit plugin, the database stop script hung.
My conclusion is that dbunit, run from the maven plug in, is not closing its database connection.
My solutions was to use:
pg_ctl stop -m f
This will shutdown the database without waiting for all clients to disconnect, forcing a role back for any currently open transactions.
|
Show » |
Sort Order:
|